User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36
When connecting to WPA2/PEAP/MSCHAPv2 wifi networks which do not have a CA Certificate Network Manager may incorrectly mark the CA certificate as needing verification and fail that verification.
Reproducible: Always
Steps to Reproduce:
1. Attempt to connect to WPA2/PEAP/MSCHAPv2 wifi network which does not have a CA Certificate.
Actual Results:
The line system-ca-certs=true is erroneously added to the relevant Network Manager config file and connection fails.
Expected Results:
Connection to network should occur despite the lack of a CA Certificate (as many educational/business enterprise networks don't provide them).
User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36
When connecting to WPA2/PEAP/MSCHAPv2 wifi networks which do not have a CA Certificate Network Manager may incorrectly mark the CA certificate as needing verification and fail that verification.
Reproducible: Always
Steps to Reproduce: ca-certs= true is erroneously added to the relevant Network Manager config file and connection fails.
1. Attempt to connect to WPA2/PEAP/MSCHAPv2 wifi network which does not have a CA Certificate.
Actual Results:
The line system-
Expected Results: business enterprise networks don't provide them).
Connection to network should occur despite the lack of a CA Certificate (as many educational/
See also https:/ /bugs.launchpad .net/ubuntu/ +source/ network- manager/ +bug/1104476