[lkml]   [2012]   [Mar]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Patch in this message
    Subject[PATCH 2/9] keys: update the description with info about "logon" keys
    From: Jeff Layton <>

    Signed-off-by: Jeff Layton <>
    Signed-off-by: David Howells <>

    Documentation/security/keys.txt | 15 ++++++++++++++-
    1 files changed, 14 insertions(+), 1 deletions(-)

    diff --git a/Documentation/security/keys.txt b/Documentation/security/keys.txt
    index 7877170..4c8cf36 100644
    --- a/Documentation/security/keys.txt
    +++ b/Documentation/security/keys.txt
    @@ -123,7 +123,7 @@ KEY SERVICE OVERVIEW

    The key service provides a number of features besides keys:

    - (*) The key service defines two special key types:
    + (*) The key service defines three special key types:

    (+) "keyring"

    @@ -137,6 +137,19 @@ The key service provides a number of features besides keys:
    blobs of data. These can be created, updated and read by userspace,
    and aren't intended for use by kernel services.

    + (+) "logon"
    + Like a "user" key, a "logon" key has a payload that is an arbitrary
    + blob of data. It is intended as a place to store secrets that the
    + to which the kernel should have access but that should not be
    + accessable from userspace.
    + The description can be arbitrary, but must be prefixed with a non-zero
    + length string that describes the key "subclass". The subclass is
    + separated from the rest of the description by a ':'. "logon" keys can
    + be created and updated by userspace, but the payload is only readable
    + from kernel space.
    (*) Each process subscribes to three keyrings: a thread-specific keyring, a
    process-specific keyring, and a session-specific keyring.

     \ /
      Last update: 2012-03-28 12:51    [W:0.036 / U:10.808 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site