[Olsr-dev] including wifi stats in jsoninfo

Clemens Hopfer (spam-protected)
Sat Jun 9 13:15:57 CEST 2012


On Wednesday 06 June 2012 16:20:35 Hans-Christoph Steiner wrote:
> [...]
> I agree we should not put everything into olsrd.  The stuff I'm talking
> about is entirely in the jsoninfo plugin, so people don't need to use it
> all.  The jsoninfo plugin would not be larger than pud or tas with iwinfo
> in it.

keep in mind, that the plugin will be running with the same privileges as the 
olsrd, since it's just a loaded library. And since olsrd must be running as 
root, its a _very_bad_ idea to be able to call binaries from the plugin.

Also, since olsrd is basically not threaded, it will block (pls correct me if 
I'm wrong) while processing data for the plugin communication.

So being able to acces, and thus attack a olsrd plugin is directly attacking 
the olsrd itself, which is the core element of your infrastructure.

> One idea for making olsrd smaller is making it easy to build the plugins
> outside of olsrd itself, so they can be entirely separate projects.  This
> is a better approach IMHO than trying to limit what people do with
> plugins.

IMHO this should be an external application accessing the APIs of olsrd and 
the other binaries you want to get data from.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.olsr.org/pipermail/olsr-dev/attachments/20120609/8ebec9d2/attachment.sig>

More information about the Olsr-dev mailing list