4 ms·
I wish browsers showed a large warning like "This site's TLS certificate EXPIRES IN FIVE DAYS", or something. It would be less shameful to have it than an expi
by nine_k 5y ago
I wish browsers showed a large warning like "This site's TLS certificate EXPIRES IN FIVE DAYS", or something.
It would be less shameful to have it than an expired certificate. But most of all, anyone handling the site would have an advance warning, instead of a catastrophic failure. This would lower the number of actual expirations significantly.
- jraph 5y agoIt would be terrible for visitors who have no clue on what a certificate is, or even what HTTP is. It could be scary for them, they could even think they were "hacked".
- KMag 5y agoI think that a bunch of things like the JavaScript console, DOM editor, etc. should only be enabled when a browser developer mode has been activated, and such a mode would also enable a variety of warnings like this. It shouldn't be difficult to find or enable the developer mode, but it shouldn't be on by default. That way, people who know (or should know) what these sorts of warnings mean will see them without ordinary users getting unnecessarily scared or confused. Hopefully a site's own developers regularly view their own site in the same browser they've used in the past for debugging the site.
- hakre 5y agoa certificate is either valid or its not. this is more for administering it or for users that rely on it and want to know within build systems, at least that is where it did hit me. the failure then, the same. wondered although if there is some use in knowing an upcoming expiration. # curl + GNU date + GNU grep -P $ echo "cert days left: ~$(( ($(date +%s -d "$(curl -IvsS https://www.w3.org 2>&1 >/dev/null | grep -Po '(?<=^\* expire date: ).*')")-$(date +%s))/86400 ))" cert days left: ~396 but then what should the information give? that my build breaks, say next Tuesday? and what if until then the certificate expiration is enlarged?