We have moved to a new Sailfish OS Forum. Please start new discussions there.

Revision history [back]

click to hide/show revision 1
initial version

posted 2014-02-06 17:58:19 +0200

EAP-TLS: Private key not configured

I cannot seem to connect to my companies wifi via TLS private key, this is the log from WPA_supplicant:

wlan0: Trying to associate with SSID 'Private'

wlan0: Associated with MAC ADDRESS

wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started

wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=17 -> NAK

wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13

EAP-TLS: Private key not configured

wlan0: EAP: Failed to initialize EAP method: vendor 0 method 13 (TLS)

wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed

wlan0: Authentication with MAC ADDRESS timed out.

wlan0: CTRL-EVENT-DISCONNECTED bssid=MAC ADDRESS reason=3 locally_generated=1

wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Private" auth_failures=1 duration=10

and this is my configuration for /var/lib/connman/wifi_private.config:

[service_private]

Type=wifi

Name=Private

EAP=tls

PrivateKeyFile=/home/nemo/.cert/private_wifi.p12

PrivateKeyPassphrase=KEYPASSPHRASE

PrivateKeyPassphraseType=fsid

Identity=name@email.com

Anybody know where I might be going wrong? The certificate file, the p12 file is definitely valid since when I connect through a Ubuntu laptop using that certificate it works perfectly.

EAP-TLS: Private key not configured

I cannot seem to connect to my companies wifi via TLS private key, this is the log from WPA_supplicant:

wlan0: Trying to associate with SSID 'Private'

'Private' wlan0: Associated with MAC ADDRESS

ADDRESS wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started

started wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=17 -> NAK

NAK wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13

method=13 EAP-TLS: Private key not configured

configured wlan0: EAP: Failed to initialize EAP method: vendor 0 method 13 (TLS)

(TLS) wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed

failed wlan0: Authentication with MAC ADDRESS timed out.

out. wlan0: CTRL-EVENT-DISCONNECTED bssid=MAC ADDRESS reason=3 locally_generated=1

locally_generated=1 wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Private" auth_failures=1 duration=10

duration=10

and this is my configuration for /var/lib/connman/wifi_private.config:

[service_private]

Type=wifi

Name=Private

EAP=tls

PrivateKeyFile=/home/nemo/.cert/private_wifi.p12

PrivateKeyPassphrase=KEYPASSPHRASE

PrivateKeyPassphraseType=fsid

Identity=name@email.com

[service_private]
Type=wifi
Name=Private
EAP=tls
PrivateKeyFile=/home/nemo/.cert/private_wifi.p12
PrivateKeyPassphrase=KEYPASSPHRASE
PrivateKeyPassphraseType=fsid
Identity=name@email.com

Anybody know where I might be going wrong? The certificate file, the p12 file is definitely valid since when I connect through a Ubuntu laptop using that certificate it works perfectly.

EAP-TLS: Private key not configured

I cannot seem to connect to my companies wifi via TLS private key, this is the log from WPA_supplicant:

wlan0: Trying to associate with SSID 'Private'
wlan0: Associated with MAC ADDRESS
wlan0: CTRL-EVENT-EAP-STARTED EAP authentication started
wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=17 -> NAK
wlan0: CTRL-EVENT-EAP-PROPOSED-METHOD vendor=0 method=13
EAP-TLS: Private key not configured
wlan0: EAP: Failed to initialize EAP method: vendor 0 method 13 (TLS)
wlan0: CTRL-EVENT-EAP-FAILURE EAP authentication failed
wlan0: Authentication with MAC ADDRESS timed out.
wlan0: CTRL-EVENT-DISCONNECTED bssid=MAC ADDRESS reason=3 locally_generated=1
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Private" auth_failures=1 duration=10

and this is my configuration for /var/lib/connman/wifi_private.config:

[service_private]
Type=wifi
Name=Private
EAP=tls
PrivateKeyFile=/home/nemo/.cert/private_wifi.p12
PrivateKeyPassphrase=KEYPASSPHRASE
PrivateKeyPassphraseType=fsid
Identity=name@email.com

Anybody know where I might be going wrong? The certificate file, the p12 file is definitely valid since when I connect through a Ubuntu laptop using that certificate it works perfectly.