More RFC number corrections

RFC 7539 has been obsoleted by RFC 8439.
Incremental EdDSA didn't change to RFC 8032.

diff --git a/doc/man/man3/crypto_chacha20_encrypt.3monocypher b/doc/man/man3/crypto_chacha20_encrypt.3monocypher
index e75d024b8926bb916254795dd90f38376f1a6ac0..18db6625d01f7e9f946d29a9967e041c014469dc 100644 (file)
--- a/doc/man/man3/crypto_chacha20_encrypt.3monocypher
+++ b/doc/man/man3/crypto_chacha20_encrypt.3monocypher
@@ -176,7 +176,7 @@ Resuming the encryption will use the stream at the block
 .Ql ctr \(mu 64 ) .
 This can be used to encrypt (or decrypt) part of a long message, or to
 implement some AEAD constructions such as the one described in RFC
-7539.
+8439.
 Be careful when using this not to accidentally reuse parts of the
 random stream as that would destroy confidentiality.
 .Sh RETURN VALUES
@@ -278,7 +278,7 @@ crypto_wipe(plain_text, 500);
 .Xr intro 3monocypher
 .Sh STANDARDS
 These functions implement Chacha20 and XChacha20.
-Chacha20 is described in RFC 7539.
+Chacha20 is described in RFC 8439.
 XChacha20 derives from Chacha20 the same way XSalsa20 derives from
 Salsa20, and benefits from the same security reduction (proven secure
 as long as Chacha20 itself is secure).

diff --git a/doc/man/man3/crypto_lock.3monocypher b/doc/man/man3/crypto_lock.3monocypher
index 559fd5680b551aa58f93b89b8733bf094751c108..858218e768a3a5fa8473d994372d7971306041ca 100644 (file)
--- a/doc/man/man3/crypto_lock.3monocypher
+++ b/doc/man/man3/crypto_lock.3monocypher
@@ -245,7 +245,7 @@ crypto_wipe(key, 32);
 .Xr crypto_wipe 3monocypher ,
 .Xr intro 3monocypher
 .Sh STANDARDS
-These functions implement RFC 7539, with XChacha20 instead of Chacha20.
+These functions implement RFC 8439, with XChacha20 instead of Chacha20.
 XChacha20 derives from Chacha20 the same way XSalsa20 derives from
 Salsa20, and benefits from the same security reduction (proven secure
 as long as Chacha20 itself is secure).

diff --git a/doc/man/man3/crypto_lock_init.3monocypher b/doc/man/man3/crypto_lock_init.3monocypher
index 8f0aa4c90fbb962dd46401bf94698d727f193550..d8c6802031dc690c5239673e287373f3fba2c8fd 100644 (file)
--- a/doc/man/man3/crypto_lock_init.3monocypher
+++ b/doc/man/man3/crypto_lock_init.3monocypher
@@ -269,7 +269,7 @@ crypto_lock_final(&ctx, mac);
 .Xr crypto_wipe 3monocypher ,
 .Xr intro 3monocypher
 .Sh STANDARDS
-These functions implement RFC 7539, with XChacha20 instead of Chacha20.
+These functions implement RFC 8439, with XChacha20 instead of Chacha20.
 XChacha20 derives from Chacha20 the same way XSalsa20 derives from
 Salsa20, and benefits from the same security reduction (proven secure
 as long as Chacha20 itself is secure).

diff --git a/doc/man/man3/crypto_poly1305.3monocypher b/doc/man/man3/crypto_poly1305.3monocypher
index 8e85e5b0914f8d29c9bb1af2dfbbd5969b41f92a..bf8dd761d1068c0f34362e7eaed805bc5dc231be 100644 (file)
--- a/doc/man/man3/crypto_poly1305.3monocypher
+++ b/doc/man/man3/crypto_poly1305.3monocypher
@@ -134,7 +134,7 @@ crypto_poly1305_final(&ctx, mac);
 .Xr crypto_verify16 3monocypher ,
 .Xr intro 3monocypher
 .Sh STANDARDS
-These functions implement Poly1305, described in RFC 7539.
+These functions implement Poly1305, described in RFC 8439.
 .Sh SECURITY CONSIDERATIONS
 Poly1305 is difficult to use correctly.
 Do not use it unless you are absolutely sure what you are doing.

diff --git a/doc/man/man3/crypto_sign_init_first_pass.3monocypher b/doc/man/man3/crypto_sign_init_first_pass.3monocypher
index 6a8a7b1153fa2a8b3870958f748db6197678bc40..59bc2b88792a72c2d96711790cb7e290efca5a84 100644 (file)
--- a/doc/man/man3/crypto_sign_init_first_pass.3monocypher
+++ b/doc/man/man3/crypto_sign_init_first_pass.3monocypher
@@ -161,9 +161,9 @@ if (crypto_check_final(&ctx)) {
 .Xr crypto_wipe 3monocypher ,
 .Xr intro 3monocypher
 .Sh STANDARDS
-These functions implement EdDSA with Curve25519 and Blake2b.
+These functions implement PureEdDSA with Curve25519 and Blake2b, as
+described in RFC 8032.
 This is the same as Ed25519, with Blake2b instead of SHA-512.
-Ed25519 is described in RFC 7748.
 .Sh SECURITY CONSIDERATIONS
 Messages are not verified until the call to
 .Fn crypto_check_final .