make caveat consistent with description in md5.1

2015-09-19 Thread Rob Pierce
Mention that collisions are theorizied for SHA-1 in the caveat.

Regards,

Index: md5.1
===
RCS file: /cvs/src/bin/md5/md5.1,v
retrieving revision 1.44
diff -u -p -r1.44 md5.1
--- md5.1   4 Dec 2014 20:10:16 -   1.44
+++ md5.1   20 Sep 2015 02:43:55 -
@@ -144,7 +144,7 @@ and \*(Gt0 if an error occurs.
 .%O FIPS PUB 180-2
 .Re
 .Sh CAVEATS
-Since collisions have been found for MD5,
+Since collisions have been found for MD5, and are theorized for SHA-1,
 the use of
 .Nm sha256
 is recommended instead.



Re: make caveat consistent with description in md5.1

2015-09-23 Thread Jason McIntyre
On Sat, Sep 19, 2015 at 10:46:23PM -0400, Rob Pierce wrote:
> Mention that collisions are theorizied for SHA-1 in the caveat.
> 
> Regards,
> 
> Index: md5.1
> ===
> RCS file: /cvs/src/bin/md5/md5.1,v
> retrieving revision 1.44
> diff -u -p -r1.44 md5.1
> --- md5.1 4 Dec 2014 20:10:16 -   1.44
> +++ md5.1 20 Sep 2015 02:43:55 -
> @@ -144,7 +144,7 @@ and \*(Gt0 if an error occurs.
>  .%O FIPS PUB 180-2
>  .Re
>  .Sh CAVEATS
> -Since collisions have been found for MD5,
> +Since collisions have been found for MD5, and are theorized for SHA-1,
>  the use of
>  .Nm sha256
>  is recommended instead.
> 

all the info in CAVEATS, plus the addition you proposed, is already at
page top. so i just zapped CAVEATS.

jmc