st-decrypt | Utility for encrypting/decrypting ST-Link firmware images | Encryption library

by lujji Java Version: Current License: No License

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

kandi X-RAY | st-decrypt Summary

st-decrypt is a Java library typically used in Security, Encryption, Ubuntu applications. st-decrypt has no bugs, it has no vulnerabilities and it has low support. However st-decrypt build file is not available. You can download it from GitHub.

Utility for encrypting/decrypting ST-Link firmware images

Support

Quality

Security

License

Reuse

Support

st-decrypt has a low active ecosystem.

It has 92 star(s) with 24 fork(s). There are 15 watchers for this library.

It had no major release in the last 6 months.

There are 1 open issues and 0 have been closed. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of st-decrypt is current.

Quality

st-decrypt has 0 bugs and 0 code smells.

Security

st-decrypt has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

st-decrypt code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

st-decrypt does not have a standard license declared.

Check the repository for any license declaration and review the terms closely.

Without a license, all rights are reserved, and you cannot use the library in your applications.

Reuse

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

st-decrypt 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.

It has 1697 lines of code, 21 functions and 4 files.

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

Top functions reviewed by kandi - BETA

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

Main entry point
Encrypt a firmware file
Returns the unsigned 16 - bit integer
Returns u32 of a 32 - bit integer
Returns the 16 - bit unsigned integer stored in an integer
Pack unsigned 32 bits
Calculate a polynomial
Convert an integer to a number
Calculate a power of two integers
Closes the stream
Append byte array
Convert string to byte array
Calculate the power of 2
Encodes the given array and writes it to the device
Dumpfw firmware to a file
Reads the 4 bytes of the firmware
Decode key - value pair
Determines the length of the firmware file
Decrypt a firmware file
Dump a byte array to a file

Get all kandi verified functions for this library.

st-decrypt Key Features

No Key Features are available at this moment for st-decrypt.

st-decrypt Examples and Code Snippets

No Code Snippets are available at this moment for st-decrypt.

Community Discussions

Trending Discussions on st-decrypt

BadPaddingException: mac check in GCM failed

QUESTION

BadPaddingException: mac check in GCM failed

Asked 2019-Sep-24 at 11:57

I am trying to encrypt/decrypt using AES-GCM and JDK 1.8 CipherOutputStream, But getting BadPaddingException during decryption. I am using same IV and secret key during encryption and decryption, but not sure what is going wrong. Please see the code below:

...

ANSWER

Answered 2019-Sep-24 at 11:57

Encryption doesn't work properly: In encrypt, CipherOutputStream#close must be called before FileOutputStream#close. This is because CipherOutputStream#close calls Cipher#doFinal that generates the tag and appends it to the ciphertext. This portion can only be written to the FileOutputStream-instance if FileOutputStream#close has not yet been called. By the way, CipherOutputStream#flush doesn't need to be called.
There is also a problem with decryption: In decrypt, outputStream.write(data) must be replaced by outputStream.write(data, 0, read). Otherwise usually too much data will be written to the FileOutputStream-instance.
The classes javax.crypto.CipherInputStream and javax.crypto.CipherOutputStream may perform the authentication false positive and are therefore not suitable for GCM-mode, e.g. from the documentation (Java 12) for CipherInputStream:

This class may catch BadPaddingException and other exceptions thrown by failed integrity checks during decryption. These exceptions are not re-thrown, so the client may not be informed that integrity checks failed. Because of this behavior, this class may not be suitable for use with decryption in an authenticated mode of operation (e.g. GCM). Applications that require authenticated encryption can use the Cipher API directly as an alternative to using this class.

Therefore, either the Cipher API should be used directly, as recommended in the documentation, or the BouncyCastle-implementations org.bouncycastle.crypto.io.CipherInputStream and org.bouncycastle.crypto.io.CipherOutputStream, e.g. for encryption:

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

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

Vulnerabilities

No vulnerabilities reported

Install st-decrypt

You can download it from GitHub.
You can use st-decrypt like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the st-decrypt component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

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: