[vbox-dev] hardening feature

[Felix morack]

Like so many people i am still running 4.12 due to the "hardening" issues.
yes, i reported a bunch of them back when we first started, and yes i have
since tested all versions up to 4.18. We are now nearing a point where i
cant deploy 4.12 anymore due to formal security regulations, so i have to
get serious about this now.

I am therefore looking for a detailed, technical description of this new
'feature' and why devs think it is necessary.

Yes, i have the code, but a high level reasoning would be very helpful,
especially what has changed with version 4.12. Specifically i am looking
for documentation "between" the source code and the manual. Does such a
documentation exist in public? Any technical discussion of it perhaps?

Background is that i am think about deploying my own custom build with
hardening disabled. Which is pretty insane, but there is no chance in hell
anything post 4.12 ends up even in proximity to systems whose stability i
am responsible for.

tb

p.s. does vmware have such a feature? How do they handle it?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.virtualbox.org/pipermail/vbox-dev/attachments/20141111/99900a5e/attachment.html>