From: David Howells <dhowells@redhat.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: dhowells@redhat.com, "Jason A. Donenfeld" <Jason@zx2c4.com>,
keyrings@vger.kernel.org, kernel-hardening@lists.openwall.com,
LKML <linux-kernel@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>,
Herbert Xu <herbert@gondor.apana.org.au>,
Kirill Marinushkin <k.marinushkin@gmail.com>,
security@kernel.org
Subject: [kernel-hardening] Re: [PATCH v2] security/keys: rewrite all of big_key crypto
Date: Wed, 07 Jun 2017 08:31:09 +0100 [thread overview]
Message-ID: <29551.1496820669@warthog.procyon.org.uk> (raw)
In-Reply-To: <20170607042219.GC594@zzz>
Eric Biggers <ebiggers3@gmail.com> wrote:
> but I skipped the big_key type because it was one of the more obscure key
> types (and frankly I have no idea what, if anything, actually uses it)
Kerberos can use it.
David
WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: dhowells@redhat.com, "Jason A. Donenfeld" <Jason@zx2c4.com>,
keyrings@vger.kernel.org, kernel-hardening@lists.openwall.com,
LKML <linux-kernel@vger.kernel.org>,
Theodore Ts'o <tytso@mit.edu>,
Herbert Xu <herbert@gondor.apana.org.au>,
Kirill Marinushkin <k.marinushkin@gmail.com>,
security@kernel.org
Subject: Re: [PATCH v2] security/keys: rewrite all of big_key crypto
Date: Wed, 07 Jun 2017 07:31:09 +0000 [thread overview]
Message-ID: <29551.1496820669@warthog.procyon.org.uk> (raw)
In-Reply-To: <20170607042219.GC594@zzz>
Eric Biggers <ebiggers3@gmail.com> wrote:
> but I skipped the big_key type because it was one of the more obscure key
> types (and frankly I have no idea what, if anything, actually uses it)
Kerberos can use it.
David
WARNING: multiple messages have this Message-ID (diff)
From: David Howells <dhowells@redhat.com>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: dhowells@redhat.com, "Jason A. Donenfeld" <Jason@zx2c4.com>,
keyrings@vger.kernel.org, kernel-hardening@lists.openwall.com,
LKML <linux-kernel@vger.kernel.org>,
"Theodore Ts'o" <tytso@mit.edu>,
Herbert Xu <herbert@gondor.apana.org.au>,
Kirill Marinushkin <k.marinushkin@gmail.com>,
security@kernel.org
Subject: Re: [PATCH v2] security/keys: rewrite all of big_key crypto
Date: Wed, 07 Jun 2017 08:31:09 +0100 [thread overview]
Message-ID: <29551.1496820669@warthog.procyon.org.uk> (raw)
In-Reply-To: <20170607042219.GC594@zzz>
Eric Biggers <ebiggers3@gmail.com> wrote:
> but I skipped the big_key type because it was one of the more obscure key
> types (and frankly I have no idea what, if anything, actually uses it)
Kerberos can use it.
David
next prev parent reply other threads:[~2017-06-07 7:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-06 21:51 [kernel-hardening] [PATCH v2] security/keys: rewrite all of big_key crypto Jason A. Donenfeld
2017-06-06 21:51 ` Jason A. Donenfeld
2017-06-06 21:51 ` Jason A. Donenfeld
2017-06-07 4:22 ` [kernel-hardening] " Eric Biggers
2017-06-07 4:22 ` Eric Biggers
2017-06-07 4:22 ` Eric Biggers
2017-06-07 7:10 ` [kernel-hardening] " Herbert Xu
2017-06-07 7:10 ` Herbert Xu
2017-06-07 7:10 ` Herbert Xu
2017-06-07 7:31 ` David Howells [this message]
2017-06-07 7:31 ` David Howells
2017-06-07 7:31 ` David Howells
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=29551.1496820669@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=Jason@zx2c4.com \
--cc=ebiggers3@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=k.marinushkin@gmail.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=security@kernel.org \
--cc=tytso@mit.edu \
/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.