cpabe: Serializing ciphertext with 32-bit prefixes. #490
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Serializing ciphertext with 32-bit prefixes.
Previously, tkn20 ciphertext was encoding the ciphertext header
C1
, the envelopeenv
(containing inner ciphertext), andmacData
using 16-bit prefixes, which caused a limitation on the maximum size allowed for encrypting plaintexts.With this change, the encoding now uses 32-bit prefixes for these three elements allowing to encrypt plaintexts longer than 2^16 bytes. So, ciphertexts produced by tkn20 package are now 12 bytes longer.
Changes are backwards compatible, meaning that ciphertexts in the previous format are still decryptable. The following functions are backwards-compatible:
- AttributeKey.Decrypt
- Attributes.CouldDecrypt
- Policy.ExtractFromCiphertext
Note: Since the format of ciphertexts is changed, we need to release a version, once this gets merged.
Fixes #484