I'm reading a webpage in elinks because Chromium has decided I can't override an expired cert, because HSTS
-
-
Replying to @edefic
Can everything just take a --jesus-christ-i-know-wtf-i-am-doing-just-let-me-get-on-with-my-daily-life-god-fucking-damn-it
3 replies 2 retweets 3 likes -
Replying to @edefic
@FrozenFire@bofh453 No.Next thing you know every shitty Windows website is telling people to put it "just in case".2 replies 0 retweets 1 like -
Replying to @whitequark
@whitequark@FrozenFire@bofh453 And part of the idea of using HSTS is that you want to avoid risk of old compromised certs being used.1 reply 0 retweets 0 likes -
Replying to @RichFelker
@whitequark@FrozenFire@bofh453 If expiration is [part of] your cert revocation model you don't want users easily tricked into ignoring it.1 reply 0 retweets 0 likes -
Replying to @RichFelker
@RichFelker@whitequark@FrozenFire IMO cert revocation based on anything other than "this cert is different than last time, wtf" is useless2 replies 0 retweets 0 likes
@bofh453 @whitequark @FrozenFire Pinning and Certificate Transparency address these issues, but expiration is important too.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.