Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
N
nettle
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Labels
Merge Requests
5
Merge Requests
5
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Commits
Open sidebar
Nettle
nettle
Commits
9b29534a
Commit
9b29534a
authored
Apr 22, 2014
by
Niels Möller
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fix typos in umac documentation.
parent
cf570173
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
5 deletions
+5
-5
nettle.texinfo
nettle.texinfo
+5
-5
No files found.
nettle.texinfo
View file @
9b29534a
...
...
@@ -2433,17 +2433,17 @@ secret.
The nonce must be at least one octet, and at most 16; nonces shorter
than 16 octets are zero-padded. Nettle's implementation of
@acronym
{
UMAC
}
increments the nonce
for automatically
each message, so
@acronym
{
UMAC
}
increments the nonce
automatically for
each message, so
explicitly setting the nonce for each message is optional. This
auto-increment uses network byte order and it takes the length of the
nonce into acount. E.g., if the initial nonce is ``abc'' (3 octets),
nonce into ac
c
ount. E.g., if the initial nonce is ``abc'' (3 octets),
this value is zero-padded to 16 octets for the first message. For the
next message, the nonce is incremented to ``abd'', and this incremented
value is zero-padded to 16 octets.
@acronym
{
UMAC
}
is defined in four variants, for different output sizes:
32 bits (4 octe
st
), 64 bits (8 octets), 96 bits (12 octets) and 128 bits
(16 octets), corresponding to different tradeoffs between speed and
32 bits (4 octe
ts
), 64 bits (8 octets), 96 bits (12 octets) and 128 bits
(16 octets), corresponding to different trade
-
offs between speed and
security. Using a shorter output size sometimes (but not always!) gives
the same result as using a longer output size and truncating the result.
So it is important to use the right variant. For consistency with other
...
...
@@ -2482,7 +2482,7 @@ The size of an UMAC96 digest, 12.
@defvr Constant UMAC128
_
DIGEST
_
SIZE
The size of an UMAC128 digest, 16.
@end defvr
@defvr Constant UMAC
128
_
DATA
_
SIZE
@defvr Constant UMAC
_
DATA
_
SIZE
The internal block size of UMAC.
@end defvr
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment