[Buildroot] [PATCH 1/1] package/wpa_supplicant: disable TEAP for internal TLS implementation

[Sergey Matyukevich]

> > > 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.
> > 
> >  So then why don't we just unconditionally disable this feature? Preferably with
> > a comment in the .mk file that it's disabled due to its experimental nature, so
> > that someone who needs it a couple of years down the line can note that it's not
> > longer experimental.
> 
> Well, this is another possible option. But I don't see why we should
> disable it completely. TEAP does not build with internal hostapd TLSv1
> implementation, which in its turn is also marked as experimental. On
> the other hand, TEAP successfully builds if OpenSSL is selected as TLS
> implementation. So why don't we just disable known broken combination,
> leaving the choice between working combinations to the end user.

Hi Thomas, Arnout,

It has been a while since my last reply. Do you still have any other
concerns regarding suggested approach ?

Let me reiterate the idea. TEAP is a farily new and experimental hostapd
feature which does not compile with internal hostapd TLS implementation.
On the other hand, it can be successfully built with OpenSSL as TLS
provider for hostapd.

So suggested approach explicitly disables broken configuration, but still
lets the users to play with it if they need to.

Regards,
Sergey