![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
My company still uses SVN, but we have almost 20 years of history in the repository, not including the autogenerated commits from when we migrated from CVS.
My department would like for us to move to git (some sub projects have) but it’s important for our process to retain the history and nobody has had the time to figure out if the migration would be clean then update all of our auto-testing infrastructure (which itself is over a decade old) to use git, all while not stopping active development.
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.