How very bizarre… Chrom(ium) chokes if your TLS server certificate has an @ symbol in the Common Name (CN) field. It also fails with an “unable to parse file” error if you try to import a certificate authority that has the same (but, if you add the same certificate authority to the system trust store, it imports it without issue when you next start the browser).
TL; DR: Do not use the @ symbol in the Common Name (CN) fields of your TLS certificates.
(Firefox has no trouble with the same certificates and neither does OpenSSL.)
I am not a security expert but when I look at things like this, then read about security issues at Lastpass and other companies, is there a link. Surely the industry needs to get it's act together ASAP over all this.
@zleap @aral I'd say probably not. Nowadays phishing campaigns are the most common way those big companies get hacked, but you never know. Not sure how this tls issue would help an attack.