I am seeing the same issue -- failure to associate due to a self-signed certificate. (at least that's what it looks like to me)
What seems to be the relevant portion of the log is: Nov 18 09:37:35 my_laptop wpa_supplicant[1587]: CTRL-EVENT-EAP-METHOD EAP vendor 0 method 25 (PEAP) selected Nov 18 09:37:35 my_laptop wpa_supplicant[1587]: TLS: Certificate verification failed, error 19 (self signed certificate in certificate chain) depth 2 for '/C=US/O=The Go Daddy Group, Inc./OU=Go Daddy Class 2 Certification Authority' Nov 18 09:37:35 my_laptop wpa_supplicant[1587]: SSL: SSL3 alert: write (local SSL3 detected an error):fatal:unknown CA Nov 18 09:37:35 my_laptop wpa_supplicant[1587]: OpenSSL: tls_connection_handshake - SSL_connect error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed Nov 18 09:37:35 my_laptop wpa_supplicant[1587]: CTRL-EVENT-EAP-FAILURE EAP authentication failed I've attached the full log ** Attachment added: "syslog output" http://launchpadlibrarian.net/35841222/syslog.log ** Changed in: network-manager (Ubuntu) Status: Invalid => New -- network manager (WPA-EAP TLS) fails - can't use CA certificate https://bugs.launchpad.net/bugs/293238 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
