Cryptol

Cryptol
DeveloperGalois, Inc.
First appeared1980; 44 years ago (1980)
Stable release
3.2.0 / August 20, 2024; 4 months ago (2024-08-20)
Implementation languageHaskell, Python
PlatformAArch64, x86-64
OSLinux, macOS, Windows
LicenseBSD 3-clause
Websitewww.cryptol.net

Cryptol is a domain-specific programming language for cryptography developed by the Portland, Oregon based software development firm, Galois, Inc.[1][2] It is free and open-source software released under a BSD 3-clause software license.

The language was originally developed for use by the United States National Security Agency.[1][3] The language is also used by private firms that provide information technology systems, such as the American company Rockwell Collins provides to aerospace and defense contractors in the United States.[1]

The programming language is used for all aspects of developing and using cryptography, such as the design and implementation of new ciphers and the verification of existing cryptographic algorithms.[1][2][4] Cryptol is designed to allow a cryptographer to watch how stream processing functions in the program manipulate ciphers or encryption algorithms.[2]

References

  1. ^ a b c d "Cryptol-the-language-of-cryptology-now-available". December 2008. Retrieved 2015-05-05.
  2. ^ a b c GoogleBook linkSutcliffe, Geoff; Voronkov, Andrei, eds. (2006). Logic for Programming, Artificial Intelligence, and Reasoning: 12th International Conference, LPAR 2005, December 2–6, 2005, Proceedings ... / Lecture Notes in Artificial Intelligence). Montego Bay, Jamaica: Springer. p. 744. ISBN 978-3-540-30553-8.
  3. ^ The Next Wave, High Confidence Software and Systems (HCSS) (PDF), vol. 19, 2011, archived from the original (PDF) on 2014-07-14, retrieved 2014-07-07
  4. ^ Lewis, J.R.; Martin, B. (October 2003). "Cryptol: high assurance, retargetable crypto development and validation". Military Communications Conference, 2003. MILCOM 2003. IEEE. Vol. 2. Boston, Massachusetts: Armed Forces Communications & Electronics Association (AFCEA); IEEE Communications Society. pp. 820–825. doi:10.1109/MILCOM.2003.1290218. S2CID 8380437.