Contents
What does rolling your own crypto mean?
Rolling your own crypto means that you write your own cryptographic libraries. This has huge potential for errors as this is a very precise science. One error and the whole idea falls to the ground because the thing you think you have encrypted correctly is open to the world.
Why not to roll your own crypto?
You Really Shouldn’t Roll Your Own Crypto: An Empirical Study of Vulnerabilities in Cryptographic Libraries. The security of the Internet rests on a small number of open-source cryptographic libraries: a vulnerability in any one of them threatens to compromise a significant percentage of web traffic.
Who created Blowfish?
Bruce Schneier
Blowfish is an encryption algorithm, or cipher, specifically a block cipher. Blowfish has a 64-bit block size and it supports key lengths of 32-448 bits. It is fully in the public domain, open-source and royalty-free as per its creator, Bruce Schneier.
Why is it bad to roll your own cryptography?
Easy for a newbie to understand. Clear and explicit in why rolling your own is a bad idea. Provides strong examples. Obligatory xkcd. You can roll your own, but you probably will make a major security mistake if you are not an expert in security/cryptography or have had your scheme analyzed by multiple experts.
Is there a story about Navy developing their own ciphers?
There is a story in “The American Black Chamber”* about the Navy developing their own ciphers. The Navy would show their new cryptosystem, pleased with themselves and Yardley, the Army analyst, would promptly break the code, explaining what they had done wrong.
Why is rolling your own a bad idea?
With that in mind, I’m looking for a canonical answer, with the following properties: Easy for a newbie to understand. Clear and explicit in why rolling your own is a bad idea. Provides strong examples. Obligatory xkcd.