]> git.codecow.com Git - Monocypher.git/commit
projects / Monocypher.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: e13215c) | patch
Better wording for Poly1305 security considerations
authorLoup Vaillant <loup@loup-vaillant.fr>
Wed, 7 Feb 2018 22:55:51 +0000 (23:55 +0100)
committerLoup Vaillant <loup@loup-vaillant.fr>
Wed, 7 Feb 2018 22:55:51 +0000 (23:55 +0100)
commit643e2cfaf70aa526032b664cd34572d7af393fcb
tree07d7a19cdd30ea38a3c268c9bbd653e7a6996cbbtree | snapshot
parente13215c8d16e094eaed131f80c529edef4d4ae10commit | diff
Better wording for Poly1305 security considerations

Fixes #84.  I hope.

Some users *will* use Poly1305 for who knows what nefarious purpose I
haven't anticipated.  This is why we expose low-level primitives in the
first place.

This may sound bikeshed-y, but Poly1305 is quite exacting.  Not as bad
as AES-GCM from what I've heard, but close.  So the manual must be
precise and unambiguous.
doc/man/man3/crypto_poly1305.3monocypher diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.