Re: Fwd: Re: [Cryptography] Encryption opinion

On Sep 2, 2014 8:35 AM, "Rob Meijer" <rmeijer-qWit8jRvyhVmR6Xm/[email protected]> wrote:
> You may not actually need a single equality function for that. If the
> scripts on the page are aware of their own equality requirements, you
> could allow for private storage at different granularities of equality
> that the scripts may pick from.

Now you're talking. :) Yes that is an intriguing line of discussion and it
would be really great to design an infrastructure around that. When I've
thought about this, I have thought that a browser should provide to scripts
two things --

1. An Introducer that turns unguessable capability strings into authority
over local storage objects; and

2. A "profile ID" GUID that scripts can use to determine from their server
components which capabilities to try to load on the client side.

Perhaps #2 is not necessary; I don't know.

> > * Pages may grant one another access to local storage by sharing
> > capabilities
>
> Sounds promising, If only I had some more spare time the above two points
> would be a great use-case for a ChromeOS fork that uses my (slowly)
> ongoing work on RumpelstiltskinFs and friends ;-) Unfortunately my
> spare-time night already be to small at the moment to even finish
> RumpelstiltskinFs itself any time soon :-(

If only we all had time. I'll look at RumpelstiltsinkFs ... never heard of
that before.

The key here -- and that's what led me to my second line of thinking
upthread, the one that I withdrew -- is that, under these circumstances,
the Web browser becomes a powerbox, granting not only local authorities
(the camera, etc.) but also mediating and keeping track of the grants
between one page and another, a la the Web Introducer.

In this new same-origin-free world, we'd need to come up with some way to
assign responsibility for capabilities granted -- "to whom" where they
granted? What set of pages | objects | UI affordances should we now assume
can wield capability C?

And if these pages embed third-party objects of their own, they are then
acting as nested powerboxes. How can we best represent that, short of just
nested visual boxes within boxes within boxes?

Ihab

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