Skip to content
GitLab
Explore
Sign in
Register
Primary navigation
Search or go to…
Project
F
fuchsia.googlesource.com-third_party-tink
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Model registry
Analyze
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
fuchsia-mirror
fuchsia.googlesource.com-third_party-tink
Commits
aa40ff24
Commit
aa40ff24
authored
5 years ago
by
przydatek
Committed by
Copybara-Service
5 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Documenting that size() of a decrypting stream (in C++) is not guaranteed to be correct.
PiperOrigin-RevId: 264564958
parent
4c865a5d
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
cc/streaming_aead.h
+4
-0
4 additions, 0 deletions
cc/streaming_aead.h
with
4 additions
and
0 deletions
cc/streaming_aead.h
+
4
−
0
View file @
aa40ff24
...
...
@@ -66,6 +66,10 @@ class StreamingAead {
// via the wrapper leads to AEAD-decryption of the underlying ciphertext,
// using 'associated_data' as associated authenticated data, and the
// read bytes are bytes of the resulting plaintext.
// Note that the returned wrapper's size()-method reports size that is
// not checked for integrity. For example, if the ciphertext file has been
// truncated then size() will return a wrong result. Reading the last block
// of the plaintext will verify whether size() is correct.
// Reading through the wrapper is thread safe.
virtual
crypto
::
tink
::
util
::
StatusOr
<
std
::
unique_ptr
<
crypto
::
tink
::
RandomAccessStream
>>
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment