• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..15-Feb-2021-

README.mdH A D15-Feb-20211.5 KiB1711

aes.cH A D15-Feb-202141.4 KiB1,096822

aes.hH A D15-Feb-20217.4 KiB12472

aes_test.cH A D15-Feb-20219.7 KiB286139

arcfour.cH A D15-Feb-20211.3 KiB4829

arcfour.hH A D15-Feb-20211.2 KiB317

arcfour_test.cH A D15-Feb-20211.6 KiB4826

base64.cH A D15-Feb-20213.8 KiB136102

base64.hH A D15-Feb-20211.1 KiB287

base64_test.cH A D15-Feb-20212.4 KiB5533

blowfish.cH A D15-Feb-202116.1 KiB270236

blowfish.hH A D15-Feb-20211.3 KiB3314

blowfish_test.cH A D15-Feb-20212.6 KiB6941

crypto_types.hH A D15-Feb-2021592 165

des.cH A D15-Feb-202112.3 KiB270208

des.hH A D15-Feb-20211.4 KiB3815

des_test.cH A D15-Feb-20213.3 KiB8455

md2.cH A D15-Feb-20213.1 KiB10575

md2.hH A D15-Feb-20211.1 KiB3415

md2_test.cH A D15-Feb-20212.1 KiB5935

md5.cH A D15-Feb-20215.7 KiB190149

md5.hH A D15-Feb-20211 KiB3415

md5_test.cH A D15-Feb-20212 KiB6136

rot-13.cH A D15-Feb-20211.2 KiB3617

rot-13.hH A D15-Feb-2021761 215

rot-13_test.cH A D15-Feb-20211.3 KiB4521

sha1.cH A D15-Feb-20213.8 KiB150117

sha1.hH A D15-Feb-20211.1 KiB3516

sha1_test.cH A D15-Feb-20212 KiB5936

sha256.cH A D15-Feb-20215.1 KiB159120

sha256.hH A D15-Feb-20211.2 KiB3516

sha256_test.cH A D15-Feb-20212.4 KiB6239

README.md

1crypto-algorithms
2=================
3
4
5About
6---
7These are basic implementations of standard cryptography algorithms, written by Brad Conte (brad@bradconte.com) from scratch and without any cross-licensing. They exist to provide publically accessible, restriction-free implementations of popular cryptographic algorithms, like AES and SHA-1. These are primarily intended for educational and pragmatic purposes (such as comparing a specification to actual implementation code, or for building an internal application that computes test vectors for a product). The algorithms have been tested against standard test vectors.
8
9This code is released into the public domain free of any restrictions. The author requests acknowledgement if the code is used, but does not require it. This code is provided free of any liability and without any quality claims by the author.
10
11Note that these are *not* cryptographically secure implementations. They have no resistence to side-channel attacks and should not be used in contexts that need cryptographically secure implementations.
12
13These algorithms are not optimized for speed or space. They are primarily designed to be easy to read, although some basic optimization techniques have been employed.
14
15Building
16---
17The source code for each algorithm will come in a pair of a source code file and a header file. There should be no inter-header file dependencies, no additional libraries, no platform-specific header files, or any other complicating matters. Compiling them should be as easy as adding the relevent source code to the project.