hello,
On Wed, Nov 20, 2024 at 12:48 PM Dmitry Belyavskiy wrote:
>
[...]
>> > The idea here was to auto-enable pkcs11-provider when it is installed,
>> > which still makes sense to me. The issue here I think is that many people
>> > ended up with pkcs11-provider installed because of a recommen
hi,
(adding Vlad to the loop)
On Wed, Nov 20, 2024 at 3:43 PM Davide Caratti wrote:
>
> hi,
>
> (Also, I tried reproducing locally on f41
> with NetworkManager-ci and << simwifi_ttls_mschapv2_eap >> test, but
> did not see any failure... @Arthur, can you share
hi,
On Wed, Nov 20, 2024 at 12:48 PM Dmitry Belyavskiy wrote:
>
[...]
>> I'm trying a setup right now, to understand what's happening.
>> wpa_supplicant does not need pkcs11-provider *at the moment*, because
>> it uses engine API for pkcs11 (and that is going to be a problem in
>> the future for
hi,
On Wed, Nov 20, 2024 at 11:09 AM Clemens Lang wrote:
>
> Hi,
>
> > On 19. Nov 2024, at 17:47, Arthur Bols wrote:
> >
> > A few days ago pkcs11-provider-0.5-3.fc41 update was pushed to Fedora 41.
> > Unfortunately, this update breaks eduroam and possibly many other
> > WPA2-Enterprise wifi
Hello,
my name is Davide Caratti, I'm a networking developer working for Red
Hat; I've been playing sometimes with Fedora, mostly as a contributor
for the 'wpa_supplicant'[1] package. I'm also doing some contribution
for the Linux kernel, mostly in the networking area.
C
