[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180117180537.GB6948@thunk.org>
Date: Wed, 17 Jan 2018 13:05:37 -0500
From: Theodore Ts'o <tytso@....edu>
To: André Draszik <git@...red.net>
Cc: Eric Biggers <ebiggers3@...il.com>, linux-kernel@...r.kernel.org,
Mimi Zohar <zohar@...ux.vnet.ibm.com>,
David Howells <dhowells@...hat.com>,
James Morris <james.l.morris@...cle.com>,
"Serge E. Hallyn" <serge@...lyn.com>,
Jaegeuk Kim <jaegeuk@...nel.org>,
Jonathan Corbet <corbet@....net>,
Kees Cook <keescook@...omium.org>,
linux-integrity@...r.kernel.org, keyrings@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-fscrypt@...r.kernel.org, linux-doc@...r.kernel.org
Subject: Re: [PATCH 3/3] encrypted-keys: document new fscrypt key format
On Wed, Jan 17, 2018 at 02:38:59PM +0000, André Draszik wrote:
> > > [...]
> >
> > Please be very clear about exactly what security properties are achieved
> > by
> > using encrypted-keys.
>
> I've left out all of this in the updated documentation, as any such
> information should probably be in Documentation/security/keys/trusted-
> encrypted.rst in the first place.
Where is this document going to be found / when will it be written?
It seems really odd to be requesting a do code review when the
specifications aren't available and/or haven't been written yet. I
prefer to review the *design* first, as opposed to trying to both
review the code and try to guess at the design and review my guess of
the design at the same time....
- Ted
Powered by blists - more mailing lists