From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1166153AbdEAOst (ORCPT ); Mon, 1 May 2017 10:48:49 -0400 Received: from wtarreau.pck.nerim.net ([62.212.114.60]:47337 "EHLO 1wt.eu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1165477AbdEAOsk (ORCPT ); Mon, 1 May 2017 10:48:40 -0400 Date: Mon, 1 May 2017 16:48:35 +0200 From: Willy Tarreau To: "Jason A. Donenfeld" Cc: stable@vger.kernel.org, LKML , Linux Crypto Mailing List , security@kernel.org Subject: Re: crypto_memneq not backported to 3.10 Message-ID: <20170501144835.GA20339@1wt.eu> References: <20170409132514.GA3970@1wt.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.6.1 (2016-04-27) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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