tiny-AES-c | Small portable AES128/192/256 in C

by kokke C Version: v1.0.0 License: Unlicense

X-Ray Key Features Code Snippets Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | tiny-AES-c Summary

tiny-AES-c is a C library. tiny-AES-c has no bugs, it has no vulnerabilities, it has a Permissive License and it has medium support. You can download it from GitHub.

Small portable AES128/192/256 in C

Support

Quality

Security

License

Reuse

Support

tiny-AES-c has a medium active ecosystem.

It has 3597 star(s) with 1213 fork(s). There are 137 watchers for this library.

It had no major release in the last 12 months.

There are 13 open issues and 137 have been closed. On average issues are closed in 31 days. There are 8 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of tiny-AES-c is v1.0.0

Quality

tiny-AES-c has no bugs reported.

Security

tiny-AES-c has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

tiny-AES-c is licensed under the Unlicense License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

tiny-AES-c releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of tiny-AES-c

Get all kandi verified functions for this library.

tiny-AES-c Key Features

No Key Features are available at this moment for tiny-AES-c.

tiny-AES-c Examples and Code Snippets

No Code Snippets are available at this moment for tiny-AES-c.

Community Discussions

Trending Discussions on tiny-AES-c

fwrite in C add extra binary characters at the end of file

C Convert char* to uint8_t []

Encrypt in PHP, decrypt in C

tiny-aes-c AES CTR 128 cuts off decrypted string in some cases

Problem with JavaScript AES 256 decryption of data that is encrypted in C

AES algorithm implementation in C

How to fix decryption of AES in C using MPI

C - tiny-aes-c and Javascript CryptoJS interoperability

C - Encrypt and decrypt a string with AES

Adding 16 to pointer?

QUESTION

fwrite in C add extra binary characters at the end of file

Asked 2021-Apr-20 at 12:26

Requirements:

I'm a developer but with near-zero experience with C until a week ago. For a project, I need to encrypt/decrypt source-code/text files and need to use C for that.

What I did?

I'm using Kokke/tony-AES-c library for it and implementing it with pkcs7 padding as explained in this Gist. The code I wrote is:

main.c

...

ANSWER

Answered 2021-Apr-20 at 12:26

In my_decrypt() when writing the decrypted data to the file the length determined with pkcs7_padding_data_length() is not used: int out_len = sizeof(hexarray) must be replaced by int out_len = actualDataLength. This makes the decryption work on my machine.

Furthermore the padding of the ciphertext in my_decrypt() makes no sense. It also has no effect here, since pkcs7_padding_pad_buffer() does not pad due to data_length + pad_byte > buffer_size (and pkcs7_padding_valid() indicates an invalid padding).

Also, the key should not be padded. If the key does not have the length defined for AES, it is better to display an error message. If a password is to be used instead of the key, a reliable key derivation function like PBKDF2 should be used.

Finally, for security reasons, don't apply a static IV.

Source https://stackoverflow.com/questions/67173664

QUESTION

C Convert char* to uint8_t []

Asked 2020-Jul-03 at 20:39

I'm working on a program that receives an encrypted string. For this I'm using tiny-AES-c library.

The encrypted string I'm receiving is char*. In order to use the string with the function AES_CBC_decrypt_buffer(struct AES_ctx* ctx, uint8_t* buf, uint32_t length) I will need to convert the string to uint8_t [].

This is how the tiny-AES-c library likes the format, as seen in their test.c:

...

ANSWER

Answered 2020-Jul-03 at 20:39

This could be as simple as:

Source https://stackoverflow.com/questions/62722353

QUESTION

Encrypt in PHP, decrypt in C

Asked 2020-Jul-02 at 07:47

I'd like to encrypt a string in PHP and then decrypt it in C. I'm stuck on the decryption part.

(PHP) I first encrypt the string:

...

ANSWER

Answered 2020-Jul-02 at 07:47

In the PHP code, AES-256 is used. tiny-AES-c only supports AES-128 by default. In order for AES-256 to be supported, the corresponding constant must be defined in aes.h, i.e. the line //#define AES256 1 must be commented in, here.
PHP uses PKCS7 padding by default. The padding should be removed in the C code.
PHP implicitly pads too short keys with zero values to the specified length. Since AES-256-CBC was specified in the PHP code, the key test is extended as follows:

Source https://stackoverflow.com/questions/62683340

QUESTION

tiny-aes-c AES CTR 128 cuts off decrypted string in some cases

Asked 2020-Mar-26 at 19:39

