[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200826120832.GA2996@gondor.apana.org.au>
Date: Wed, 26 Aug 2020 22:08:32 +1000
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Ard Biesheuvel <ardb@...nel.org>
Cc: Paul Menzel <pmenzel@...gen.mpg.de>,
Caleb Jorden <caljorden@...mail.com>,
Sasha Levin <sashal@...nel.org>, iwd@...ts.01.org,
"# 3.4.x" <stable@...r.kernel.org>,
Greg KH <gregkh@...uxfoundation.org>,
LKML <linux-kernel@...r.kernel.org>,
"David S. Miller" <davem@...emloft.net>,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>
Subject: Re: Issue with iwd + Linux 5.8.3 + WPA Enterprise
On Wed, Aug 26, 2020 at 01:59:53PM +0200, Ard Biesheuvel wrote:
> On Wed, 26 Aug 2020 at 13:50, Herbert Xu <herbert@...dor.apana.org.au> wrote:
> >
> > On Wed, Aug 26, 2020 at 12:40:14PM +0200, Ard Biesheuvel wrote:
> > >
> > > It would be helpful if someone could explain for the non-mac80211
> > > enlightened readers how iwd's EAP-PEAPv0 + MSCHAPv2 support relies on
> > > the algif_aead socket interface, and which AEAD algorithms it uses. I
> > > assume this is part of libell?
> >
> > I see the problem. libell/ell/checksum.c doesn't clear the MSG_MORE
> > flag before doing the recv(2).
>
> But that code uses a hash not an aead, afaict.
Good point. In that case can we please get a strace with a -s
option that's big enough to capture the crypto data?
Comparing the working strace and the non-working one should be
sufficient to identify the problem.
Thanks,
--
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Powered by blists - more mailing lists