457
Comment:
|
802
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
Line 4: | Line 3: |
An SSH server can authenticate clients using a variety of different methods. The most basic of these is password authentication, which is easy to use, but not the most secure.<<BR>><<BR>> SSH keys prove to be a reliable and secure alternative. To use this alternative you need a key pair with a public and a private key. You can generate a key pair with the command ssh-keygen: {{{ |
The problem with RaspberryPi devices is, that they cannot authorize themselfs in 802.1x networks. With 'wpa_supplicant' authorizing on a 802.1x networks will be possible. Proceed as followed: |
Line 8: | Line 5: |
}}} | 1. Change to '/etc/wpa_supplicant/' 1. Create the file 'wpa_supplicant.conf' and make following entries (in this case for the 'eth' SSID): {{{ network={ ssid="eth" proto=RSN key_mgmt=WPA-EAP pairwise=CCMP auth_alg=OPEN eap=PEAP identity="NETHZ login" password="Netzwerk Passwort" phase1="peaplabel=auto peapver=0" phase2="auth=PAP" } }}} See here for further informations (german): https://emanuelduss.ch/2012/01/eine-wpa2-wlan-verbindung-herstellen-mit-wpa_supplicant/ |
How to authorize a RaspberryPi device for 802.1x WLAN
The problem with RaspberryPi devices is, that they cannot authorize themselfs in 802.1x networks. With 'wpa_supplicant' authorizing on a 802.1x networks will be possible. Proceed as followed:
- Change to '/etc/wpa_supplicant/'
- Create the file 'wpa_supplicant.conf' and make following entries (in this case for the 'eth' SSID):
network={ ssid="eth" proto=RSN key_mgmt=WPA-EAP pairwise=CCMP auth_alg=OPEN eap=PEAP identity="NETHZ login" password="Netzwerk Passwort" phase1="peaplabel=auto peapver=0" phase2="auth=PAP" }
See here for further informations (german):
https://emanuelduss.ch/2012/01/eine-wpa2-wlan-verbindung-herstellen-mit-wpa_supplicant/