All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Boeckel <mathstuf@gmail.com>
To: keyrings@vger.kernel.org
Subject: [PATCH 0/5] keys: const-ification and other fixes
Date: Thu, 27 Sep 2018 13:14:45 +0000	[thread overview]
Message-ID: <20180927131450.23458-1-mathstuf@gmail.com> (raw)

The main patch is #4, but these are all things I found while using the
code and documentation to make Rust wrappers for `libkeyutils` with
stronger typing.

If it is preferred that these be split up, let me know.

--Ben

Ben Boeckel (5):
  docs: fix prototype for `request_key`
  docs: clarify `keyctl ... trusted` commands
  rxrpc: mention that client key payloads are not arbitrary
  keyctl.h: update pointer types
  dns_key: add a function to verify the key description

 Documentation/security/keys/core.rst          |  2 +-
 .../security/keys/trusted-encrypted.rst       | 20 ++++-----
 include/uapi/linux/keyctl.h                   |  4 +-
 net/dns_resolver/dns_key.c                    | 44 +++++++++++++++----
 net/rxrpc/key.c                               |  4 +-
 5 files changed, 50 insertions(+), 24 deletions(-)

-- 
2.17.1

                 reply	other threads:[~2018-09-27 13:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180927131450.23458-1-mathstuf@gmail.com \
    --to=mathstuf@gmail.com \
    --cc=keyrings@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.