Tiny AES128 in C alternatives and similar libraries
Based on the "Cryptography" category.
Alternatively, view Tiny AES128 in C alternatives based on common mentions on social networks and blogs.
OpenSSL9.8 9.9 L2 Tiny AES128 in C VS OpenSSLTLS/SSL and crypto library
libsodium9.3 5.6 L3 Tiny AES128 in C VS libsodiumA modern, portable, easy to use crypto library.
mbedTLS8.7 10.0 L2 Tiny AES128 in C VS mbedTLSAn open source, portable, easy to use, readable and flexible TLS library, and reference implementation of the PSA Cryptography API.
Crypto++8.3 1.0 L1 Tiny AES128 in C VS Crypto++free C++ class library of cryptographic schemes
s2n8.2 8.9 L3 Tiny AES128 in C VS s2nAn implementation of the TLS/SSL protocols
Botan7.2 9.7 L1 Tiny AES128 in C VS BotanCryptography Toolkit
LibTomCrypt6.7 5.4 L3 Tiny AES128 in C VS LibTomCryptLibTomCrypt is a fairly comprehensive, modular and portable cryptographic toolkit that provides developers with a vast array of well known published block ciphers, one-way hash functions, chaining modes, pseudo-random number generators, public key cryptography and a plethora of other routines.
Themis by Cossack Labs6.2 5.6 L3 Tiny AES128 in C VS Themis by Cossack LabsEasy to use cryptographic framework for data protection: secure messaging with forward secrecy and secure data storage. Has unified APIs across 14 platforms.
LibreSSL6.1 4.3 L4 Tiny AES128 in C VS LibreSSLLibreSSL Portable itself. This includes the build scaffold and compatibility layer that builds portable LibreSSL from the OpenBSD source code. Pull requests or patches sent to [email protected] are welcome.
Bcrypt5.5 9.2 L3 Tiny AES128 in C VS BcryptModern(-ish) password hashing for your software and your servers
libhydrogen4.2 2.6 Tiny AES128 in C VS libhydrogenA lightweight, secure, easy-to-use crypto library suitable for constrained environments.
digestpp3.0 4.3 Tiny AES128 in C VS digestppC++11 header-only message digest library
retter2.4 0.0 L3 Tiny AES128 in C VS retterA collection of hash functions, ciphers, tools, libraries, and materials related to cryptography & security. :closed_lock_with_key::closed_lock_with_key::closed_lock_with_key::closed_lock_with_key::closed_lock_with_key: (project was renamed, libchaos is main)
mbedcrypto1.9 0.8 Tiny AES128 in C VS mbedcryptoa portable, small, easy to use and fast c++14 library for cryptography.
GnuTLS1.1 0.0 L2 Tiny AES128 in C VS GnuTLSGnuTLS
GnuPG1.0 0.0 L1 Tiny AES128 in C VS GnuPGMirror of git://git.gnupg.org/gnupg.git — master branch contains no changes from upstream.
BeeCryptA portable and fast cryptography library. [LGPLv2.1+]
NettleA low-level cryptographic library. [LGPL]
LibgcryptA general purpose cryptographic library originally based on code from GnuPG. [LGPLv2.1+]
Write Clean C++ Code. Always.
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Tiny AES128 in C or a related project?
Tiny AES in C
This is a small and portable implementation of the AES ECB, CTR and CBC encryption algorithms written in C.
You can override the default key-size of 128 bit with 192 or 256 bit by defining the symbols AES192 or AES256 in
The API is very simple and looks like this (I am using C99
<stdint.h>-style annotated types):
/* Initialize context calling one of: */ void AES_init_ctx(struct AES_ctx* ctx, const uint8_t* key); void AES_init_ctx_iv(struct AES_ctx* ctx, const uint8_t* key, const uint8_t* iv); /* ... or reset IV at random point: */ void AES_ctx_set_iv(struct AES_ctx* ctx, const uint8_t* iv); /* Then start encrypting and decrypting with the functions below: */ void AES_ECB_encrypt(const struct AES_ctx* ctx, uint8_t* buf); void AES_ECB_decrypt(const struct AES_ctx* ctx, uint8_t* buf); void AES_CBC_encrypt_buffer(struct AES_ctx* ctx, uint8_t* buf, size_t length); void AES_CBC_decrypt_buffer(struct AES_ctx* ctx, uint8_t* buf, size_t length); /* Same function for encrypting as for decrypting in CTR mode */ void AES_CTR_xcrypt_buffer(struct AES_ctx* ctx, uint8_t* buf, size_t length);
- No padding is provided so for CBC and ECB all buffers should be multiples of 16 bytes. For padding PKCS7 is recommendable.
- ECB mode is considered unsafe for most uses and is not implemented in streaming mode. If you need this mode, call the function for every block of 16 bytes you need encrypted. See wikipedia's article on ECB for more details.
- This library is designed for small code size and simplicity, intended for cases where small binary size, low memory footprint and portability is more important than high performance. If speed is a concern, you can try more complex libraries, e.g. Mbed TLS, OpenSSL etc.
You can choose to use any or all of the modes-of-operations, by defining the symbols CBC, CTR or ECB in
aes.h (read the comments for clarification).
C++ users should
#include aes.hpp instead of aes.h
There is no built-in error checking or protection from out-of-bounds memory access errors as a result of malicious input.
The module uses less than 200 bytes of RAM and 1-2K ROM when compiled for ARM, but YMMV depending on which modes are enabled.
It is one of the smallest implementations in C I've seen yet, but do contact me if you know of something smaller (or have improvements to the code here).
I've successfully used the code on 64bit x86, 32bit ARM and 8 bit AVR platforms.
GCC size output when only CTR mode is compiled for ARM:
$ arm-none-eabi-gcc -Os -DCBC=0 -DECB=0 -DCTR=1 -c aes.c $ size aes.o text data bss dec hex filename 1171 0 0 1171 493 aes.o
.. and when compiling for the THUMB instruction set, we end up well below 1K in code size.
$ arm-none-eabi-gcc -Os -mthumb -DCBC=0 -DECB=0 -DCTR=1 -c aes.c $ size aes.o text data bss dec hex filename 903 0 0 903 387 aes.o
I am using the Free Software Foundation, ARM GCC compiler:
$ arm-none-eabi-gcc --version arm-none-eabi-gcc (4.8.4-1+11-1) 4.8.4 20141219 (release) Copyright (C) 2013 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
This implementation is verified against the data in:
National Institute of Standards and Technology Special Publication 800-38A 2001 ED Appendix F: Example Vectors for Modes of Operation of the AES.
The other appendices in the document are valuable for implementation details on e.g. padding, generation of IVs and nonces in CTR-mode etc.
A heartfelt thank-you to all the nice people out there who have contributed to this project.
All material in this repository is in the public domain.