@Darkassassin07@lemmy.ca avatar

Darkassassin07

@Darkassassin07@lemmy.ca

🇨🇦

This profile is from a federated server and may be incomplete. Browse more on the original instance.

Darkassassin07, (edited )
@Darkassassin07@lemmy.ca avatar

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.

Darkassassin07,
@Darkassassin07@lemmy.ca avatar

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.

Darkassassin07,
@Darkassassin07@lemmy.ca avatar

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.

Darkassassin07, (edited )
@Darkassassin07@lemmy.ca avatar

Are they supporting FOSS, or looking to buy out the project to make it a closed in-house solution and avoid the bad publicity they created this last week?

Darkassassin07, (edited )
@Darkassassin07@lemmy.ca avatar

Yeah, but relying on peoples generosity is less than ideal unfortunately…

On the other hand; when you’ve got to pay to use a product, you’re a bit more entitled to its use and support than a free project that gets worked on at the devs leisure. Especially when the developers maintain that same view.

It’s a fine line between securing stable income for your efforts while not limiting the usage of your products. I think Embys developers have done a pretty good job keeping that balance. I’ve certainly never had an issue with the activation and use of premium features, and the licence I bought 7 years ago has held excellent value. I’ve just been waiting on some funds to donate ontop as I feel I’ve gotten more than I’ve paid for.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • localhost
  • All magazines
  • Loading…
    Loading the web debug toolbar…
    Attempt #