Issue #999
closedCAcert should be added to Replicant
0%
Description
This isn't strictly-speaking a bug, but some of the Replicant default bookmarks are to the HTTPS version of the Replicant site itself, which uses a CAcert-issued certificate, though the CAcert root certificates are not installed in Replicant by default. Both to prevent these bookmarked pages from throwing errors and to support community-driven certificates, it would be nice to see the CAcert added to the list of Replicant default certificates.
Updated by My Self about 9 years ago
That's a great idea in my eyes.
Hope this would be possible in future Replicant releases.
Updated by Paul Kocialkowski about 9 years ago
That seems reasonable, but I'm going to have to do this the right way. I think the best way for me to establish a chain of trust would be to meet with trusted CaCert members at FOSDEM to verify the certificate. In the meantime, I suppose I could still include it and let people report if there is a mismatch.
Note that this would have been a better fit for the forums or the mailing list, as this is not really a bug.
Updated by Paul Kocialkowski almost 9 years ago
- Status changed from New to Closed
- Resolution set to fixed
This was included in our repositories and will be part of the next batch of images: https://gitorious.org/replicant/libcore/commit/b32087cc78dfd13aac9e6476266cf211b179af2f
However, it still shows replicant.us as untrusted, while other websites using CaCert work normally. I will raise the issue with them next time.