From: Sergey Matyukevich <geomatsi@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/wpa_supplicant: disable TEAP for internal TLS implementation
Date: Sun, 15 Mar 2020 23:07:57 +0300 [thread overview]
Message-ID: <20200315200757.GA5880@curiosity> (raw)
In-Reply-To: <20200108190439.459316-1-geomatsi@gmail.com>
On Wed, Jan 08, 2020 at 10:04:39PM +0300, Sergey Matyukevich wrote:
> EAP-TEAP support in hostapd/wpa_supplicant fails to build with internal
> TLS implementation. This patch disables TEAP support in wpa_supplicant
> when internal TLS implementation is selected. Similar fix for hostapd
> package has already been merged to Buildroot: see commit 47d14e3b1c20
> ("package/hostapd: disable TEAP for internal TLS implementation").
>
> TEAP is still an experimental feature that is not recommmended for
> production use. Currently it should not be used for anything else
> than experimentation and interoperability testing. Those who needs
> experimenting with TEAP are encouraged to enable openssl in their
> buildroot configuration.
>
> Fixes:
> http://autobuild.buildroot.net/results/e83613c06041a60f89da787f4ebf876245713cd2/
Also fixes similar recent autobuild failure:
http://autobuild.buildroot.net/results/c52dd7fbb74d8f7bdd0149ce0bd90f89caec5776/
Regards,
Sergey
next prev parent reply other threads:[~2020-03-15 20:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 19:04 [Buildroot] [PATCH 1/1] package/wpa_supplicant: disable TEAP for internal TLS implementation Sergey Matyukevich
2020-01-13 23:05 ` Arnout Vandecappelle
2020-01-14 8:02 ` Sergey Matyukevich
2020-02-16 14:38 ` Sergey Matyukevich
2020-03-15 20:07 ` Sergey Matyukevich [this message]
2020-08-13 21:08 ` Thomas Petazzoni
2020-08-28 16:25 ` Peter Korsgaard
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=20200315200757.GA5880@curiosity \
--to=geomatsi@gmail.com \
--cc=buildroot@busybox.net \
/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