Skip to content

Commit 10849c1

Browse files
committed
editing README
1 parent d8da55c commit 10849c1

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ To enable transparent encryption and signing, simply specify the necessary encry
9393

9494
Note that by default all attributes except the primary keys are both encrypted and signed for maximum security. To selectively disable encryption, the annotation [@DoNotEncrypt][donotencrypt] can be used as shown in the [Book](#getting-started) class above. To disable both encryption and signing, the annotation [@DoNotTouch][donottouch] can be used.
9595

96-
There is a variety of existing [EncryptionMaterialsProvider][materialprovider] implemenations that you can use to provide the encryption material, including [KeyStoreMaterialsProvider][keystoreprovider] which makes use of a Java keystore. Alternatively, you can also plug in your own custom implementation.
96+
There is a variety of existing [EncryptionMaterialsProvider][materialprovider] implementations that you can use to provide the encryption material, including [KeyStoreMaterialsProvider][keystoreprovider] which makes use of a Java keystore. Alternatively, you can also plug in your own custom implementation.
9797

9898
## Supported Algorithms
9999

@@ -103,8 +103,8 @@ For signing, the user specified signing key can be either symmetric or asymmetri
103103

104104
## FAQ
105105

106-
1. Do the content-encrypting key and signing key get encryted and stored along side with the data in Amazon DynamoDB ?
107-
* No, neither the content-encrypting key nor the signing key get persisted by this library. However, in order to locate the material for decryption purposes, the identifying information (ie material descriptions) for the encryption material is indeed stored along side with the data in Amazon DynamoDB. In particular, the user specified [EncryptionMaterialsProvider][materialprovider] is responsible for not only providing the keys, but also the corresponding material descriptions.
106+
1. Do the content-encrypting key and signing key get encrypted and stored along side with the data in Amazon DynamoDB ?
107+
* No, neither the content-encrypting key nor the signing key get persisted by this library. However, in order to locate the material for decryption purposes, the identifying information (i.e. material descriptions) for the encryption material is indeed stored along side with the data in Amazon DynamoDB. In particular, the user specified [EncryptionMaterialsProvider][materialprovider] is responsible for not only providing the keys, but also the corresponding material descriptions.
108108

109109
2. How is the IV generated and where is it stored ?
110110
* For each attribute that needs to be encrypted, a unique IV is randomly generated, and get stored along side with the binary representation of the attribute value.

0 commit comments

Comments
 (0)