Skip to content

Commit aacd32c

Browse files
committed
editing README
1 parent 5aa6c53 commit aacd32c

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
@@ -110,10 +110,10 @@ For signing, the user specified signing key can be either symmetric or asymmetri
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.
111111

112112
3. How many bits are used for the random IV ?
113-
* The size used for the random IV is the as the block size of the block cipher used for content encryption, which therefore depends on the specific algorithm of the secret key provided by the user (via EncryptionMaterialsProvider). Typically this means AES and which therefore 128 bits.
113+
* The bit size used for the random IV is the as the block size of the block cipher used for content encryption, which therefore depends on the specific algorithm of the content encrypting key provided by the user. Typically this means AES, or 128 bits.
114114

115-
4. How is the key length for the content encrypting key ?
116-
* This depends on the specific secret key provided by the user (via EncryptionMaterialsProvider). The typical key length of AES key is 128 bits or 256 bits.
115+
4. What is the key length for the content encrypting key ?
116+
* This depends on the specific content encrypting key provided by the user. A typical key length of AES key is 128 bits or 256 bits.
117117

118118
## Known Limitations
119119

0 commit comments

Comments
 (0)