this post was submitted on 21 Jan 2024
69 points (91.6% liked)

Privacy

31993 readers
553 users here now

A place to discuss privacy and freedom in the digital world.

Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.

In this community everyone is welcome to post links and discuss topics related to privacy.

Some Rules

Related communities

Chat rooms

much thanks to @gary_host_laptop for the logo design :)

founded 5 years ago
MODERATORS
 

disclaimer: I'm just asking to get understanding of the theory behind network traffic encryption, I know this doesn't happen irl most likely.

Let's take https connection for example. I like watching revolutionary things on youtube and do not wish for authorities to know what I am watching, we accept here for the sake of showcase that google won't sell my watch history if asked (LMAO what am I even saying?).
So if I'm not mistaken since youtube has https implemented, our communication is encrypted, the keys are shared only between me and youtube. But when Youtube shares the key with me/my client the first time, is that also encrypted? Wouldn't the same question keep getting answered until there is something unencrypted? I know this is a bit too much unlikely, but if ISP automated the process of gathering keys and decrypting web traffic for a certain site with them for all users, would that work for them?
I'm taking https here as an example, while I have the same question for like VPN.

EDIT: Thank you everybody. I am not a member of this community, but every comment was a golden experience to read!

you are viewing a single comment's thread
view the rest of the comments
[–] Darkassassin07@lemmy.ca 5 points 10 months ago* (last edited 10 months ago) (2 children)

Youtube never knows the private half of your key pair. That never leaves your system.

Anything encrypted with the private half can only be decrypted with the public half, and anything encrypted with the public half can only be decrypted with the private half. These halves are known as the public key and the private key. Each side of the connection generates their own key pairs.

We both generate a set of keys, and exchange the public halves with each other. I then want to send you a message: I first encrypt it using my private key, I then encrypt it again using your public key and send that to you.

In order to read that message, you first decrypt it using your private key. This ensures the message was intended for you and wasn't modified in transit, as you are the only one with access to that private key and only its matching public key could have been used to encrypt that layer.

You then decrypt it a second time using my public key. As I'm the only one with access to my own private key, you can be sure the message was sent by me.

As long as that resulted in a readable message; You've now verified who sent the message, that it was intended for you, and that the contents have not been modified or read in transit.

All this, including the key exchange is handled for you by the https (tls) protocol every time you connect to a website. Each of the messages sent between you and the site are encrypted in this manner.

[–] zaknenou@lemmy.dbzer0.com 3 points 10 months ago (2 children)

so you can encrypt a message with my public key but you cannot decrypt it afterward ??

[–] deluxeparrot@thelemmy.club 4 points 10 months ago* (last edited 10 months ago)

The best way I find to think about it is a padlocked box.

The public key is a box with an open padlock on it. I can give it to anyone. If someone puts a message inside the box they can lock the padlock, but they don't have the key to open it again.

I keep the key private. If someone sends me a locked box that has my padlock on it, only I have the key to open it and read the message.

[–] Darkassassin07@lemmy.ca 3 points 10 months ago

Exactly. Once encrypted with your public key, you're the only one who can decrypt and read it as you are the only one with access to your private key.

[–] intensely_human@lemm.ee -2 points 10 months ago (1 children)

Anything encrypted with the private half can only be decrypted with the public half, and anything encrypted with the public half can only be decrypted with the private half.

This is not true. In key pair cryptography, the public key used only for encryption and the private key is used only for decryption.

[–] Darkassassin07@lemmy.ca 2 points 10 months ago (2 children)

As far as I understand a key pair can be used bi-directionally like I'd described. Was I mistaken?

In practice, the private key is usually used to create signatures instead, but I avoided that for simplicity.

[–] azdle@news.idlestate.org 3 points 10 months ago* (last edited 10 months ago)

You're not mistaken, it is definitely possible with at least RSA, though, I would guess it may not always be possible. It also sounds like it's still a bad idea unless you know all of the parameters used to generate the keys and can be sure what information is actually encoded in the keys.

[–] chayleaf@lemmy.ml -1 points 10 months ago

no, it isn't bidirectional, public = encrypt, private = decrypt, that's it. You can address a message to multiple recipients though (when using GPG), so often in case of email a message is addressed both to yourself and your recipient, so both you and your recipient have access to message text