Fix ciphertext segment size validation.
We changed the segment size validation in all Tink streaming keys such that the first block always needs to have room for at least 1 byte of ciphertext. Previously it was not consistent. The decision whether to allow empty ciphertexts in the first segment is somewhat arbitrary, but it should be consistent everywhere. PiperOrigin-RevId: 262315914
Showing
- cc/streamingaead/BUILD.bazel 1 addition, 0 deletionscc/streamingaead/BUILD.bazel
- cc/streamingaead/CMakeLists.txt 1 addition, 0 deletionscc/streamingaead/CMakeLists.txt
- cc/streamingaead/aes_gcm_hkdf_streaming_key_manager.cc 6 additions, 2 deletionscc/streamingaead/aes_gcm_hkdf_streaming_key_manager.cc
- cc/subtle/aes_ctr_hmac_stream_segment_encrypter.cc 1 addition, 1 deletioncc/subtle/aes_ctr_hmac_stream_segment_encrypter.cc
- cc/subtle/aes_ctr_hmac_stream_segment_encrypter_test.cc 1 addition, 1 deletioncc/subtle/aes_ctr_hmac_stream_segment_encrypter_test.cc
- cc/subtle/aes_gcm_hkdf_stream_segment_decrypter.cc 1 addition, 1 deletioncc/subtle/aes_gcm_hkdf_stream_segment_decrypter.cc
- cc/subtle/aes_gcm_hkdf_stream_segment_decrypter_test.cc 3 additions, 1 deletioncc/subtle/aes_gcm_hkdf_stream_segment_decrypter_test.cc
- cc/subtle/aes_gcm_hkdf_stream_segment_encrypter.cc 1 addition, 1 deletioncc/subtle/aes_gcm_hkdf_stream_segment_encrypter.cc
- cc/subtle/aes_gcm_hkdf_stream_segment_encrypter_test.cc 2 additions, 1 deletioncc/subtle/aes_gcm_hkdf_stream_segment_encrypter_test.cc
- cc/subtle/aes_gcm_hkdf_streaming.cc 3 additions, 2 deletionscc/subtle/aes_gcm_hkdf_streaming.cc
- java/src/main/java/com/google/crypto/tink/streamingaead/AesCtrHmacStreamingKeyManager.java 6 additions, 2 deletions...pto/tink/streamingaead/AesCtrHmacStreamingKeyManager.java
- java/src/main/java/com/google/crypto/tink/streamingaead/AesGcmHkdfStreamingKeyManager.java 7 additions, 2 deletions...pto/tink/streamingaead/AesGcmHkdfStreamingKeyManager.java
Loading
Please register or sign in to comment