All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: stable@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Linux Crypto Mailing List <linux-crypto@vger.kernel.org>,
	security@kernel.org
Subject: Re: crypto_memneq not backported to 3.10
Date: Mon, 1 May 2017 16:48:35 +0200	[thread overview]
Message-ID: <20170501144835.GA20339@1wt.eu> (raw)
In-Reply-To: <CAHmME9r9Jj=WtQxhxqtwWHFxwJV6KzMWO7qdsvhfG8R3B1qbJw@mail.gmail.com>

Hi Jason,

On Mon, May 01, 2017 at 04:30:01PM +0200, Jason A. Donenfeld wrote:
> > I'll check if the 3.12 patches above can be safely backported, and I'll
> > have to re-apply the missing part of the one that was trimmed down
> > (commit 620c411 ("crypto: more robust crypto_memneq")).
> 
> I'm vaguely wondering if you ever decided on backporting this. After I
> reported the issue to Ubiquiti -- a random vendor doing ipsec with
> 3.10 -- they actually released a backport of these functions in a
> security update for their stuff. So I imagine others might want this
> sort of thing too.

I'll do it. It just happens that I've been quite busy lately so
no new 3.10 was released since you reported this ~1 month ago. I'll
get back to this ASAP.

Thanks for the heads up,
Willy

      reply	other threads:[~2017-05-01 14:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-09 12:59 crypto_memneq not backported to 3.10 Jason A. Donenfeld
2017-04-09 13:25 ` Willy Tarreau
2017-05-01 14:30   ` Jason A. Donenfeld
2017-05-01 14:48     ` Willy Tarreau [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=20170501144835.GA20339@1wt.eu \
    --to=w@1wt.eu \
    --cc=Jason@zx2c4.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=security@kernel.org \
    --cc=stable@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.