From: Eric Biggers <ebiggers@kernel.org>
To: Tobias Brunner <tobias@strongswan.org>
Cc: netdev@vger.kernel.org, linux-crypto@vger.kernel.org,
Corentin Labbe <clabbe@baylibre.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Herbert Xu <herbert@gondor.apana.org.au>,
Steffen Klassert <steffen.klassert@secunet.com>
Subject: Re: [PATCH net v3 3/3] esp, ah: modernize the crypto algorithm selections
Date: Wed, 10 Jun 2020 08:53:12 -0700 [thread overview]
Message-ID: <20200610155312.GB1339@sol.localdomain> (raw)
In-Reply-To: <c87f1edb-4130-a4a9-2915-ae5d55302f0a@strongswan.org>
On Wed, Jun 10, 2020 at 11:03:55AM +0200, Tobias Brunner wrote:
> Hi Eric,
>
> > + Note that RFC 8221 considers AH itself to be "NOT RECOMMENDED". It is
> > + better to use ESP only, using an AEAD cipher such as AES-GCM.
>
> What's NOT RECOMMENDED according to the RFC is the combination of ESP+AH
> (i.e. use ESP only for confidentiality and AH for authentication), not
> AH by itself (although the RFC keeps ENCR_NULL as a MUST because ESP
> with NULL encryption is generally preferred over AH due to NATs).
>
> Regards,
> Tobias
Okay, I'll drop this paragraph. I'm surprised that authentication-only is still
considered a valid use case though.
- Eric
prev parent reply other threads:[~2020-06-10 15:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 0:53 [PATCH net v3 0/3] esp, ah: improve crypto algorithm selections Eric Biggers
2020-06-10 0:54 ` [PATCH net v3 1/3] esp, ah: consolidate the " Eric Biggers
2020-06-10 1:00 ` Herbert Xu
2020-06-10 0:54 ` [PATCH net v3 2/3] esp: select CRYPTO_SEQIV Eric Biggers
2020-06-10 1:01 ` Herbert Xu
2020-06-10 0:54 ` [PATCH net v3 3/3] esp, ah: modernize the crypto algorithm selections Eric Biggers
2020-06-10 1:01 ` Herbert Xu
2020-06-10 9:03 ` Tobias Brunner
2020-06-10 15:53 ` Eric Biggers [this message]
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=20200610155312.GB1339@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=clabbe@baylibre.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--cc=tobias@strongswan.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