From: Denis Kenzior <denkenz@gmail.com>
To: Michael John <MJohn@midmark.com>,
"iwd@lists.linux.dev" <iwd@lists.linux.dev>
Subject: Re: TLS based WPA-Enterprise authentication methods on kernel 4.19
Date: Fri, 10 Jan 2025 14:36:17 -0600 [thread overview]
Message-ID: <19782535-90f6-48cb-ad20-94f80cbb42b0@gmail.com> (raw)
In-Reply-To: <LV8PR08MB9350AF162B98623BB2E6AC85AE1C2@LV8PR08MB9350.namprd08.prod.outlook.com>
Hi Michael,
On 1/10/25 1:35 PM, Michael John wrote:
> Hello,
>
> I'm running Linux kernel 4.19.231 (embedded, Buildroot build system) and when starting IWD I see the following message:
>
> Jan 10 19:13:39 cm1sd systemd[1]: Starting Wireless service...
> Jan 10 19:13:40 cm1sd iwd[1537]: No asymmetric key support found.
> Jan 10 19:13:40 cm1sd iwd[1537]: TLS based WPA-Enterprise authentication methods will not function.
> Jan 10 19:13:40 cm1sd iwd[1537]: Kernel 4.20+ is required for this feature.
> Jan 10 19:13:40 cm1sd iwd[1537]: The following options are missing in the kernel:
> Jan 10 19:13:40 cm1sd iwd[1537]: CONFIG_ASYMMETRIC_KEY_TYPE
> Jan 10 19:13:40 cm1sd iwd[1537]: CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE
> Jan 10 19:13:40 cm1sd iwd[1537]: CONFIG_PKCS7_MESSAGE_PARSER
> Jan 10 19:13:40 cm1sd iwd[1537]: CONFIG_X509_CERTIFICATE_PARSER
> Jan 10 19:13:40 cm1sd iwd[1537]: CONFIG_PKCS8_PRIVATE_KEY_PARSER
> Jan 10 19:13:40 cm1sd iwd[1537]: Wireless daemon version 2.17
>
> My kernel has many backports and all of the listed options exist and are enabled.
>
>> ag 'ASYMMETRIC_KEY|ASYMMETRIC_PUBLIC_KEY|PKCS7_MESSAGE|X509_CERTIFICATE|PKCS8_PRIVATE_KEY' ./buildroot/buildroot/output/cm1sd/build/linux-custom/.config
> 2475:CONFIG_ASYMMETRIC_KEY_TYPE=y
> 2476:CONFIG_ASYMMETRIC_PUBLIC_KEY_SUBTYPE=y
> 2477:CONFIG_X509_CERTIFICATE_PARSER=y
> 2478:CONFIG_PKCS8_PRIVATE_KEY_PARSER=y
> 2479:CONFIG_PKCS7_MESSAGE_PARSER=y
>
> Even though my 4.19 kernel appears to have the required options I still see this error about missing features.
> Are there additional features that are required but not getting listed?
Nope. See the logic here for yourself. iwd invokes this check with
L_KEY_FEATURE_CRYPTO:
https://git.kernel.org/pub/scm/libs/ell/ell.git/tree/ell/key.c#n791
You may want to strace iwd (or one of the ell unit tests, such as
unit/test-key.c) and see what the kernel is reporting.
Regards,
-Denis
prev parent reply other threads:[~2025-01-10 20:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 19:35 TLS based WPA-Enterprise authentication methods on kernel 4.19 Michael John
2025-01-10 20:36 ` Denis Kenzior [this message]
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=19782535-90f6-48cb-ad20-94f80cbb42b0@gmail.com \
--to=denkenz@gmail.com \
--cc=MJohn@midmark.com \
--cc=iwd@lists.linux.dev \
/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