this post was submitted on 14 Aug 2024
44 points (95.8% liked)

Programming

17433 readers
236 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[โ€“] booly@sh.itjust.works 4 points 3 months ago (1 children)

One time pads are perfect encryption, but the problem is that the key length needs to be longer than the message length. So if you have the ability to get the symmetric key to the recipient securely, then you had the ability to get the whole message to the recipient securely.

[โ€“] robojeb@lemmy.world 2 points 3 months ago

One time pads aren't really feasible at scale. Getting the pad (key) to your partner securely will involve moving it in meatspace.

If you tried to send the pad with some other encryption that becomes the weak point and defeats the pad.

You can't reuse the pad for multiple transmissions or you are vulnerable to analysis attacks.

You can't compress the pad and send it with remaining space of a previous pad because the pad has to be true random numbers and won't compress well so you will always come out behind.

They are great in theory, and in practice for a few fixed short form communications in emergency situations but I don't know of any practical way they could be used generally. Your bank isn't going to ship you a hard drive of random numbers for you to securely look at your account.