> > *Actually, I wouldn't do this.* > I totally would, because it's a test, not a production environment.
* If a program is badly written to the point that it segfaults because of* > *a lack of permissions I wouldn't trust it with root permissions where* > *all of its bugs can be exploited to become security vulnerabilities with* > *maximum damage.* > This is standard behavior when you're trying to run a program that attempts to use a device that requires elevated permissions to use(but doesn't currently have). For example, if you run the test applications for any of the PRU examples, and you do not run these with root permissions, they *will* seg fault. However, once something like this is found, by way of testing, or whatever. This is really easy to fix by adding 2 lines of code, or 3 lines if you require the executable to print out why it failed. You can also setup a udev rule / policy that allows a regular user to be part of a group, or otherwise have access to this asset. I think that ideally, really, both of these situations would be preferred. App permission check, and some form of GUID access for the user in question( non root ). On Wed, Jan 13, 2016 at 2:56 AM, Elena ``of Valhalla'' < [email protected]> wrote: > On 2016-01-12 at 11:35:21 -0700, William Hermans wrote: > > No idea what docker is, and do not care. But . . . many applications that > > do not check to user type in Linux will fail with "segmentation fault . . > > ." if they require elevated permissions, and non are given. > > > > So . . . in other words. Run your command with sudo. This is not a > > guaranteed fix, but at least worth checking. > > Actually, I wouldn't do this. > > If a program is badly written to the point that it segfaults because of > a lack of permissions I wouldn't trust it with root permissions where > all of its bugs can be exploited to become security vulnerabilities with > maximum damage. > > -- > Elena ``of Valhalla'' > > -- > 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.
