diff options
author | Jason McIntyre <jmc@cvs.openbsd.org> | 2015-11-10 23:48:19 +0000 |
---|---|---|
committer | Jason McIntyre <jmc@cvs.openbsd.org> | 2015-11-10 23:48:19 +0000 |
commit | 4a35cd787d4211704bc33e641f746562a95af113 (patch) | |
tree | ce29960844dfe2d3545c23bd8dc426039505259c /lib/libc/hash | |
parent | e52a9092ce1104a642ff695bcda23f72e5066399 (diff) |
update NAME section to include all documented functions,
or otherwise change Dt to reflect the name of an existing function;
feedback/ok schwarze
Diffstat (limited to 'lib/libc/hash')
-rw-r--r-- | lib/libc/hash/md5.3 | 6 | ||||
-rw-r--r-- | lib/libc/hash/rmd160.3 | 6 | ||||
-rw-r--r-- | lib/libc/hash/sha1.3 | 6 | ||||
-rw-r--r-- | lib/libc/hash/sha2.3 | 37 |
4 files changed, 41 insertions, 14 deletions
diff --git a/lib/libc/hash/md5.3 b/lib/libc/hash/md5.3 index 5ec7c3ef800..547f5f76cb4 100644 --- a/lib/libc/hash/md5.3 +++ b/lib/libc/hash/md5.3 @@ -16,10 +16,10 @@ .\" If we meet some day, and you think this stuff is worth it, you .\" can buy me a beer in return. Poul-Henning Kamp .\" -.\" $OpenBSD: md5.3,v 1.4 2014/11/16 19:57:24 schwarze Exp $ +.\" $OpenBSD: md5.3,v 1.5 2015/11/10 23:48:18 jmc Exp $ .\" -.Dd $Mdocdate: November 16 2014 $ -.Dt MD5 3 +.Dd $Mdocdate: November 10 2015 $ +.Dt MD5INIT 3 .Os .Sh NAME .Nm MD5Init , diff --git a/lib/libc/hash/rmd160.3 b/lib/libc/hash/rmd160.3 index 4536e38b030..9678b02dc62 100644 --- a/lib/libc/hash/rmd160.3 +++ b/lib/libc/hash/rmd160.3 @@ -1,4 +1,4 @@ -.\" $OpenBSD: rmd160.3,v 1.34 2014/11/16 19:57:24 schwarze Exp $ +.\" $OpenBSD: rmd160.3,v 1.35 2015/11/10 23:48:18 jmc Exp $ .\" .\" Copyright (c) 1997, 2004 Todd C. Miller <Todd.Miller@courtesan.com> .\" @@ -17,8 +17,8 @@ .\" See http://www.esat.kuleuven.ac.be/~bosselae/ripemd160.html .\" for detailed information about RIPEMD-160. .\" -.Dd $Mdocdate: November 16 2014 $ -.Dt RMD160 3 +.Dd $Mdocdate: November 10 2015 $ +.Dt RMD160INIT 3 .Os .Sh NAME .Nm RMD160Init , diff --git a/lib/libc/hash/sha1.3 b/lib/libc/hash/sha1.3 index 885b2c99a3c..4479b0d45d4 100644 --- a/lib/libc/hash/sha1.3 +++ b/lib/libc/hash/sha1.3 @@ -1,4 +1,4 @@ -.\" $OpenBSD: sha1.3,v 1.41 2014/11/26 02:05:58 schwarze Exp $ +.\" $OpenBSD: sha1.3,v 1.42 2015/11/10 23:48:18 jmc Exp $ .\" .\" Copyright (c) 1997, 2004 Todd C. Miller <Todd.Miller@courtesan.com> .\" @@ -17,8 +17,8 @@ .\" See http://csrc.nist.gov/publications/fips/fips180-1/fip180-1.txt .\" for the detailed standard .\" -.Dd $Mdocdate: November 26 2014 $ -.Dt SHA1 3 +.Dd $Mdocdate: November 10 2015 $ +.Dt SHA1INIT 3 .Os .Sh NAME .Nm SHA1Init , diff --git a/lib/libc/hash/sha2.3 b/lib/libc/hash/sha2.3 index 46e6ce6bc62..1238306e041 100644 --- a/lib/libc/hash/sha2.3 +++ b/lib/libc/hash/sha2.3 @@ -1,4 +1,4 @@ -.\" $OpenBSD: sha2.3,v 1.22 2015/02/05 02:33:09 schwarze Exp $ +.\" $OpenBSD: sha2.3,v 1.23 2015/11/10 23:48:18 jmc Exp $ .\" .\" Copyright (c) 2003, 2004 Todd C. Miller <Todd.Miller@courtesan.com> .\" @@ -20,10 +20,19 @@ .\" .\" See http://www.nist.gov/sha/ for the detailed standard .\" -.Dd $Mdocdate: February 5 2015 $ -.Dt SHA2 3 +.Dd $Mdocdate: November 10 2015 $ +.Dt SHA256INIT 3 .Os .Sh NAME +.Nm SHA224Init , +.Nm SHA224Update , +.Nm SHA224Pad , +.Nm SHA224Final , +.Nm SHA224Transform , +.Nm SHA224End , +.Nm SHA224File , +.Nm SHA224FileChunk , +.Nm SHA224Data , .Nm SHA256Init , .Nm SHA256Update , .Nm SHA256Pad , @@ -32,7 +41,25 @@ .Nm SHA256End , .Nm SHA256File , .Nm SHA256FileChunk , -.Nm SHA256Data +.Nm SHA256Data , +.Nm SHA384Init , +.Nm SHA384Update , +.Nm SHA384Pad , +.Nm SHA384Final , +.Nm SHA384Transform , +.Nm SHA384End , +.Nm SHA384File , +.Nm SHA384FileChunk , +.Nm SHA384Data , +.Nm SHA512Init , +.Nm SHA512Update , +.Nm SHA512Pad , +.Nm SHA512Final , +.Nm SHA512Transform , +.Nm SHA512End , +.Nm SHA512File , +.Nm SHA512FileChunk , +.Nm SHA512Data .Nd calculate the NIST Secure Hash Standard (version 2) .Sh SYNOPSIS .In sys/types.h @@ -114,7 +141,7 @@ The SHA2 functions implement the NIST Secure Hash Standard, FIPS PUB 180-2. The SHA2 functions are used to generate a condensed representation of a message called a message digest, suitable for use as a digital signature. -There are three families of functions, with names corresponding to +There are four families of functions, with names corresponding to the number of bits in the resulting message digest. The SHA-224 and SHA-256 functions are limited to processing a message of less than 2^64 bits as input. |