chosen-plaintext | small python library for exploiting simple chosen | Hacking library

by EiNSTeiN- Python Version: Current License: GPL-2.0

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

kandi X-RAY | chosen-plaintext Summary

chosen-plaintext is a Python library typically used in Security, Hacking applications. chosen-plaintext has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. However chosen-plaintext build file is not available. You can download it from GitHub.

Python framework for extracting plaintext data from a block cipher in ECB or CBC mode for the specific case where a user input is encrypted directly before a secret that needs to be recovered and the ciphertext can be observed by the attacker. Recovery is possible in the following cases: * Any ECB mode block cipher. * A CBC mode block cipher when the IV is static. * A CBC mode block cipher when the IV is predictable, and the attacker has full control on the first block. A few vulnerable samples are provided, one for each use case described above.

Support

Quality

Security

License

Reuse

Support

chosen-plaintext has a low active ecosystem.

It has 38 star(s) with 3 fork(s). There are 3 watchers for this library.

It had no major release in the last 6 months.

chosen-plaintext has no issues reported. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of chosen-plaintext is current.

Quality

chosen-plaintext has 0 bugs and 0 code smells.

Security

chosen-plaintext has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

chosen-plaintext code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

chosen-plaintext is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

chosen-plaintext releases are not available. You will need to build from source code and install.

chosen-plaintext has no build file. You will be need to create the build yourself to build the component from source.

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

chosen-plaintext saves you 128 person hours of effort in developing the same functionality from scratch.

It has 323 lines of code, 36 functions and 7 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed chosen-plaintext and discovered the below as its top functions. This is intended to give you an instant insight into chosen-plaintext implemented functionality, and help decide if they suit your requirements.

Runs the attack
Find block information
Find the first block of two blocks
Gets the ciphertext
Test if the ciphertext is consistent
Generate a random pair
Return a list of blocks
The IV
Encipher text using ciphertext
Return n random letters
Encapsulates the request
Receive a blob from the server
Encrypt data
Send data to the server

Get all kandi verified functions for this library.

chosen-plaintext Key Features

No Key Features are available at this moment for chosen-plaintext.

chosen-plaintext Examples and Code Snippets

No Code Snippets are available at this moment for chosen-plaintext.

Community Discussions

Trending Discussions on chosen-plaintext

AES Known-Plaintext-Attack and IV?

QUESTION

AES Known-Plaintext-Attack and IV?

Asked 2019-Jan-28 at 12:09

Edit: I address Known-Plaintext-Attack and Chosen-plaintext attack (both) with my question

I have a little problem understandig the right use of IV.

AES is only safe against Known-Plaintext-Attack if I use a different IV for every message. Right?

I need to know the used IV to decrypt a message. Also right?

AES that isn't protected against Known-Plaintext-Attack is a weak encryption. Right?

This means I have to store every IV with the encrypted data (e.g. in a extra DB column). Sounds like a lot of overhead.

Is there any solution to this problem?

...

ANSWER

Answered 2019-Jan-28 at 12:09

For a 128 bit message, a 96 bit IV (for AES in GCM mode as per NIST recommendation) might look like a big overhead. But usually the plain text messages to be encrypted are much larger than that. Much larger as compared to the fixed size 96 bit IV.

On the other hand, almost every safe encryption or hashing mechanisms need a kind of randomness in the form of IV, nonce, salt etc. Not just AES.

It's an overhead but that is a tradeoff for security.

Usually IV is appended or prepended with the ciphertext. And decryption logic knows where to find it in the cipher text.

Overhead is everywhere. For e.g. in an RDBMS table when we create an index, it's an overhead in terms of space and write processing time. But it's a tradeoff for fast query performance.

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

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

Vulnerabilities

No vulnerabilities reported

Install chosen-plaintext

You can download it from GitHub.
You can use chosen-plaintext like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

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: