This site was created because I shouldn't have to reread FIPS or paw through IACR archives just to find out whether $SOME_CRYPTOGRAPHIC_SCHEME is $PROVABLE_SECURITY_DEFINITION or not. It's not that I don't love poking around to see what's out there, it's just that somebody should probably be caching the answers somewhere.
I do not have a crypto PhD, and even if I did, human beings are generally terrible at reasoning about crypto (except for DBJ. All hail DBJ).
I have contributed some starter content to this website to get the ball rolling, but it might as well be "Lorem ipsum". That starter content isn't the point. The point is to provide an example of how this kind of reference content can --and IMHO should-- be organized.
The dream here is that someday, this site will be a battle-tested field guide for anyone looking to choose a cryptographic scheme or algorithm.
In order to make that dream a reality, I need readers like YOU to come yell at me, and explain how terribly wrong and misguided I am.
A special extra note: Please let me know if this website duplicates a similar cataloging project.
If so, I will HAPPILY delete this site and migrate over any suitable content.
(see also: xkcd.com: Standards)
Copyright © 2021 cryptalgo - All Rights Reserved.
At least in the United States, copyright itself is inherently and automatically created as soon as an idea is "fixed in a tangible medium of expression".
The "Copyright © $YEAR $COPYRIGHT_HOLDER" boilerplate is not the mechanism by which that right is created. Rather, that statement makes explicit claims about the creation date and holder of that implicit right.
If one were to consider the cryptographic security of those claims, one might define a cryptographic game InfringeCopyright and attempt to prove an upper bound on the advantage wielded by some class of adversaries (subject to certain restrictions on computational power). Such analysis is beyond the scope of this website for two reasons: