Comment on They're F*ing trying again

• tux7350@lemmy.world ⁨1⁩ ⁨day⁩ ago

  But the central service for those keys is only sharing the public key. Only the recipient can decrypt the message.

  The only information it would give out is “this IP downloaded this public key”. Which can easily be covered up with multiple downloads from different IPs. You really only need to do this once per recipient too, once you have the public key you can just always keep a copy.

  Shit, if your already using GnuPG, encrypt a file that’s got all your friends public keys. When you need to send a message, decrypt your file and grab the key you need.

  source

  • TootSweet@lemmy.world ⁨1⁩ ⁨day⁩ ago

    It’s true that the public keys aren’t sensitive and nothing is compromised (in fact, it’s recommended) if the public key is available from, say, a key server.

    But MITM is always a concern. Public-key encryption is supposed to mitigate that by ensuring that any third-party listening in in the middle can only get the ciphertext and cannot derive the plaintext of the communication.

    But, if a jurisdiction legally forces a rule like the “we get to snoop on everything” one in this law, it changes things. They could, for instance, force key servers to to only give out keys that are generated/controlled by the EU agency so that they can MITM to their heart’s content. My guess at Aniki’s thought process is that if there’s a central distributor of keys, that can be legally strong-armed into bad things, but the people you’ve talked directly to are a different matter. “Web of trust” as it were.

    I do think there are probably better ways to deal with that than what Aniki’s getting at, though. If you have Alice’s public key, you can verify signatures she generated, and you can be sure (hand-waves, rubber-hoses, caveat emptor, blah blah blah) that if you have a valid signature signing Bob’s public key with Alice’s private key, Alice vouches for that specific public key being authentically Bob’s public key.

    Now, if you only ever get public keys from a small set of (compromiseable) central key servers, then the very first public key you get could be compromised and any other signature generated from the associated private key could be forged by an adversarial party (like the EU.) And theoretically the EU could generate a whole counterfeit web of signatures. So there’s benefit to having at least some of the public keys you trust come directly from the one who generated the key through a known-secure channel.

    Before this law goes into effect, (maybe) we can trust at least some of the signatures in public key servers and use those as a basis for secure communication from which we can create a pool of known-uncompromised (qualifier, caveat, tin hats, etc) public keys, and based on those (maybe) detect forgeries and such.

    (Mind you, I don’t know the details of this law or whatever. It might be that the law as written will require, say, GnuPG to introduce backdoors. Not that I think they should, no matter what the law says, but it might be that the EU isn’t really likely to engage in quite the lever of subterfuge that I’ve outlined above. It might be more of a blatant “fuck you, we’re the government and you’re going to comply” approach than a sneaky-sneaky trick-everybody-into-thinking-they’ve-got-security-they-don’t approach.)

    source

    • locahosr443@lemmy.world ⁨1⁩ ⁨day⁩ ago

      Yeah they could MITM to give false keys so they can decrypt before sending on again using the real key, but if that’s what they want to do then it would be much more effective at monitoring people who are actively engaging in protecting their communication do just do that quietly rather than this circus.

      This is probably more a combination of boomer levels of technical understanding and incrementally shifting the norm away from any expectation of privacy.

      source