Hi,
This sounds like a bug to me. Noticed it last year and I've just
checked that it's still not resolved in the latest snapshot.
jill!solar:~/build/openssl-SNAP-20020416$ apps/openssl dgst -md5 /bin/ls
MD5(/bin/ls)= d93498d9f52c3dc0330ab930fe3ffc50
OK.
jill!solar:~/build/openssl-SNAP-20020416$ apps/openssl dgst -md5 /bin
MD5(/bin)= d41d8cd98f00b204e9800998ecf8427e
jill!solar:~/build/openssl-SNAP-20020416$ apps/openssl dgst -md5 /dev/log
MD5(/dev/log)= d41d8cd98f00b204e9800998ecf8427e
Wrong. I'd want it to fail with a message to stderr and a non-zero
exit code. Also on any read error, not just on non-regular files.
open("/bin", O_RDONLY) = 4
[some getpid()'s]
read(4, 0x8189fb0, 8192) = -1 EISDIR (Is a directory)
[lots of getpid()'s, why?!]
write(1, "MD5(/bin)= d41d8cd98f00b204e9800"..., 44) = 44
--
/sd
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
