Skip to contentSkip to conversation

wpa-supplicant & EAP-TLS

DISCUSSION Gary Thomas 5 participants 10 messages Aug 14, 2012 – Aug 15, 2012

lore
Share & tools
lore
#0 lore raw

Does anyone know why the recipe for wpa_supplicant is using gnutls and not the default OpenSSH for TLS services? It seems that gnutls is somehow broken and EAP-TLS does not work with this configuration. Changing wpa_supplicant to use the OpenSSH libraries makes EAP-TLS work fine.

Would a patch to make this change be entertained? or should I just keep it in my own layer?

Thanks

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw
Quoted 8 lines · Gary Thomas

Does anyone know why the recipe for wpa_supplicant is using gnutls and not the default OpenSSH for TLS services? It seems that gnutls is somehow broken and EAP-TLS does not work with this configuration. Changing wpa_supplicant to use the OpenSSH libraries makes EAP-TLS work fine.

Would a patch to make this change be entertained? or should I just keep it in my own layer?

I don't think a patch to just flip the default would be a good idea. A patch to make it be a DISTRO_FEATURE, on the other hand, would be excellent.

p.

#2 lore raw
Quoted 7 lines · Phil Blundell
Quoted 6 lines · Gary Thomas

Does anyone know why the recipe for wpa_supplicant is using gnutls and not the default OpenSSH for TLS services? It seems that gnutls is somehow broken and EAP-TLS does not work with this configuration. Changing wpa_supplicant to use the OpenSSH libraries makes EAP-TLS work fine.

Quoted 7 lines
Quoted 2 lines

Would a patch to make this change be entertained? or should I just keep it in my own layer?

I don't think a patch to just flip the default would be a good idea. A patch to make it be a DISTRO_FEATURE, on the other hand, would be excellent.

+1

Sau!

Quoted 10 lines

p.

_______________________________________________
Openembedded-core mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

#3 lore raw
In reply to Phil Blundell
Quoted 7 lines · Phil Blundell
Quoted 6 lines · Gary Thomas

Does anyone know why the recipe for wpa_supplicant is using gnutls and not the default OpenSSH for TLS services? It seems that gnutls is somehow broken and EAP-TLS does not work with this configuration. Changing wpa_supplicant to use the OpenSSH libraries makes EAP-TLS work fine.

Quoted 6 lines
Quoted 2 lines

Would a patch to make this change be entertained? or should I just keep it in my own layer?

I don't think a patch to just flip the default would be a good idea. A patch to make it be a DISTRO_FEATURE, on the other hand, would be excellent.

Thanks, I'll see about working one up.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#4 lore raw
Quoted 8 lines · Gary Thomas
Quoted 7 lines · Phil Blundell
Quoted 6 lines · Gary Thomas

Does anyone know why the recipe for wpa_supplicant is using gnutls and not the default OpenSSH for TLS services? It seems that gnutls is somehow broken and EAP-TLS does not work with this configuration. Changing wpa_supplicant to use the OpenSSH libraries makes EAP-TLS work fine.

Quoted 8 lines
Quoted 6 lines
Quoted 2 lines

Would a patch to make this change be entertained? or should I just keep it in my own layer?

I don't think a patch to just flip the default would be a good idea. A patch to make it be a DISTRO_FEATURE, on the other hand, would be excellent.

Thanks, I'll see about working one up.

Btw. You mean openssl not openssh, which uses openssl too.

And a problem with using openssl for wpa_supplicant was license incompatibilities.

Mabyee it is fixed meanwhile.

Bye Henning

#5 lore raw

Op 14 aug. 2012, om 15:59 heeft Henning Heinold <[email protected]> het volgende geschreven:

Quoted 16 lines · Gary Thomas
Quoted 15 lines · Phil Blundell
Quoted 13 lines · Gary Thomas
Quoted 8 lines

Does anyone know why the recipe for wpa_supplicant is using gnutls and not the default OpenSSH for TLS services? It seems that gnutls is somehow broken and EAP-TLS does not work with this configuration. Changing wpa_supplicant to use the OpenSSH libraries makes EAP-TLS work fine.

Would a patch to make this change be entertained? or should I just keep it in my own layer?

I don't think a patch to just flip the default would be a good idea. A patch to make it be a DISTRO_FEATURE, on the other hand, would be excellent.

Quoted 5 lines
Quoted 1 line

Thanks, I'll see about working one up.

Btw. You mean openssl not openssh, which uses openssl too.

And a problem with using openssl for wpa_supplicant was license incompatibilities.

I think wpa_supplicant has the openssl exception in its license nowadays, but it's best to double check

#6 lore raw
Quoted 19 lines · Koen Kooi

Op 14 aug. 2012, om 15:59 heeft Henning Heinold <[email protected]> het volgende geschreven:

Quoted 16 lines · Gary Thomas
Quoted 15 lines · Phil Blundell
Quoted 13 lines · Gary Thomas
Quoted 8 lines

