this post was submitted on 10 Nov 2023
518 points (98.9% liked)

Technology

59622 readers
2880 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago
MODERATORS
[email protected]
[email protected]
[email protected]
[email protected]
[email protected]
518
EU Article 45 requires that browsers trust certificate authorities appointed by governments (www.eff.org)
submitted 1 year ago by [email protected] to c/[email protected]
111 comments fedilink hide all child comments
 

EU Article 45 requires that browsers trust certificate authorities appointed by governments::The EU is poised to pass a sweeping new regulation, eIDAS 2.0. Buried deep in the text is Article 45, which returns us to the dark ages of 2011, when certificate authorities (CAs) could collaborate with governments to spy on encrypted traffic—and get away with it. Article 45 forbids browsers from...

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 41 points 1 year ago

There can be an infinite amount of certificates for a single domain.

When you setup a connection to a website you basically get a response back that has been signed with a certificate.

Your Browser / OS has a list of certification authorities that it deems trustworthy.

So when you get the response the browser checks if the certificate was issued by a trusted CA.

Now, if the EU forces browsers to trust their CA they can facilitate a man-in-the-middle attack.

In this instance they will intercept the TLS Handshake and give you back a response that was signed by their certificate. Your Browser deems the certificate valid and sets up a secure tunnel to the EUs Server.

From then on they can forward packets between you and the real website while being able to read everything in cleartext