You are not logged in.
When I connect to a network which requires a Certificate before I would select the specific certificate.
In my case 'Thawte_Premium_Server_CA.pem'.
Now it seems the file input has changed and the file is no longer recognized.
It confused me for a bit so in case someone else has this problem, simply using "/etc/ssl/cert.pem" works.
This file contains all certificates even though this seems a bit redundant, possibly slowing down making the connection. (..?)
I can however get the certificates to be recognized individually, by changing the file format from
-----BEGIN TRUSTED CERTIFICATE-----
MIIDJzCCApCgAwIBAgIBATANBgkqhkiG9w0BAQQFADCBzjELMAkGA1UEBhMCWkEx
[....]
-----END TRUSTED CERTIFICATE-----to
-----BEGIN CERTIFICATE-----
MIIDJzCCApCgAwIBAgIBATANBgkqhkiG9w0BAQQFADCBzjELMAkGA1UEBhMCWkEx
[....]
-----END CERTIFICATE-----(however NetworkManager then does not want to continue with this file)
Has anyone else experienced this? Is something wrong with the Certficate files?
Last edited by skiwi (2015-01-05 18:32:52)
Offline
Related to this recent news on the front page?
Arch on: ASUS Pro-PRIME x470, AMD 5800X3D, AMD 6800XT, 32GB, | ThinkPad X1 | ASUS ux303ua | Surface Laptop 2 | Minisforum UM780
Offline
It would appear so. I didn't expect it because it was after a fresh install yesterday evening. Doing as proposed in the news feed is then probably the better option.
Thanks
Offline
Just tried to set it up as proposed in the new feed but GNOME's NetworkManager still doesn't understand the crt files.
After moving everything, I open up network settings, select to change the certificate, browse to /etc/ca-certificates/trust-source/anchors, but the folder shows up empty.
Again, I can remove the "TRUSTED" keyword from the file, which makes it visible but the "Apply" button (to save settings) remains greyed out.
It's working for me using the file which includes all certificates but it's at least a bit ugly as it is.
Noone else is bothered by this?
Last edited by skiwi (2015-01-06 14:34:02)
Offline