On Monday 01 September 2008, walt wrote: > Frank Mehnert wrote: > > Instead of editing LocalConfig.kmk there is now a configure option > > for disabling this setuid requirement: > > > > ./configure --disable-hardened > > > > Make sure you update any udev rules and reload the right vboxdrv > > after build it like this, otherwise it won't run (you'll get access > > denied errors). > > For the record, it's ./configure --disable-hardening, but it does the > job. Thanks very much.
This is now better documented if configure is started without any argument. > Is there an on-line discussion of why the hardening feature was started > and/or who would want to use it? (If the discussion has been in this > mailing list then it's well disguised :o) The hardening feature ensures that only trusted modules can be loaded by the VM. Kind regards, Frank -- Dr.-Ing. Frank Mehnert Sun Microsystems http://www.sun.com/
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ vbox-dev mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-dev