Does anyone know why the recipe for wpa_supplicant is using gnutls and not the default OpenSSH for TLS services? It seems that gnutls is somehow broken and EAP-TLS does not work with this configuration. Changing wpa_supplicant to use the OpenSSH libraries makes EAP-TLS work fine.

Would a patch to make this change be entertained? or should I just keep it in my own layer?

I don't think a patch to just flip the default would be a good idea. A patch to make it be a DISTRO_FEATURE, on the other hand, would be excellent.

Quoted 7 lines
Quoted 5 lines
Quoted 1 line

Thanks, I'll see about working one up.

Btw. You mean openssl not openssh, which uses openssl too.

And a problem with using openssl for wpa_supplicant was license incompatibilities.

I think wpa_supplicant has the openssl exception in its license nowadays, but it's best to double check

I don't see anything explicit on this topic. That said, the latest version (1.0) is dual licensed GPL and BSD and the OpenSSL license is BSD compatible from what I can tell.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#7 lore raw
Quoted 3 lines · Gary Thomas

I don't see anything explicit on this topic. That said, the latest version (1.0) is dual licensed GPL and BSD and the OpenSSL license is BSD compatible from what I can tell.

Yes, wpa-supplicant itself has been OK in this respect for some time. (The dual-licensing option has actually been removed for the very latest versions of wpa-supplicant and it's now under the BSD license only, but this is fine for OpenSSL compatibility purposes.) However, there are quite a lot of other SSL-using programs which are only licensed under GPL terms and linking these with OpenSSL is problematic for some people. In an ideal world the oe-core license machinery would be able to detect and warn about that conflict, but I don't think we are quite there yet.

As a general rule, we don't want to build and ship multiple SSL implementations when one will suffice. GnuTLS seems to be the most compatible (in license terms) which is why it is generally the default. However, DISTROs which don't need to worry about the OpenSSL-GPL conflict for whatever reason might legitimately want to use OpenSSL globally, and DISTROs which aren't too bothered about potentially shipping both might legitimately want to use OpenSSL for specific packages like wpa-supplicant even if they have GnuTLS elsewhere.

p.

#8 lore raw
Quoted 14 lines · Phil Blundell
Quoted 3 lines · Gary Thomas

I don't see anything explicit on this topic. That said, the latest version (1.0) is dual licensed GPL and BSD and the OpenSSL license is BSD compatible from what I can tell.

Yes, wpa-supplicant itself has been OK in this respect for some time. (The dual-licensing option has actually been removed for the very latest versions of wpa-supplicant and it's now under the BSD license only, but this is fine for OpenSSL compatibility purposes.) However, there are quite a lot of other SSL-using programs which are only licensed under GPL terms and linking these with OpenSSL is problematic for some people. In an ideal world the oe-core license machinery would be able to detect and warn about that conflict, but I don't think we are quite there yet.

Quoted 8 lines

As a general rule, we don't want to build and ship multiple SSL implementations when one will suffice. GnuTLS seems to be the most compatible (in license terms) which is why it is generally the default. However, DISTROs which don't need to worry about the OpenSSL-GPL conflict for whatever reason might legitimately want to use OpenSSL globally, and DISTROs which aren't too bothered about potentially shipping both might legitimately want to use OpenSSL for specific packages like wpa-supplicant even if they have GnuTLS elsewhere.

I looked a bit into this and found that OE-core is already rather schizo on this topic, so I'm not quite sure what needs to be done here (i.e. should there be a DISTRO_FEATURES switch that chooses only one?) It would seem that all systems (at least those with wpa-supplicant included) will already have both SSL libraries installed.

opsnssl is used in these packages:
midori
socat
curl-native
openvpn
bind
telepathy-idle
dhcp
xserver-kdrive
tcf-agent
python
rpm
git
task-core-basic
mailx
libzypp (=> sat-solver, zypper)
wget

gnutls is used by these packages:
cups
wpa-supplicant
neon
curl

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#9 lore raw
Quoted 5 lines · Gary Thomas

I looked a bit into this and found that OE-core is already rather schizo on this topic, so I'm not quite sure what needs to be done here (i.e. should there be a DISTRO_FEATURES switch that chooses only one?) It would seem that all systems (at least those with wpa-supplicant included) will already have both SSL libraries installed.

"All systems" is probably a bit strong. I certainly have multiple configurations which don't install anything from the openssl list below.

Anyway, it looks like the best way forward in the short term is to make the choice of SSL library be a PACKAGECONFIG option for wpa-supplicant and any other recipes that you feel like changing. I think it would also make sense to have some sort of DISTRO_FEATURE to set a global preference for this although perhaps the exact form of that setting needs a bit of further thought.

Quoted 18 lines

opsnssl is used in these packages:
midori
socat
curl-native
openvpn
bind
telepathy-idle
dhcp
xserver-kdrive
tcf-agent
python
rpm
git
task-core-basic
mailx
libzypp (=> sat-solver, zypper)
wget

Quoted 5 lines

gnutls is used by these packages:
cups
wpa-supplicant
neon
curl

p.