[cap-talk] Confessions of a C programmer

Ben Kloosterman bklooste at gmail.com
Wed Sep 23 04:05:54 PDT 2009


Gets down to the definition of interpreter as well , most  Java run times
now use JITs and as they cache the compilation result and reuse the compiled
code and hence dynamic checks are only valid against the state when it was
first compiled.

>-----Original Message-----
>From: cap-talk-bounces at mail.eros-os.org [mailto:cap-talk-
>bounces at mail.eros-os.org] On Behalf Of Ka-Ping Yee
>Sent: Wednesday, September 23, 2009 5:28 PM
>To: rmeijer at xs4all.nl; General discussions concerning capability systems.
>Subject: Re: [cap-talk] Confessions of a C programmer
>
>On Wed, 23 Sep 2009, Rob Meijer wrote:
>> Would there also be considerations that would favor an interpreter over
>a
>> compiler when looking at verifying security properties?
>
>An interpreter can perform security checks against the dynamic state
>of the running program -- checks that might be hard or impossible to
>anticipate through static analysis.  The interpreter wouldn't give you
>these guarantees ahead of time, but it could guarantee that programs
>violating the constraints would abort rather than running in violation.
>
>
>-- ?!ng
>_______________________________________________
>cap-talk mailing list
>cap-talk at mail.eros-os.org
>http://www.eros-os.org/mailman/listinfo/cap-talk



More information about the cap-talk mailing list