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
e0f56103
Commit
e0f56103
authored
5 years ago
by
tanujdhir
Committed by
Copybara-Service
5 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Add beginner-friendly explanation of AEADs to PRIMITIVES docs.
PiperOrigin-RevId: 257589675
parent
d01290a5
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
docs/PRIMITIVES.md
+11
-6
11 additions, 6 deletions
docs/PRIMITIVES.md
with
11 additions
and
6 deletions
docs/PRIMITIVES.md
+
11
−
6
View file @
e0f56103
...
...
@@ -91,12 +91,17 @@ Hybrid Encryption | ECIES with AEAD and HKDF
AEAD primitive (Authenticated Encryption with Associated Data) provides
functionality of symmetric authenticated encryption. Implementations of this
primitive are secure against adaptive chosen ciphertext attacks. When
encrypting a plaintext one can optionally provide _associated data_ that should
be authenticated but not encrypted. That is, the encryption with associated data
ensures authenticity (ie. who the sender is) and integrity (ie. data has not
been tampered with) of that data, but not its secrecy
(see
[
RFC 5116
](
https://tools.ietf.org/html/rfc5116
)
).
primitive are secure against adaptive chosen ciphertext attacks.
When encrypting a plaintext one can optionally provide _associated data_ that
should be authenticated but not encrypted. That is, the encryption with
associated data ensures authenticity (ie. who the sender is) and integrity (ie.
data has not been tampered with) of that data, but not its secrecy (see
[
RFC 5116
](
https://tools.ietf.org/html/rfc5116
)
). This is often used for binding
encryptions to a context. For example, in a banking database the contents of a
row (e.g. bank account balance) can be encrypted using the customer's id as
_associated data_
. This would prevent swapping encrypted data between customers'
records.
Minimal properties:
...
...
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