this post was submitted on 09 Sep 2025
521 points (99.1% liked)

Microblog Memes

9149 readers
2489 users here now

A place to share screenshots of Microblog posts, whether from Mastodon, tumblr, ~~Twitter~~ X, KBin, Threads or elsewhere.

Created as an evolution of White People Twitter and other tweet-capture subreddits.

Rules:

  1. Please put at least one word relevant to the post in the post title.
  2. Be nice.
  3. No advertising, brand promotion or guerilla marketing.
  4. Posters are encouraged to link to the toot or tweet etc in the description of posts.

Related communities:

founded 2 years ago
MODERATORS
 

article

toot

easily contact your MEP: https://fightchatcontrol.eu/

you are viewing a single comment's thread
view the rest of the comments
[–] IphtashuFitz@lemmy.world 9 points 1 day ago (1 children)

Blocking HTTPS would be frighteningly hilarious. My employer is one of thousands of websites that utilizes HSTS, which tells web browsers to use HTTPS. Our implementation of HSTS, like lots of banks etc. is also listed with HSTSpreload, which means browsers like chrome will only ever use HTTPS with our site.

[–] tgxn@lemmy.tgxn.net 3 points 23 hours ago (1 children)

What if they just do MITM with a Trusted root? Does HSTS provide a method to do cert pinning?

[–] IphtashuFitz@lemmy.world 2 points 23 hours ago

HSTS just enforces HTTPS over HTTP.

I seriously doubt Chrome or Firefox would ever be coerced into trusting a cert like that. If they did then you would see a very rapid shift away from those browsers to one or more of the open source alternatives.

And any CA that issued such a cert that allowed for wholesale MITM access like that would be blacklisted by all the browsers very quickly as well. That would put the CA out of business very quickly.