Richard,
> Check (with 'od -c', for example) if there's a \n at the end of that
> file. In that case, you have digested "abcdefghijklmnopqrstuvwxyz\n"
> rather than "abcdefghijklmnopqrstuvwxyz". This is quite a common
> mistake.
Thanx, that was the problem. It dit show the \n as you mentioned.
From: "Zwet van der, PH (Pim)" <[EMAIL PROTECTED]>
P.H.Zwet> I'm using the datastring "abcdefghijklmnopqrstuvwxyz" in a
P.H.Zwet> file called data1 as input for the folowing command:
P.H.Zwet>
P.H.Zwet> > cat data1 | openssl sha1 -sha1
P.H.Zwet>
P.H.Zwet> This results in the folowing output:
P.
Hi,
I noticed a difference in output when using the commandline SHA1 function
and the one from the API (using a c program).
I'm using the datastring "abcdefghijklmnopqrstuvwxyz" in a file called data1
as input for the folowing command:
> cat data1 | openssl sha1 -sha1
This results in the folow
