[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Restricted storage
From: |
Jonathan S. Shapiro |
Subject: |
Re: Restricted storage |
Date: |
Mon, 29 May 2006 15:15:15 -0400 |
On Mon, 2006-05-29 at 11:27 +0200, Bas Wijnen wrote:
> On Mon, May 29, 2006 at 11:16:10AM +0200, Bas Wijnen wrote:
> > There is one very important point though. I think those restrictions can
> > easily be implemented in the user session. This means that we can just
> > build
> > a system with no support for restricted storage, and add it if we find that
> > we
> > did need it after all. However, Jonathan doesn't seem to agree. At the
> > moment I still think he doesn't quite understand what I mean. However, if
> > he
> > does and is correct that it cannot be added later, we would need to decide
> > this before building the system.
>
> Oh, and I forgot one thing. I'm very sure that I do indeed want the user to
> be able to run his own programs on fully opaque storage. This is very useful
> for programs handling encryption keys....
I seem to recall that this was one of the very first use cases that I
pointed out.
shap
- Restricted storage, Bas Wijnen, 2006/05/29
- Re: Restricted storage, Bas Wijnen, 2006/05/29
- Re: Restricted storage,
Jonathan S. Shapiro <=
- Re: Restricted storage, Bas Wijnen, 2006/05/29
- RE: Restricted storage, Christopher Nelson, 2006/05/31
- RE: Restricted storage, Jonathan S. Shapiro, 2006/05/31
- Re: Restricted storage, Bas Wijnen, 2006/05/31
- Re: Restricted storage, Eric Northup, 2006/05/31
- Re: Restricted storage, Jonathan S. Shapiro, 2006/05/31
- Re: Restricted storage, Pierre THIERRY, 2006/05/31
Re: Restricted storage, Marcus Brinkmann, 2006/05/29
Re: Restricted storage, Pierre THIERRY, 2006/05/29