linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: torvalds@linux-foundation.org
Cc: dhowells@redhat.com, jarkko.sakkinen@linux.intel.com,
	mathstuf@gmail.com, gustavoars@kernel.org, Jason@zx2c4.com,
	keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [GIT PULL] keys: Changes for 5.8
Date: Tue, 02 Jun 2020 17:28:00 +0100	[thread overview]
Message-ID: <1509351.1591115280@warthog.procyon.org.uk> (raw)

Hi Linus,

Could you pull these keyrings fixes please?

 (1) Fix a documentation warning.

 (2) Replace a [0] array with [].

 (3) Make the big_key key type use ChaCha20Poly1305 and use the crypto
     algorithm directly rather than going through the crypto layer.

 (4) Implement the update op for the big_key type.

Thanks,
David
---
The following changes since commit 6a8b55ed4056ea5559ebe4f6a4b247f627870d4c:

  Linux 5.7-rc3 (2020-04-26 13:51:02 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/keys-next-20200602

for you to fetch changes up to b6f61c31464940513ef4eccb3a030a405b4256d6:

  keys: Implement update for the big_key type (2020-06-02 17:22:31 +0100)

----------------------------------------------------------------
Keyrings changes

----------------------------------------------------------------
Ben Boeckel (1):
      Documentation: security: core.rst: add missing argument

David Howells (1):
      keys: Implement update for the big_key type

Gustavo A. R. Silva (1):
      KEYS: Replace zero-length array with flexible-array

Jason A. Donenfeld (1):
      security/keys: rewrite big_key crypto to use library interface

 Documentation/security/keys/core.rst |   8 +-
 include/keys/big_key-type.h          |   1 +
 include/keys/user-type.h             |   2 +-
 security/keys/Kconfig                |   4 +-
 security/keys/big_key.c              | 257 +++++++----------------------------
 5 files changed, 60 insertions(+), 212 deletions(-)


             reply	other threads:[~2020-06-02 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-02 16:28 David Howells [this message]
2020-06-04 17:35 ` [GIT PULL] keys: Changes for 5.8 pr-tracker-bot

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=1509351.1591115280@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=Jason@zx2c4.com \
    --cc=gustavoars@kernel.org \
    --cc=jarkko.sakkinen@linux.intel.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=mathstuf@gmail.com \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).