Radius and using an ecrypted password in wpa_supplicant.

[pfazer]

Hello All,

I have been able to connect and authenticate to our radius server using plain text username and password, using the below config.


ctrl_interface=/var/run/wpa_supplicant
ap_scan=1
update_config=1

network={
ssid="XXXXXXX"
scan_ssid=1
key_mgmt=WPA-EAP
proto=RSN
pairwise=CCMP
group=CCMP
eap=PEAP
identity="XXXXXXX"
password="XXXXXXXXXX"
phase2="auth=MSCHAPv2"
priority=10
}

I have read that I can generate a password hash by using echo -n password_here | iconv -t utf16le | openssl md4

But how do you use the hash password in the above config ?

[rcrsn51]

Have a look at PeasyWiFi at the top of this section. It handles encrypted passphrases.

1. Move your current profile into the profiles folder, if it's not there already. It must be a one-word alpha-numeric filename.

2. Restart PeasyWiFi

3. Open the Encrypt tab. Select a 4-character PIN.

4. Connect. You will get a pop-up box asking for the PIN.

This would be the first test of PeasyWifi on something other than a vanilla WiFi server. Please report back.

--------------------------

[pfazer]

Hello rcrsn51,

Many Thanks for this. This works well, but I have some questions.

1. When the Encrypt feature is used, is the password stored in the bcrypt file (and referenced when needed)?

2. I have used the Auto feature, is there a setting to pull the pin, so that it is populated when peasywifi is Auto run?


3. Is it possible to have peasywifi to prompt for the password ?

[rcrsn51]

This works well

Excellent! This is a great test result.

[Edit] See below.

[rcrsn51]

[Edit] An auto-started connection will also pop-up the PIN box.

[pfazer]

Hello rcrsn51,

Thanks for you help and checking this out.

I wanted to check something about the encryption.

It looks that I cannot decrypt the file manually from the command prompt with the PIN, but only use the file in conjcution with PeasyWiFi application, which is more secure in my eyes.

Is this by design ?

[rcrsn51]

Is this by design ?

Yes. If you look in the PeasyWiFi code, you will see why. It has to do with the minimum length of a blowfish encryption key.

I have decided to implement the Encrypt+Auto feature and will release v2.0 shortly.