Releases: dbsystel/TUPW
v6.1.4
New release because of several changes one of which is a breaking change:
- Small changes in Base32Encoding
- Refactored ProtectedByteArray
- Deprecated "DecryptData" methods are removed
- Ensure deletion of sensitive data
- Ensure "equals" always clears sensitive data in SecureSecretKeySpec.
- Corrected entropy threshold constant
The breaking change is the removal of the "DecryptData" methods. Please use one of the replacement methods.
v5.4.2
Corrected wrong method and variable names.
SonarLint fixes
In this release several SonarLint findings where fixed.
While most of them were just cosmetics there was a bug in SecureSecretKeySpec that used a bitwise and-operator instead of a logical and-operator. That bug did not break anything but has been corrected anyway.
Now SecureSecretKeySpec also adheres to the Serializable interface. That part was missing from true SecretKeySpec interchangeability.
V5.3.0: New copy- and script-friendly encoding of the encrypted data
This release brings a new encoding of the encrypted data. There are no more any special characters in the encrypted data string. This makes it easier to use the values in scripts and they can be copied by double-clicking the string.
V5.2.2: Improvement in ArbitraryTailPadding
This release brings a small improvement in arbitrary tail padding.
V5.1.0: Fix bug in packed unsigned integer code
This release fixes a bug in the code for packed unsigned integers. This is a breaking change if you ever encoded something with a length greater than 16,447 bytes. Probably, nobody was hit by this bug.
V5.0.1: Add a few finals
In this release only some finals were added.
V5.0.0: Interface with byte and character arrays
In this release a switch was made from only encrypting and decrypting strings to handling byte and character arrays. This makes it possible to use byte and character arrays where the secrets can be safely deleted after use. Strings are immutable, so they stays in memory until the garbage collector clears them. With byte and character arrays the developer can control the deletion of secret data.