LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 12-13-2018, 06:43 PM   #1
gablek
LQ Newbie
 
Registered: Jan 2013
Location: Oregon, USA
Distribution: Slackware64-current
Posts: 9

Rep: Reputation: Disabled
Unable to authenticate via WPA2-Enterprise since 12-08-2018 -current upgrades


My workplace has two secured wifi networks (eduroam is one; WPA2-Enterprise/PEAP/MSCHAPV2) that I could authenticate to on 12/7 but could no longer do so as of 12/10. My home network (WPA2-Personal) still authenticates OK.

My evidence that something in Slackware changed is that Slack Live v. 1.3.0 allowed me to authenticate today, but updating the stick to 1.3.0.1 (most current as of today) caused authentication to fail. I conclude that one or more of the Saturday/Sunday updates has changed how things are being handled.

Trying to use wpa_supplicant from the command line throws a couple errors:
Code:
SSL: SSL3 alert: write (local SSL3 detected an error):fatal:internal error
OpenSSL: openssl_handshake - SSL_connect error:141A90B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers available
I did try downgrading the following potential sources of the problem to no avail:
wpa_supplicant back to 2.6.0
mozilla-nss back to 3.4.0
Kernel back to 4.19.6

I also tried dropping openssl back to 1.1.1 from 1.1.1a; still no luck.

So what else changed that might lead to this? Nothing else that was updated would seem to affect how openssl would hash a password (which seems to me to be the problem).
 
Old 12-13-2018, 07:28 PM   #2
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,633

Rep: Reputation: 3393Reputation: 3393Reputation: 3393Reputation: 3393Reputation: 3393Reputation: 3393Reputation: 3393Reputation: 3393Reputation: 3393Reputation: 3393Reputation: 3393
How are you updating your Slackware Live installation? It could be the upgrade wasn't completed properly so it broke some things.
 
Old 12-13-2018, 08:36 PM   #3
gablek
LQ Newbie
 
Registered: Jan 2013
Location: Oregon, USA
Distribution: Slackware64-current
Posts: 9

Original Poster
Rep: Reputation: Disabled
Same as I always do:

iso2usb.sh -r -i slackware64-live-plasma5-current.iso -o /dev/sdX

Though it would be curious if the only thing that got munged was the same thing I'm having problems with in the main install. And it doesn't solve the original problem, either; something is clearly wrong.
 
Old 12-14-2018, 03:51 AM   #4
lotar
LQ Newbie
 
Registered: Aug 2012
Location: Rome
Distribution: Slackware64 -current, CentOS
Posts: 12

Rep: Reputation: 21
Hi, i have the same error with my company WPA2 Enterprise WiFi:

Code:
SSL: SSL3 alert: write (local SSL3 detected an error):fatal:internal error
OpenSSL: openssl_handshake - SSL_connect error:141A90B5:SSL routines:ssl_cipher_list_to_bytes:no ciphers available
The problem is a new version of wpa_supplicant package (2.7) upgraded in -current few days ago (2018-12-08). I have reverted wpa_supplicant package to previous version (2.6) and now works fine.
 
2 members found this post helpful.
Old 12-14-2018, 04:22 AM   #5
fsauer
Member
 
Registered: Jul 2012
Posts: 83

Rep: Reputation: Disabled
I can confirm this, also on enterprise WPA. In /var/log/messages: Authentication with ... timed out.

eduroam still works. Luckily.

A few releases earlier, this happened a lot, but did work nicely for the last few months.

Have a nice day.

Franz
 
Old 12-14-2018, 07:34 AM   #6
kgha
Member
 
Registered: May 2018
Location: Sweden
Distribution: AlienBob's LiveSlak MATE
Posts: 34

Rep: Reputation: 25
Ah, so that's why I no longer have been able to connect to the Eduroam wlan on my job the last few days (WPA2Enterprise). The connection has always been a bit dodgy (router far away from my room) so I haven't bothered to look deeper into it, especially since I'm going into retirement after Christmas. I'll try downgrading to wpa_supplicant-2.6 and see if that helps as it did for lotar (but apparently not for gablek?).
Hope a fixed package upgrade will be there soon.
 
Old 12-14-2018, 11:06 AM   #7
gablek
LQ Newbie
 
Registered: Jan 2013
Location: Oregon, USA
Distribution: Slackware64-current
Posts: 9

Original Poster
Rep: Reputation: Disabled
I think the problem is wpa_supplicant--I just hadn't rebooted when I tried it earlier. Downgrading to 2.6 and rebooting allows me to authenticate.
 
2 members found this post helpful.
Old 12-14-2018, 12:40 PM   #8
kgha
Member
 
Registered: May 2018
Location: Sweden
Distribution: AlienBob's LiveSlak MATE
Posts: 34

Rep: Reputation: 25
With due respect: should this thread really be marked as solved? To me, downgrading from the latest available package to an older version is a (temporary) workaround rather than a solution?
 
Old 12-14-2018, 06:31 PM   #9
Andersen
Member
 
Registered: Dec 2008
Distribution: Slackware
Posts: 120

Rep: Reputation: 44
I had the same problem, thanks for help guys!


