-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Am Fr den 3. Feb 2017 um 19:56 schrieb Don Armstrong: > As near as I can tell, the certificates for the BTS are just fine: > > % openssl s_client -showcerts -connect bugs.debian.org:443 </dev/null|openssl > x509 -text|grep -e verify -e GMT -i > depth=2 O = Digital Signature Trust Co., CN = DST Root CA X3 > verify return:1 > depth=1 C = US, O = Let's Encrypt, CN = Let's Encrypt Authority X3 > verify return:1 > depth=0 CN = bugs.debian.org > verify return:1 > DONE > Not Before: Jan 6 10:58:00 2017 GMT > Not After : Apr 6 10:58:00 2017 GMT
Ah, so debian changed the CA? Was that published somewhere? I do not usually trust certificates coming from a different CA. > So if you're getting this error, it's either that reportbug is > connecting to the wrong URI, you don't have the appropriate CAs > installed, or something else is going on. Well, as I told, I do not trust CAs per default. I usually check certificates very good. As good as possible. And I cannot find any documentation that debian switched or want to switch. So, yes, that might be the reason, but please do document that proper. Regards Klaus - -- Klaus Ethgen http://www.ethgen.ch/ pub 4096R/4E20AF1C 2011-05-16 Klaus Ethgen <kl...@ethgen.ch> Fingerprint: 85D4 CA42 952C 949B 1753 62B3 79D0 B06F 4E20 AF1C -----BEGIN PGP SIGNATURE----- Comment: Charset: ISO-8859-1 iQGzBAEBCgAdFiEEMWF28vh4/UMJJLQEpnwKsYAZ9qwFAliU1aYACgkQpnwKsYAZ 9qyG/AwAmUC6bPFTaEflheY7hiW8ixBFHUzthgna1qMkE0VnMdfLHnB/xea5FAem gnf3HgPoZxBenGWDfqjnfNIr6d8ILBntho4EpiCTPIhmOX3XQ4tKgpAa/ezgiBZv wKWbWg3++6Ynd+2vrrgKJX8BjqOkW6nB1nB8dF/MbmWnft3GKa62sGvhHTYTXYom OT/6nb4VaKdzOqxmr3BGFV043+U01eluUWYqwIPphs4Bs35c6B+MVfP4k2ZqyJFI yYqyWnj6bk25PHYgsKFbMtcO6xBjXT5Myk2sA2P8Iq8oe6pqrgnh+B6STbPqx+gr HqcgAVwvtsYnhwoLynbe0EptM9AAZG01HVfEoJmdU3bNBQuLSAF33gqUmR2GMncX v/iYGifE9df+FqPYet5uDQ++JjEUTbKGsmyIuV/Ihfw9Lnrim6LGM00VzinLGjoO p29mPGPFuZG+/isWTqk2Bdc1ff2voo7WqTaUbSnd0ZKZREZ9hE7kVQ+o5wcJyB9S CZnuw35p =0sEI -----END PGP SIGNATURE-----