On Sun, Dec 16, 2001 at 01:57:44PM +1030, Daniel O'Connor wrote:
On 15-Dec-2001 Kris Kennaway wrote:
Or just ln -sf /usr/bin/openssl /usr/bin/sha1
OpenSSL already checks the name it's invoked under and behaves
accordingly.
Does it grok the options for md5? :)
-s would be easy
We currently have a MD5 driver, but no SHA1 driver, even though
we have SHA1 as part of libmd. So I took md5.c from /usr/src/sbin/md5
and made sha1.c as well as a respective man page. Attached is the
source file, the manual page for it, as well as a makefile.
Hope this is useful and makes its
On Saturday 15 December 2001 11:34 am, Mike Wiacek wrote:
We currently have a MD5 driver, but no SHA1 driver, even though
we have SHA1 as part of libmd. So I took md5.c from
/usr/src/sbin/md5 and made sha1.c as well as a respective man page.
Attached is the source file, the manual page for
On 15-Dec-2001 Dominic Marks wrote:
Why not have one program for all the supported hash algorithms as
opposed to individual ones for each (md5, sha1) ?
You could use something like:
hash -a md5 /some/file
hash -a sha1 /some/other/file
Conceivably a fairly simple script or two
On Sat, Dec 15, 2001 at 11:58:14AM +, Dominic Marks wrote:
On Saturday 15 December 2001 11:34 am, Mike Wiacek wrote:
We currently have a MD5 driver, but no SHA1 driver, even though
we have SHA1 as part of libmd. So I took md5.c from
/usr/src/sbin/md5 and made sha1.c as well as a
On Sat, Dec 15, 2001 at 06:12:53PM +0100, Alson van der Meulen wrote:
Why not have one program for all the supported hash algorithms as
opposed to individual ones for each (md5, sha1) ?
You could use something like:
hash -a md5 /some/file
hash -a sha1 /some/other/file
It's
On 15-Dec-2001 Kris Kennaway wrote:
Or just ln -sf /usr/bin/openssl /usr/bin/sha1
OpenSSL already checks the name it's invoked under and behaves
accordingly.
Does it grok the options for md5? :)
-s would be easy to simulate in a shell script.
-p would be much more difficult unless
7 matches
Mail list logo
