If we create gpio/pinmux group, I think we could keep from burdening users while moving Cloud9 IDE to the 'debian' user. I believe we also have a sudoers for the 'debian' user, meaning we could probably at that point prevent direct root login unless someone does something to disable the root password. I'd worry about that breaking things like LabVIEW, etc., but if we can at least try out some minor steps towards security, it will at least make everyone more aware of the holes and challenges.
I kind of roughly describe that here: https://github.com/wphermans/Bonejs/blob/master/documentation/permissions.md Although there is much mroe to consider than just the little bit I covered there. But that should be a good start. On Wed, Jul 20, 2016 at 11:00 AM, Jason Kridner < jason.krid...@hangerhead.com> wrote: > > > On Fri, Jun 24, 2016 at 8:10 PM Charles Steinkuehler < > char...@steinkuehler.net> wrote: > >> On 6/24/2016 5:52 PM, William Hermans wrote: >> > /Note the security 'bar' is not set particularly high, given the/ >> > /default BBB images have no root password. :)/ >> > >> > >> > Thats been changed, since at least the last couple of images. >> > > I don't think that's the case---we still have no root password, though one > can be set. The Cloud9 IDE further doesn't require a login. > > If we create gpio/pinmux group, I think we could keep from burdening users > while moving Cloud9 IDE to the 'debian' user. I believe we also have a > sudoers for the 'debian' user, meaning we could probably at that point > prevent direct root login unless someone does something to disable the root > password. I'd worry about that breaking things like LabVIEW, etc., but if > we can at least try out some minor steps towards security, it will at least > make everyone more aware of the holes and challenges. > > >> >> Ahh...that's probably why you were getting the "askpass" errors. >> >> I haven't tried anything more recent than a few months ago. >> >> -- >> Charles Steinkuehler >> char...@steinkuehler.net >> >> -- >> 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 beagleboard+unsubscr...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beagleboard/d19cdd9b-9ae5-08a8-6028-cecbbea7d4f8%40steinkuehler.net >> . >> 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 beagleboard+unsubscr...@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPmBBQk0hy%2Bwz3ktPnaUYNoKC9aSvNK7y-xGDNc7gKaqUg%40mail.gmail.com > <https://groups.google.com/d/msgid/beagleboard/CA%2BT6QPmBBQk0hy%2Bwz3ktPnaUYNoKC9aSvNK7y-xGDNc7gKaqUg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > 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 beagleboard+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORoVNciV7%3DocOW9nxeUvMkvVN_jTnfSgynTDnh-9LemS8g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
