If this was to be extended with cached global syscall information like
gettimeofday, would we want that to be in a separate page that is marked
non-executable? Is there any way to trick the kernel into leaking arbitrary
(and thus executable) code? Also, would it matter for jails? Per-process
If this was to be extended with cached global syscall information like
gettimeofday, would we want that to be in a separate page that is marked
non-executable? Is there any way to trick the kernel into leaking arbitrary
(and thus executable) code? Also, would it matter for jails?
On Jun 15, 2011, at 6:44 PM, Julian Elischer wrote:
If this was to be extended with cached global syscall information like
gettimeofday, would we want that to be in a separate page that is marked
non-executable? Is there any way to trick the kernel into leaking arbitrary
(and thus
On Jun 15, 2011, at 6:44 PM, Julian Elischer wrote:
If this was to be extended with cached global syscall information like
gettimeofday, would we want that to be in a separate page that is marked
non-executable? Is there any way to trick the kernel into leaking arbitrary
(and thus
On Tue, Jun 14, 2011 at 6:08 PM, K. Macy km...@freebsd.org wrote:
http://svnweb.freebsd.org/base/head/sys/sys/imgact.h
kib added rudimentary support for this in January
To clarify, this is just the kernel side of the shared page
infrastructure, and is currently only hosting the the signal
http://svnweb.freebsd.org/base/head/sys/sys/imgact.h
kib added rudimentary support for this in January
On Tue, Jun 14, 2011 at 6:11 PM, Luigi Rizzo ri...@iet.unipi.it wrote:
there were discussions at some point on an imprecise but
fast implementations of gettimeofday() that would not require
