Max, process segregation. You can have one Nodejs process running as root doing all the GPIO / root stuff. Another process that handles the outside communications. Then you pick a method for these two process to communicate.
what you describe though sounds very much like what I understand as setuid / setgid. However, I'm not exactly experienced with this, only have done a bit of reading on the subject. On Mon, Aug 25, 2014 at 4:00 AM, <[email protected]> wrote: > On Monday, 11 August 2014 00:58:36 UTC+1, William Hermans wrote: > >> Never allow a Nodejs process that faces the internet to run as root. >> *EVER*. That's #1 rule. >> > > So is there a way that a node.js process could start as root, configure > the hardware using bonescript functions, change to a non-privileged user > ID, start a server listening on a port >3000, and still use bonescript to > access the IO pins themselves? If so, how? Anyone? > > Max > > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
