Comment 16 for bug 445487

Thank You!

On Nov 23, 2009, at 3:16 AM, Remco Poortinga - van Wijnen wrote:

> A colleague of mine (Thank you Francois) found a workaround that worked for me:
> My situation: similar error message in .xsession-errors, wasn't able to 'apply' or select the .p12 certificate for WPA(2)-Enterprise, separate .pem files for usercert and key didn't work either.
>
> Repackaging the original .p12 into a new .p12 with openssl did work
> however:
>
> $ openssl pkcs12 -in original.p12 -out temp.pem
> $ openssl pkcs12 -in temp.pem -export -name "Repackaged PKCS#12 file" -out new.p12
>
> Selecting the .p12 file in the 'Private Key' entry, leaving the rest
> empty allowed me to 'apply' it and get WPA(2)-Enterprise (for eduroam)
> working.
>
> Hopefully this works for others as well.
>
> Cheers,
>
> Remco
>
> --
> Network-Manager fails WPA2 Enterprise configuration
> https://bugs.launchpad.net/bugs/445487
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “network-manager-applet” package in Ubuntu: Confirmed
>
> Bug description:
> I've recently upgraded to Karmic from Jaunty and now got network-manager-gnome=0.8~a~git.20091002t194214.8515a07-0ubuntu1
> When i configure 802.1x TLS authentication on the wired interface and fill all fields on "802.1x Security" tab, the "Apply..." button still remains inactive.
> To check correctness of settings I've connected to my network using wpa_supplicant directly, so i suppose all my files and a password is ok.
> Stracing nm-connection-editor shows following lines on its STDERR:
> while private key password is invalid (guess it's ok):
> WARNING **: Error: couldn't verify private key: 14 Failed to finalize decryption of the private key: -8023.
> when password becomes valid:
> WARNING **: Error: couldn't verify private key: 4 Couldn't decode certificate: -8183
>