Amazon DynamoDB Encryption Client for Java
APACHE-2.0 License
Bot releases are hidden (Show)
Published by texastony almost 3 years ago
Published by alex-chew about 3 years ago
Published by josecorella about 3 years ago
Published by robin-aws over 3 years ago
Fixes released jar files to ensure JDK 8 compatibility.
Published by robin-aws over 3 years ago
Fixes released jar files to ensure JDK 8 compatibility.
Published by lavaleri over 3 years ago
Removes MostRecentProvider. MostRecentProvider is replaced by CachingMostRecentProvider as of 1.15.0.
Published by lavaleri over 3 years ago
Adds the CachingMostRecentProvider and deprecates MostRecentProvider.
Time-based key reauthorization logic in MostRecentProvider did not re-authorize the use of the key after key usage permissions were changed at the key provider (for example AWS Key Management Service). This created the potential for keys to be used in the DynamoDB Encryption Client after permissions to do so were revoked.
CachingMostRecentProvider replaces MostRecentProvider and provides a cache entry TTL to reauthorize the key with the key provider.
MostRecentProvider is now deprecated, and is removed in 2.0.0. See https://docs.aws.amazon.com/dynamodb-encryption-client/latest/devguide/most-recent-provider.html#mrp-versions for more details.
1.15.0 also fixes interoperability issues between the Python and Java implementations of DynamoDB Encryption Client.
Published by johnwalker almost 6 years ago
Published by SalusaSecondus about 6 years ago
This minor release contains a potentially breaking change related to the AttributeEncryptor
.
Changes
MetaStore.replicate
to make it easier to copy data-keys from one MetaStore to anotherAttributeEncryptor
will now throw a DynamoDBMappingException
if it is used with a SaveBehavior
other than PUT
or CLOBBER`. This is necessary to avoid risk of data-corruption. Please see inline documentation for explanation of cause.Published by lizroth about 6 years ago
It is important to use SaveBehavior.CLOBBER
with AttributeEncryptor
. If you do not do so you risk corrupting your signatures and encrypted data.
When CLOBBER is not specified, fields that are present in the record may not be passed down to the encryptor, which results in fields being left out of the record signature. This in turn can result in records failing to decrypt.
This version adds an ERROR
-level log message to warn users that are at risk. A future version bump will introduce an exception in this case.
See also issue #32
Published by lizroth about 6 years ago
Summary of changes since 1.11.0:
awslabs
to aws
Published by SalusaSecondus over 8 years ago
First official production release. Moves to SDK version 1.11.x and includes a fix related to mis-used of System.nanoTime() in MostRecentProvider.
Published by SalusaSecondus over 8 years ago
Published by SalusaSecondus over 8 years ago
Published by SalusaSecondus over 8 years ago
Improved synchronization logic.
Published by SalusaSecondus over 8 years ago
Added support for HandleUnknownAttributes and TableAadOverride
Published by SalusaSecondus almost 9 years ago
Fixed release version of 0.0.4-SNAPSHOT.
Adds support for new data types and ProviderStores.
Published by hansonchar almost 10 years ago
First pre-release of aws-dynamodb-encryption-java.
jar | SHA-1 |
---|---|
aws-dynamodb-encryption-java-0.0.3-SNAPSHOT-javadoc.jar | 2ee2f27c8a21f5183b37db2046f7937c4a347a35 |
aws-dynamodb-encryption-java-0.0.3-SNAPSHOT-sources.jar | 321a43015f1a734999599ff991afa7988cc1c7c1 |
aws-dynamodb-encryption-java-0.0.3-SNAPSHOT.jar | 5acc0c4030121f3e7f2d5353ccbfa34d621adeea |