On Fri, 2014-03-14 at 17:14 +, David Howells wrote:
> Mimi Zohar wrote:
>
> > > As I understand the code, I think operations being performed from
> > > ->update()
> > > are:
> > >
> > > (a) Resealing a key with a new pcrs (trusted).
> > >
> > > (b) Changing the master key (encrypted).
>
Mimi Zohar wrote:
> > As I understand the code, I think operations being performed from ->update()
> > are:
> >
> > (a) Resealing a key with a new pcrs (trusted).
> >
> > (b) Changing the master key (encrypted).
> >
> > Mimi, Dmitry: is this list right?
>
> In addition to resealing trusted
On Thu, 2014-03-13 at 15:47 +, David Howells wrote:
> Hi Linus,
>
> I've encountered a situation where I could do with providign certain key types
> with their own operations and I'm wondering as to the best way.
>
> The problem I've been trying to deal with is to improve quota management on
On Thu, 2014-03-13 at 16:17 +, David Howells wrote:
> David Howells wrote:
>
> > I can fix this in one of a number of ways:
> >
> > (1) Provide a generic control operation (analogous with ioctl()) that
> > allows
> > the user to make some general operation on a key (querying it, alte
David Howells wrote:
> I can fix this in one of a number of ways:
>
> (1) Provide a generic control operation (analogous with ioctl()) that allows
> the user to make some general operation on a key (querying it, altering
> it, interacting with hardware).
>
> (2) Provide an alter ope
Hi Linus,
I've encountered a situation where I could do with providign certain key types
with their own operations and I'm wondering as to the best way.
The problem I've been trying to deal with is to improve quota management on
keys and introduce LRU key discard when a quota is overrun. This r
6 matches
Mail list logo
