Hi Thank you, @albcares.
I tried to do a from-to in ubuntu and debian. Have some differences that I can't map between both, beyond the wpa_supplicant. Taking a look more close, I think that can be a difference in libssl, libcrypto and openssl. I tried to install the ubuntu package in my debian box, giving a lot of errors in wpa, when it try to call libssl.so.1.0.0, when in my box is 1.0.2. I did some symbolic links, without success. Is a dependence tree to solve. Anyway, I appreciate any other suggestion. Regards, Claudio Ferreira 2017-09-21 4:15 GMT-03:00 albcares <[email protected]>: > hi - what about simply throw the wpa_supplicant file away and set again > the wifi connection? Otherwise, if I understand what you mean, in such a > trial I opened the file and just cancel the rows I guessed extra-written. I > saved the ones carrying the right parameters only. > > let's know. > > 2017-09-21 1:32 GMT+02:00 Claudio Ferreira <[email protected]>: > >> Hi >> >> I'm with a strange problem. In my company, we have a enterprise wifi, >> with WPA/WPA2 enterprise and with TLS. >> >> When I access the network-manager, in gnome or kde, I can set this >> parameters with a Company.crt, my_cert.pem and my_cert_key.pem, using my >> network login as Identity and a password for my certs. >> >> The strange was that in Ubuntu 17.04, was fill the fields and connect. In >> Debian, using the sames files and parameters, returns some times asking >> again the password. >> >> Taking a look in syslog, I found a error in wpa_suppliant: >> >> Sep 14 15:51:58 nx01 wpa_supplicant[839]: OpenSSL: tls_connection_ca_cert >> - Failed to load root certificates error:00000000:lib(0):func(0): >> reason(0) >> Trying to find some thing in Google, I couldn't found any thing that >> explain what to do or what happens. >> >> Some suggestion or tip? >> >> Since now, I thank in advance. >> >> Regards, >> Claudio Ferreira >> > > > > -- > linux user #521635 >
