Sun, Jun 24, 2001 at 09:25:22, stephen (Stephen Montgomery-Smith) wrote about 
"Problems with md5 -p": 

I reproduce it stably on my -current. The second checksum is constant
and it is MD5 checksum of an empty stream:

root@iv:/usr/HEAD/src/sbin/md5##md5 </dev/null

A fix:

--- md5.c.orig  Mon Jun  4 00:38:02 2001
+++ md5.c       Sun Jun 24 19:37:13 2001
@@ -65,7 +65,7 @@
                switch (ch) {
                case 'p':
-                       break;
+                       exit(0);
                case 'q':
                        qflag = 1;

This avoids determination of other options, but this does not conflict
directly with man page.

Moreover such exit(0) should be applied not only with -p, but also with
-x, -t and -s: all these options should not gather any input files.
Patch is trivial.

> Suppose I have a file xxx.  If I type 
> md5 -p < xxx
> it should return the contents of the file followed by its md5 number:
> Some junk in the file
> 334911f8bcde69fe8edac561197e876f
> But now I get two numbers:
> Some junk in the file
> 334911f8bcde69fe8edac561197e876f
> d41d8cd98f00b204e9800998ecf8427e
> This is using FreeBSD stable of June 16.  (Maybe this has been fixed

> more recently - please tell me of it has.  It is a bit tricky for me to
> update sources because I use CTM which has been out recently - probably
> for just this very reason.  But if I know the problem has been fixed
> then I will go through the effort of using cvsup.)


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to