About & Contact

Who publishes Crypto Lab, how it is licensed, and how to reach me.

What this is

Crypto Lab is a collection of browser-based cryptography demonstrations. Every lab runs entirely in your browser — there is no backend, no account, and nothing is uploaded. Each one takes a single idea and makes it something you can operate: generate the keys, run the attack, watch the check fail.

The labs are teaching demonstrations, not hardened software. They are built to be read and taken apart rather than deployed, and several of them exist specifically to show how a thing breaks. Nothing here should be used to protect real secrets.

Who publishes it

Publisher

Paul A. Clark

Affiliation

Paul A. Clark works at the Leon County Public Library. Crypto Lab is a personal project, built and published in a personal capacity. It is not a library project, it is not published by or on behalf of the library, and nothing here should be read as a statement by that institution.

Licensing

Code

The catalog and each lab's source are released under the MIT licence. Each lab repository carries its own copy.

Teaching materials

The module pages, worksheets and instructor notes under /teach/ are released under CC BY 4.0. You may print, adapt, translate and build on them, including commercially, provided you give credit. The full licence text sits beside those pages.

Related work

CrypTool and CrypTool-Online are a long-running open-source cryptography education project, offering interactive tools and learning material covering both classical and modern cryptography. They cover a great deal that Crypto Lab does not, and are worth your time if you are learning or teaching this subject.

CrypTool-Online lists Crypto Lab on its links page.

Crypto Lab and the CrypTool project are separate and independent. Linking in either direction is not endorsement, partnership, or affiliation, and neither project speaks for the other.

Contact

The most useful way to reach me about a lab is to open an issue on its repository — a correction, a broken page, or a source I have got wrong all go furthest there, because the report sits next to the code it concerns.

• github.com/systemslibrarian — all repositories
• Issues on the catalog — for the hub, the teaching layer, or anything spanning several labs

Corrections are genuinely welcome. Several labs carry wording that changed because somebody filed an issue pointing at a paper I had not cited properly.