Quote:
Originally Posted by kgha View Post
With due respect: should this thread really be marked as solved? To me, downgrading from the latest available package to an older version is a (temporary) workaround rather than a solution?
Yes, but since this is a -current branch and the problem is reported, I trust we can expect some changes very soon.
 
Old 12-14-2018, 06:49 PM   #10
volkerdi
Slackware Maintainer
 
Registered: Dec 2002
Location: Minnesota
Distribution: Slackware! :-)
Posts: 1,619

Rep: Reputation: 4945Reputation: 4945Reputation: 4945Reputation: 4945Reputation: 4945Reputation: 4945Reputation: 4945Reputation: 4945Reputation: 4945Reputation: 4945Reputation: 4945
Quote:
Originally Posted by Andersen View Post
Yes, but since this is a -current branch and the problem is reported, I trust we can expect some changes very soon.
Sure, if I knew how to fix it. No WPA2-Enterprise here... so any hints are appreciated as always.
 
Old 12-14-2018, 10:39 PM   #11
Andersen
Member
 
Registered: Dec 2008
Distribution: Slackware
Posts: 120

Rep: Reputation: 44
[edit]I'm sorry but I'll have to correct myself here. I've just realized that I've been connected to the network with very similar name, and that's the reason it worked. However, this one is not WPA2-Enterprise, so.. nothing has changed with the latest update. Going back to wpa_supplicant 2.6

Last edited by Andersen; 12-17-2018 at 04:58 PM. Reason: wrong conclusion corrected
 
Old 12-18-2018, 02:57 AM   #12
kgha
Member
 
Registered: May 2018
Location: Sweden
Distribution: AlienBob's LiveSlak MATE
Posts: 34

Rep: Reputation: 25
Downgrading to wpa_supplicant-2.6 didn't work for me - NetworkManager ceased to pick up any networks.
Upgraded again, created new eduroam connection but authentication fails every time. Same thing when trying to connect via wpa_cli.
All the latest -current upgrades except for kernel (still on 4.14), but seems unlikely that this should be kernel related?
 
Old 12-18-2018, 06:33 AM   #13
lotar
LQ Newbie
 
Registered: Aug 2012
Location: Rome
Distribution: Slackware64 -current, CentOS
Posts: 12

Rep: Reputation: 21
Quote:
Originally Posted by kgha View Post
Downgrading to wpa_supplicant-2.6 didn't work for me - NetworkManager ceased to pick up any networks.
Upgraded again, created new eduroam connection but authentication fails every time. Same thing when trying to connect via wpa_cli.
All the latest -current upgrades except for kernel (still on 4.14), but seems unlikely that this should be kernel related?
I think a wpa_supplicant-2.7 process still alive after downgrade.

I suggest, stop NetworkManager (using rc script) and kill all process of wpa_supplicant, start NetworkManager and try again:

Code:
sh /etc/rc.d/rc.networkmanager stop
killall -9 wpa_supplicant
sh /etc/rc.d/rc.networkmanager start
 
Old 12-18-2018, 07:33 AM   #14
kgha
Member
 
Registered: May 2018
Location: Sweden
Distribution: AlienBob's LiveSlak MATE
Posts: 34

Rep: Reputation: 25
Thanks for the suggestion, Giuseppe. Unfortunately it didn't solve the issue. As a last desperate attempt I reinstalled NetworkManager and - lo and behold - it works again!

Googling reveals that trouble with WPA2 Enterprise networks seem to appear after almost every new wpa_supplicant version. Still a mystery what's the issue with the 2.7 upgrade, though.

I'll store my wpa_supplicant-2.6-x86_64-6 package in a safe place and await future upgrades.
 
1 members found this post helpful.
Old 12-30-2018, 12:13 PM   #15
lotar
LQ Newbie
 
Registered: Aug 2012
Location: Rome
Distribution: Slackware64 -current, CentOS
Posts: 12

Rep: Reputation: 21
Code:
slackman changelog --details wpa_supplicant
2018-12-30 00:13:15 (slackware:packages)
n/wpa_supplicant-2.6-x86_64-6.txz:  Upgraded
  It seems we're not the only ones with broken WPA2-Enterprise support
  with wpa_supplicant-2.7, so we'll fix it the same way as everyone else -
  by reverting to wpa_supplicant-2.6 for now.


2018-12-30 00:13:15 (slackware:packages)
testing/packages/wpa_supplicant-2.7-x86_64-2.txz:  Upgraded
  Applied a patch from Gentoo to allow building CONFIG_IEEE80211X=y without
  the experimental CONFIG_FILS=y option.
Thanks Pat!
 
1 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Problem: dbus variables not being exported since a few days ago (~2018-07-16). Lockywolf Slackware 2 07-17-2018 09:12 PM
LXer: The Difference Between Wi-Fi Security Protocols: WPA2-AES vs WPA2-TKIP LXer Syndicated Linux News 0 12-19-2014 01:36 AM
LXer: Wi-Fi Security: Should You Use WPA2-AES, WPA2-TKIP, or Both? LXer Syndicated Linux News 0 12-18-2014 07:47 PM
[SOLVED] Unable to connect to WPA2 Enterprise network, Mandriva 2010.2 Tank Jr Mandriva 3 03-07-2011 04:49 PM
Kmail error "Unable to Authenticate via. CRAM-MD5" Spreegem Debian 2 08-04-2005 01:50 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:54 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration