From: Johannes Berg <johannes@sipsolutions.net>
To: Karel Balej <balejk@matfyz.cz>, dimitri.ledkov@canonical.com
Cc: alexandre.torgue@foss.st.com, davem@davemloft.net,
dhowells@redhat.com, herbert@gondor.apana.org.au,
keyrings@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-modules@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com, mcgrof@kernel.org,
mcoquelin.stm32@gmail.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, iwd@lists.linux.dev
Subject: Re: [REGRESSION] Re: [PATCH] crypto: pkcs7: remove sha1 support
Date: Wed, 13 Mar 2024 09:56:53 +0100 [thread overview]
Message-ID: <005f998ec59e27633b1b99fdf929e40ccfd401c1.camel@sipsolutions.net> (raw)
In-Reply-To: <CZSHRUIJ4RKL.34T4EASV5DNJM@matfyz.cz>
Not sure why you're CC'ing the world, but I guess adding a few more
doesn't hurt ...
On Wed, 2024-03-13 at 09:50 +0100, Karel Balej wrote:
>
> and I use iwd
This is your problem, the wireless stack in the kernel doesn't use any
kernel crypto code for 802.1X.
I suppose iwd wants to use the kernel infrastructure but has no
fallbacks to other implementations.
johannes
WARNING: multiple messages have this Message-ID (diff)
From: Johannes Berg <johannes@sipsolutions.net>
To: Karel Balej <balejk@matfyz.cz>, dimitri.ledkov@canonical.com
Cc: alexandre.torgue@foss.st.com, davem@davemloft.net,
dhowells@redhat.com, herbert@gondor.apana.org.au,
keyrings@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-modules@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com, mcgrof@kernel.org,
mcoquelin.stm32@gmail.com, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org, iwd@lists.linux.dev
Subject: Re: [REGRESSION] Re: [PATCH] crypto: pkcs7: remove sha1 support
Date: Wed, 13 Mar 2024 09:56:53 +0100 [thread overview]
Message-ID: <005f998ec59e27633b1b99fdf929e40ccfd401c1.camel@sipsolutions.net> (raw)
In-Reply-To: <CZSHRUIJ4RKL.34T4EASV5DNJM@matfyz.cz>
Not sure why you're CC'ing the world, but I guess adding a few more
doesn't hurt ...
On Wed, 2024-03-13 at 09:50 +0100, Karel Balej wrote:
>
> and I use iwd
This is your problem, the wireless stack in the kernel doesn't use any
kernel crypto code for 802.1X.
I suppose iwd wants to use the kernel infrastructure but has no
fallbacks to other implementations.
johannes
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-03-13 8:57 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 21:22 [PATCH] crypto: pkcs7: remove sha1 support Dimitri John Ledkov
2023-10-10 21:22 ` Dimitri John Ledkov
2023-10-20 5:54 ` Herbert Xu
2023-10-20 5:54 ` Herbert Xu
2024-03-13 8:50 ` [REGRESSION] " Karel Balej
2024-03-13 8:50 ` Karel Balej
2024-03-13 8:56 ` Johannes Berg [this message]
2024-03-13 8:56 ` Johannes Berg
2024-03-13 17:26 ` James Prestwood
2024-03-13 17:26 ` James Prestwood
2024-03-13 19:44 ` Eric Biggers
2024-03-13 19:44 ` Eric Biggers
2024-03-13 20:12 ` James Prestwood
2024-03-13 20:12 ` James Prestwood
2024-03-13 20:22 ` Eric Biggers
2024-03-13 20:22 ` Eric Biggers
2024-03-13 21:17 ` James Prestwood
2024-03-13 21:17 ` James Prestwood
2024-03-13 22:10 ` Eric Biggers
2024-03-13 22:10 ` Eric Biggers
2024-03-13 22:51 ` Jeff Johnson
2024-03-13 22:51 ` Jeff Johnson
2024-03-13 23:06 ` Eric Biggers
2024-03-13 23:06 ` Eric Biggers
2024-03-13 23:40 ` Eric Biggers
2024-03-13 23:40 ` Eric Biggers
2024-03-14 11:52 ` James Prestwood
2024-03-14 11:52 ` James Prestwood
2024-03-14 12:22 ` James Bottomley
2024-03-14 12:22 ` James Bottomley
2024-03-14 20:20 ` Eric Biggers
2024-03-14 20:20 ` Eric Biggers
2024-03-14 23:38 ` Ard Biesheuvel
2024-03-14 23:38 ` Ard Biesheuvel
2024-03-13 18:39 ` Michael Yartys
2024-03-13 18:39 ` Michael Yartys
2024-03-13 19:54 ` Karel Balej
2024-03-13 19:54 ` Karel Balej
2024-03-15 13:09 ` Karel Balej
2024-03-15 13:09 ` Karel Balej
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=005f998ec59e27633b1b99fdf929e40ccfd401c1.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=alexandre.torgue@foss.st.com \
--cc=balejk@matfyz.cz \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dimitri.ledkov@canonical.com \
--cc=herbert@gondor.apana.org.au \
--cc=iwd@lists.linux.dev \
--cc=keyrings@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@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.