This is actually a big problem for two reasons: (1) The user does not get the correct feedback to the problem: Instead of a notice that the certificate not trusted, he/she is just asked again and again and again for the correct username and password. (2) Encouraging people to trust in central certificates and not in self signed ones plays in the hands of NSA and everyone how depends on man-in-the-middle attacs. People should be encouraged to trust only in certificates they know are correct and be allowed to do so, instead of forcing them to only accept 'officially' signed certificates .
(still existing in ubuntu 13.10. , btw) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1104476 Title: Network manager cannot connect to WPA2/PEAP/MSCHAPv2 network without CA_Certificate To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1104476/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
