Kedar Sabnis wrote:
in some specific case SHA1 digest is coming as 152 bits long instead of
160 bits long.
All possible 160 bits values have the same chance of being the output of
a SHA1 digest, *including* those that comprise long strings of all zeros
or all ones.
This mean that, statistic
On Sat, Sep 25, 2010 at 21:09, Kedar Sabnis wrote:
>
> HI,
>
> I am an openSSL User. We implemented SHA1 algorithm.
>
> Here in some specific case SHA1 digest is coming as 152 bits long instead
> of 160 bits long.
>
> Please suggest if any bug fix is there for this issue.
>
> Thanking you in anti
HI,
I am an openSSL User. We implemented SHA1 algorithm.
Here in some specific case SHA1 digest is coming as 152 bits long instead
of 160 bits long.
Please suggest if any bug fix is there for this issue.
Thanking you in anticipation.
Thanks & Regards,
Kedar Anilrao Sabnis
Tata Consultancy Ser
Would you perhaps like to explain how you implemented it (i.e., did
you include OpenSSL in your own application, or are you trying to use
it via a script?)? 152 bits is 8 bits -- one byte -- less than 160
bits. Are you using a library or framework that overwrites the last
byte of the buffer with
HI,
I am an openSSL User. We implemented SHA1 algorithm.
Here in some specific case SHA1 digest is coming as 152 bits long instead
of 160 bits long.
Please suggest if any bug fix is there for this issue.
Thanking you in anticipation.
Thanks & Regards,
Kedar Anilrao Sabnis
Tata Consultancy Ser
HI,
I am an openSSL User. We implemented SHA1 algorithm.
Here in some specific case SHA1 digest is coming as 152 bits long instead
of 160 bits long.
Please suggest if any bug fix is there for this issue.
Thanking you in anticipation.
Thanks & Regards,
Kedar Anilrao Sabnis
Tata Consultancy Ser
