|
> Date: Sat, 6 Jun 2015 11:25:26 -0400
> From: hsantos@xxxxxxxx > To: nd@xxxxxxxxxxxx; jari.arkko@xxxxxxxxx; ietf@xxxxxxxx > Subject: Re: Proposed Statement on "HTTPS everywhere for the IETF" > > It could not update because the > HTTPS URL was failing due the browser seeing an erroneous "Invalid > Certificate" display with no option to accept, temporary or otherwise. > You have to download via another browser that isn't so strict, yet. Why does the IETF use invalid certificates in the first place? If this is due to a wrong system clock, then the user probably cannot visit Google, Facebook, GitHub, etc. as well, and at least Firefox and Chrome advise users to fix the clock in such situation. Xiaoyin |