I've been trying to use the AES CTR 128 from tiny-aes-c (https://github.com/kokke/tiny-AES-c) to encrypt a randomly generated token, and it works, but not all the time. In some cases the retrieved string after encrypting and decrypting is cut off at some point. Here's the code:

...

ANSWER

Answered 2020-Mar-26 at 19:39

The first call to AES_CTR_xcrypt_buffer encrypts the buffer in place in CTR mode.

The buffer still has the same size (128 in your case), but can contain NUL bytes.

The strlen call in the second call of AES_CTR_xcrypt_buffer for decryption can therefore result in a length < 128 if the buffer contains a NUL byte. By the way: It works in cases where the encryption does not result in a NUL byte in the buffer.

So if you call it with TOKEN_LENGTH as the length parameter decryption will give the original string again:

Source https://stackoverflow.com/questions/60873890

QUESTION

Problem with JavaScript AES 256 decryption of data that is encrypted in C

Asked 2020-Jan-26 at 21:19

When I do AES-256 CTR encryption in C using tiny-AES-c library (https://github.com/kokke/tiny-AES-c) I unable to decrypt it properly in JavaScript. For JavaScript decryption I'm using library https://github.com/ricmoo/aes-js

After encryption I do base 64 encode and before decryption base 64 decode and that part works fine.

In fields below you can see my C and JavaScript code:

C code

...

ANSWER

Answered 2020-Jan-26 at 21:19

You need to pass entire IV as initial counter value:

Source https://stackoverflow.com/questions/59917834

QUESTION

AES algorithm implementation in C

Asked 2019-Oct-17 at 05:30

Can anyone share me AES algorithm code with Input and Key details in C, i have checked this link https://github.com/kokke/tiny-AES-c/blob/master/aes.c, but couldn't conclude as it not has the main() function.

Thanks in advance

...

ANSWER

Answered 2019-Oct-17 at 05:29

Check AES implementation in OpenSSL: https://github.com/openssl/openssl/blob/master/crypto/aes/aes_core.c

Source https://stackoverflow.com/questions/58425364

QUESTION

How to fix decryption of AES in C using MPI

Asked 2019-Oct-03 at 21:50

Currently I am trying to use MPI to pass a particular encrypted data from one processor to another using only 2 processor to just check if encryption or decryption is working. I have an int value which is converted to string for encryption and then sent to processor rank 1. I am receiving the string correctly in processor but when I call the decryption function it seems to not give me the plaintext. I have downloaded the AES code from https://github.com/kokke/tiny-AES-C

...

ANSWER

Answered 2019-Oct-03 at 21:50

First of all we must install requirements. see this link

After successfully install the requirements we run simple hello world MPI.

Hello World!

Source https://stackoverflow.com/questions/58199071

QUESTION

C - tiny-aes-c and Javascript CryptoJS interoperability

Asked 2018-May-13 at 21:18

Using tiny-aes-c. Consider the following C code:

...

ANSWER

Answered 2018-May-10 at 15:03

You are doing two things

Encrypt
Convert to base64

Upon receiving, you must do the reverse operations of both of these, in the reverse order they were applied before transmitting

Convert from base64
Decrypt

You can also swap the order of the steps, but then the order must be swapped on both the transmitting and receiving sides.

Also make sure the secret is on the same format on both sides.

Source https://stackoverflow.com/questions/50274899

QUESTION

C - Encrypt and decrypt a string with AES

Asked 2018-May-10 at 08:30

I'm trying to understand how to use this c library (tiny-AES-c). As a web developer, I'm looking to get an equivalent C code for this JS fiddle.

The JS code is straightforward:

...

ANSWER

Answered 2018-May-09 at 14:01

uint8_t in[16]  = "my message";

Source https://stackoverflow.com/questions/50254710

QUESTION

Adding 16 to pointer?

Asked 2017-Oct-27 at 06:58

Was looking at TinyAES(https://github.com/kokke/tiny-AES-c/blob/master/aes.c) , and I came across a snippet of code that I don't understand.

Assuming AES-128(meaning 16 byte key, and block size), wouldn't adding 16 to the output result in 0, since the for loop will only iterate once?

Main AES-CBC encryption function.

...

ANSWER

Answered 2017-Oct-27 at 06:19

It's the length of the input not the key. Key length is determined using macro.

If you have length of input as 16 then yes just once it will execute.

We are not adding 16 to the output of result. Check the algorithm carefully.

Source https://stackoverflow.com/questions/46968464

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install tiny-AES-c

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: