On 2014-08-19 13:43:26 +0400, Vlad Orlov wrote: > This indeed looks like a bug in 1.15, because 1.13 and 1.14 > recognize the expired certificate: > > $ wget www.cloudflarechallenge.com > --2014-08-19 13:41:45-- http://www.cloudflarechallenge.com/ > Resolving www.cloudflarechallenge.com (www.cloudflarechallenge.com)... > 107.170.194.215 > Connecting to www.cloudflarechallenge.com > (www.cloudflarechallenge.com)|107.170.194.215|:80... connected. > HTTP request sent, awaiting response... 301 Moved Permanently > Location: https://www.cloudflarechallenge.com/ [following] > --2014-08-19 13:41:46-- https://www.cloudflarechallenge.com/ > Connecting to www.cloudflarechallenge.com > (www.cloudflarechallenge.com)|107.170.194.215|:443... connected. > ERROR: The certificate of 'www.cloudflarechallenge.com' is not trusted. > The certificate has expired
This bug isn't on expired certificates, but on the revoked ones. The www.cloudflarechallenge.com test is now obsolete because the certificate has expired (wget 1.15 checks that, so no bugs here for expired certificates). Two tests with revoked certificates are still working: https://revoked.grc.com/ https://www.vinc17.net:4434/ -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
