Re: [PATCH 3/3] net: rxrpc: Replace time_t type with time64_t type

From	David Howells <dhowells@redhat.com>
Newsgroups	linux.kernel
Subject	Re: [PATCH 3/3] net: rxrpc: Replace time_t type with time64_t type
Date	2017-08-09 17:50 +0200
Message-ID	<ucBp7-PO-9@gated-at.bofh.it> (permalink)
References	(3 earlier) <ucva3-4Y5-17@gated-at.bofh.it> <ucvD4-5jn-27@gated-at.bofh.it> <ucw66-5Jg-27@gated-at.bofh.it> <uczdE-7A3-17@gated-at.bofh.it> <ucAW5-Gt-15@gated-at.bofh.it>
Organization	Red Hat UK Ltd. Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 3798903

Show all headers | View raw

Arnd Bergmann <arnd@arndb.de> wrote:

> Ah, I'm slowly starting to understand how this fits together. So you can add
> a key either through key_add() from local user space, or through an rxrpc
> socket.

No, you can't add keys through an rxrpc socket.

There are three 'classes' of key:

 (1) Client keys (type rxrpc).  These must be added by add_key() by userspace
     (but could also be acquired by upcalling to /sbin/request-key) and then
     the kernel calls request_key() to locate them on entry through either a
     kafs inode/file operation or through sendmsg() to an AF_RXRPC socket.

 (2) Server keys (type rxrpc_s).  These are created by userspace and are
     presented to an AF_RXRPC server socket by calling setsockopt().  The
     server uses these to validate/decrypt the token passed by a RESPONSE
     packet.

 (3) Service connection keys (type rxrpc).  These are created internally by
     AF_RXRPC after a successful challenge/response negotiation to hold the
     security details so that we have a struct key to pass around that
     corresponds to the key in (1).

David

Thread

[PATCH 0/3] Fix y2038 issues for security/keys subsystem Baolin Wang <baolin.wang@linaro.org> - 2017-08-09 05:00 +0200
  [PATCH 2/3] security: keys: Replace time_t with time64_t for struct key_preparsed_payload Baolin Wang <baolin.wang@linaro.org> - 2017-08-09 05:00 +0200
  [PATCH 3/3] net: rxrpc: Replace time_t type with time64_t type Baolin Wang <baolin.wang@linaro.org> - 2017-08-09 05:00 +0200
    Re: [PATCH 3/3] net: rxrpc: Replace time_t type with time64_t type Arnd Bergmann <arnd@arndb.de> - 2017-08-09 11:10 +0200
      Re: [PATCH 3/3] net: rxrpc: Replace time_t type with time64_t type David Howells <dhowells@redhat.com> - 2017-08-09 11:40 +0200
        Re: [PATCH 3/3] net: rxrpc: Replace time_t type with time64_t type Arnd Bergmann <arnd@arndb.de> - 2017-08-09 12:10 +0200
          Re: [PATCH 3/3] net: rxrpc: Replace time_t type with time64_t type David Howells <dhowells@redhat.com> - 2017-08-09 15:30 +0200
            Re: [PATCH 3/3] net: rxrpc: Replace time_t type with time64_t type Arnd Bergmann <arnd@arndb.de> - 2017-08-09 17:20 +0200
              Re: [PATCH 3/3] net: rxrpc: Replace time_t type with time64_t type David Howells <dhowells@redhat.com> - 2017-08-09 17:50 +0200
  [PATCH 1/3] security: keys: Replace time_t/timespec with time64_t Baolin Wang <baolin.wang@linaro.org> - 2017-08-09 05:00 +0200
  Re: [PATCH 0/3] Fix y2038 issues for security/keys subsystem David Howells <dhowells@redhat.com> - 2017-08-09 10:30 +0200
    Re: [PATCH 0/3] Fix y2038 issues for security/keys subsystem Baolin Wang <baolin.wang@linaro.org> - 2017-08-10 04:10 +0200
  Re: [PATCH 0/3] Fix y2038 issues for security/keys subsystem Arnd Bergmann <arnd@arndb.de> - 2017-08-09 10:50 +0200
    Re: [PATCH 0/3] Fix y2038 issues for security/keys subsystem Baolin Wang <baolin.wang@linaro.org> - 2017-08-10 04:10 +0200

csiph-web