slackware-current

mirror of git://slackware.nl/current.git synced 2024-12-29 10:25:00 +01:00

History

Patrick J Volkerding f8721233ca Wed Jan 19 18:18:02 UTC 2022 ap/inxi-3.3.12_1-noarch-1.txz: Upgraded. ap/man-db-2.9.4-x86_64-3.txz: Rebuilt. Don't use --no-purge in the daily cron job to update the databases. l/gst-plugins-bad-free-1.18.5-x86_64-4.txz: Rebuilt. Link against neon-0.32.2. Thanks to marav. n/bind-9.16.25-x86_64-1.txz: Upgraded. n/ethtool-5.16-x86_64-1.txz: Upgraded. n/samba-4.15.4-x86_64-1.txz: Upgraded. n/wpa_supplicant-2.10-x86_64-1.txz: Upgraded. The implementations of EAP-pwd in hostapd before 2.10 and wpa_supplicant before 2.10 are vulnerable to side-channel attacks as a result of cache access patterns. NOTE: this issue exists because of an incomplete fix for CVE-2019-9495. For more information, see: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23303 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-23304 (* Security fix *) x/xterm-370-x86_64-6.txz: Rebuilt. XTerm-console: improve the font settings. Thanks to GazL.		2022-01-20 08:59:56 +01:00
..
config	Wed Jun 9 18:59:30 UTC 2021	2021-06-10 08:59:32 +02:00
patches	Wed Jan 19 18:18:02 UTC 2022	2022-01-20 08:59:56 +01:00
doinst.sh	Slackware 14.0	2018-05-31 22:51:55 +02:00
README.slackware	Slackware 13.0	2018-05-31 22:41:17 +02:00
slack-desc	Wed Jan 9 03:21:06 UTC 2019	2019-01-09 08:59:41 +01:00
wpa_supplicant.SlackBuild	Wed Jan 19 18:18:02 UTC 2022	2022-01-20 08:59:56 +01:00
wpa_supplicant.url	Wed Jan 19 18:18:02 UTC 2022	2022-01-20 08:59:56 +01:00

README.slackware

=================================================
How do I get my card to use WPA-PSK in Slackware?
=================================================

First off: wpa_supplicant REQUIRES the AP to broadcast the SSID. When the AP
hides its SSID, all you will get out of wpa_supplicant is the message:
"No suitable AP found"

Also, read the MADwifi FAQ (http://madwifi.sourceforge.net/dokuwiki/doku.php)
since it contains a wealth of information.

This being said, you'll have to do the following (as root):
Edit the file named /etc/wpa_supplicant.conf and add these lines:

network={
		scan_ssid=0
		proto=WPA
		key_mgmt=WPA-PSK
		pairwise=CCMP TKIP
		group=CCMP TKIP WEP104 WEP40
}

Then execute:

/usr/sbin/wpa_passphrase YOURSSID passphrase

with the SSID of your AP and the passphrase you've entered in its WPA-PSK configuration. You'll receive an output, which looks like this:

network={
		ssid="YOURSSID"
		#psk="passphrase"

psk=66a4bfb03de5656cf26cfa03a116097546046f4aea11ee044b841171207d8308
}

Copy the three lines within the network-tag into your own entry in wpa_supplicant.conf and change the permissions after you've finished editing:

chmod 640 /etc/wpa_supplicant.conf

To get your network device up and running, execute:

### /usr/sbin/wpa_supplicant -Bw -c/etc/wpa_supplicant.conf -iath0 -Dmadwifi ###
### you don't have to run the above command by hand, because it will         ###
### be executed by the rc.inet1 command that you run:                        ###

/etc/rc.d/rc.inet1 ath0_start

In case you want to see the wpa_supplicant in action, start it on the command line before enabling the wireless device, by running:
/usr/sbin/wpa_supplicant -dw -c/etc/wpa_supplicant.conf -iath0 -Dmadwifi
The terminal where you've started the wpa_supplicant should now show the communication between your wlan card and the AP. If you got everything up and running you can let Slackware's init script take over by killing wpa_supplicant and running:

/etc/rc.d/rc.inet1 ath0_restart

Studying the wpa_supplicant README is also highly recommended for further insight!