Le 07/01/2015 07:19, Paul Wise a écrit : > On Sun, 2014-12-21 at 18:45 +0800, Paul Wise wrote: > >> systems should only trust certificates generated by us by default. >> /etc/ssl/certs should contain only certificates for debian.org services.
[…] > This change has been committed to dsa-puppet.git and is percolating > through all debian.org hosts […] > ==> /etc/ssl/certs/README <== > This directory *only* contains the certificate(s) for the current service > certificates for debian.org services. If I understand correctly, things that have been broken since ca December 15th should be fixed now. Yet, the Perl spider used for l10n purpose is still broken from tye, so is cURL: taffit@tye:~$ curl https://lists.debian.org/debian-l10n-portuguese curl: (60) SSL certificate problem: unable to get local issuer certificate More details here: http://curl.haxx.se/docs/sslcerts.html curl performs SSL certificate verification by default, using a "bundle" of Certificate Authority (CA) public keys (CA certs). If the default bundle file isn't adequate, you can specify an alternate file using the --cacert option. If this HTTPS server uses a certificate signed by a CA represented in the bundle, the certificate verification probably failed due to a problem with the certificate (it might be expired, or the name might not match the domain name in the URL). If you'd like to turn off curl's verification of the certificate, use the -k (or --insecure) option. Can anything be done here (e.g., making lists.d.o available via HTTP would be a more viable option than having stuff broken for another month)? Regards David
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Debian-l10n-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/debian-l10n-devel
