From: James Prestwood <prestwoj@gmail.com>
To: Michael Yartys <mail@yartys.no>,
"iwd@lists.linux.dev" <iwd@lists.linux.dev>
Subject: Re: Unable to connect to eduroam
Date: Fri, 23 Feb 2024 07:02:19 -0800 [thread overview]
Message-ID: <495f9bd9-b0af-4e9c-b9b7-99f1b4d544fc@gmail.com> (raw)
In-Reply-To: <njvxKaPo_CBxsQGaNSRHj8xOSxzk1_j_K-minIe4GCKUMB1qxJT8nPk9SGmfqg7Aepm_5dO7FEofYIYP1g15R9V5dJ0F8bN6O4VthSjzu1g=@yartys.no>
HI Michael,
On 2/23/24 6:25 AM, Michael Yartys wrote:
> Hi
>
> I'm running iwd 2.14 on Fedora 39 Silverblue with kernel version 6.7.5-200.fc39.x86_64, and I've been having issues for the last two weeks or so connecting to my university eduroam network. What happens is that I get an internal error that causes the connection attempt to fail with eapFail. Here's the log output with TLS debugging enabled:
<snip>
>
>
> I'm sure these certificates are correct because I was able to roll back to a working build on Fedora Silverblue to keep connecting to the network. Unfortunately, I was dumb enough to forget to pin/freeze that working build to prevent it from being replaced by new versions as I continually updated the system.
>
> I searched a bit around and found that some other folks had experienced the same issue on Arch: https://bbs.archlinux.org/viewtopic.php?id=291921
>
> That thread links to another thread about the deprecation of SHA-1 in the kernel: https://bbs.archlinux.org/viewtopic.php?id=292208
>
> rochus from the first thread was able to connect to their eduroam network when they tried a kernel with the offending commit reverted. Now, I know very little about certificates, but no certificates in my cert chain are SHA-1 signed, are they? Could this still be related to the issue I'm experiencing?
Yep it appears the issue is a lack of SHA1 in the kernel.
I'm not that familiar with TLS but based on the code RSA certs use
PKCS1, which requires SHA1 (someone correct me if I'm wrong).
The kernel apparently removed this... they did (or are doing) the same
thing for MD5. I guess we need to roll our own.
Thanks,
James
>
>
> Michael
>
next prev parent reply other threads:[~2024-02-23 15:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 14:25 Unable to connect to eduroam Michael Yartys
2024-02-23 15:02 ` James Prestwood [this message]
2024-02-23 15:04 ` Denis Kenzior
2024-02-23 19:37 ` Michael Yartys
2024-02-23 20:26 ` Denis Kenzior
2024-02-23 22:09 ` Michael Yartys
2024-02-26 10:11 ` Michael Yartys
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=495f9bd9-b0af-4e9c-b9b7-99f1b4d544fc@gmail.com \
--to=prestwoj@gmail.com \
--cc=iwd@lists.linux.dev \
--cc=mail@yartys.no \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox