Dazo-org/zerovm — Issue #8: Defense in depth
Author: camuel
Created: 2011-11-29 20:52:41+00:00
State: open
Labels: MINOR

In addition to NaCl derived isolation, ZeroVM must take all available to it measures to guard the system from NEXE and minimize damage of unlikely but possible breach (for example as result of human error/negligence).

I see following measures are straightforward to implement:

1. Nice, ZeroVM must lower its priority so NEXE will be easily preempted. For number crunching lower priority is healthy so it will not affect Swift responsiveness. Call: 'result = nice(1)', type 'man 2 nice' for documentation for nice.

2. Lower hardlimits with setrlimit functions.

3. Just before transferring control to NEXE delete all sensitive and/or unneeded information from the process address space. We don't have now any encryption keys or something other... but may have in future.