On 8/26/11 14:00 , Doug Barton wrote:
Joel,
"it doesn't" means that the mailing list archives do not require the use
of https, if the entry point urls point to the https server that bad in
this case...
If one has forgotten to renew a certificate before it expires, it takes
time to get a new one issued. as an operational pratice is is necessary
to track the issue and expiration dates of such resources.
I don't know what "It doesn't" is supposed to mean, but visiting
https://www.ietf.org/* today with firefox it is still reporting that the
certificate expired yesterday.
Given the volume of discussion about the topic starting yesterday when
the problem started one could easily make a case for "it's still broken"
being a significant "issue."
cc'ing the address listed as "Report Website Errors" on the home page.
Doug
On 08/26/2011 07:44, Joel jaeggli wrote:
It doesn't...
http://www.ietf.org/mail-archive/web/v6ops/current/maillist.html
On 8/26/11 00:18 , t.petch wrote:
Why does the IETF website consider it necessary to use TLS to access the
mailing
list archives, when they all appeared without it, or any other security, in
the
first place?
Besides all the usual hassle of TLS, today the certificate is reported by
IE as
expired, which sort of sums it up.
Tom Petch
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf
_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www.ietf.org/mailman/listinfo/ietf