[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: |
Thu, 01 Jun 2006 15:49:44 -0400 |
On Thu, 2006-06-01 at 21:33 +0200, Michal Suchanek wrote:
> On 5/29/06, Pierre THIERRY <address@hidden> wrote:
>
> > In general, some capabilities typically given by the constructor need
> > only to be read-only, for example the TCB ones, like to the
> > meta-constructor and the constructor. Though in some virtualization
> > cases, they also should be unreadable. (Jonathan, I think I'm starting
> > to understand why you think that disclosure should not be the default)
>
> I don't see why there has to be always a capability that is provided
> by the constructor.
As I stated in a previous message, there *aren't* any such magic
capabilities provided by the constructor.
shap
- Re: Restricted storage, (continued)
- Re: Restricted storage, Jonathan S. Shapiro, 2006/06/01
- RE: Restricted storage, Christopher Nelson, 2006/06/05
- Re: Restricted storage, Marcus Brinkmann, 2006/06/05
- RE: Restricted storage, Christopher Nelson, 2006/06/05
- Re: Restricted storage, Marcus Brinkmann, 2006/06/05
Re: Restricted storage, Marcus Brinkmann, 2006/06/01
Re: Restricted storage, Pierre THIERRY, 2006/06/01
Re: Restricted storage, Lluis, 2006/06/01
Re: Restricted storage, Michal Suchanek, 2006/06/01
- Re: Restricted storage,
Jonathan S. Shapiro <=
Re: Restricted storage, Tom Bachmann, 2006/06/02