Re: Pony talks about Deny Capabilities

On 11 May 2015 at 23:04, Mark Miller <[email protected]> wrote:
>
> E approached this problem by starting with the Java APIs, which already
put an oo skin over the various OSes, and therefore saved us much work. We
then "only" had to close the gap between their oo principles and ocap
principles. Although you are not starting with Java, you should be able to
learn lessons from this effort.
>
> See:
> https://code.google.com/p/joe-e/wiki/Taming
> http://www.combex.com/papers/darpa-review/security-review.html#taming
> http://www.erights.org/elib/legacy/taming.html
>
> Compare:
> http://erights.org/javadoc/java/io/File.html
> vs
> http://www.cs.berkeley.edu/~daw/joe-e/api/java/io/File.html

Fantastic, thanks. The stuff on erights.org I had read before, but will
read again. The rest is new to me.

> Without help from the OS, there's only so much a language can do.

Fair enough.

> IIUC, see
> http://erights.org/elang/io/uri-exprs.html
> with
> http://www.erights.org/data/serial/jhu-paper/exit-security.html
> as an example of unprivileged user code creating new uri "roots".
>
> Though I am not sure I understand your question.
> Is this the kind of thing you have in mind?

I'm not sure yet, but I'll read further and find out!

-s

_______________________________________________
cap-talk mailing list
[email protected]
http://www.eros-os.org/mailman/listinfo/cap-talk