From: Eric Biggers <ebiggers@google.com>
To: gregkh@linuxfoundation.org
Cc: herbert@gondor.apana.org.au, syzkaller@googlegroups.com,
stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "crypto: hash - prevent using keyed hashes without setting key" has been added to the 4.9-stable tree
Date: Wed, 14 Feb 2018 11:12:24 -0800 [thread overview]
Message-ID: <20180214191224.GB221549@google.com> (raw)
In-Reply-To: <1518634738133174@kroah.com>
On Wed, Feb 14, 2018 at 07:58:58PM +0100, gregkh@linuxfoundation.org wrote:
>
> This is a note to let you know that I've just added the patch titled
>
> crypto: hash - prevent using keyed hashes without setting key
>
> to the 4.9-stable tree which can be found at:
> http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
>
> The filename of the patch is:
> crypto-hash-prevent-using-keyed-hashes-without-setting-key.patch
> and it can be found in the queue-4.9 subdirectory.
>
> If you, or anyone else, feels it should not be added to the stable tree,
> please let <stable@vger.kernel.org> know about it.
Hi Greg, this patch needs some prerequisites including "crypto: hash - annotate
algorithms taking optional key". You got all the prerequisites for 4.14 and
4.15 but not all applied to earlier kernels, so you should hold off on this for
4.9 and earlier for now. (The prerequisites by themselves shouldn't break
anything though; only this final patch would.) Thanks,
Eric
next prev parent reply other threads:[~2018-02-14 19:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 18:58 Patch "crypto: hash - prevent using keyed hashes without setting key" has been added to the 4.9-stable tree gregkh
2018-02-14 19:12 ` Eric Biggers [this message]
2018-02-14 19:34 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2018-02-23 7:46 gregkh
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=20180214191224.GB221549@google.com \
--to=ebiggers@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzkaller@googlegroups.com \
/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.