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 a \0 to prevent C-string buffer-read overruns?
-Kyle H On Sat, Sep 25, 2010 at 6:17 AM, Kedar Sabnis <kedar.sab...@tcs.com> 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 anticipation. > > Thanks & Regards, > Kedar Anilrao Sabnis > Tata Consultancy Services > SDF-V GROUND Unit No.130/131,SDF-V > Seepz,Andheri(East) > Mumbai - 400096,Maharshtra > India > Mailto: kedar.sab...@tcs.com > Website: http://www.tcs.com > ____________________________________________ > Experience certainty. IT Services > Business Solutions > Outsourcing > ____________________________________________ > > =====-----=====-----===== > Notice: The information contained in this e-mail > message and/or attachments to it may contain > confidential or privileged information. If you are > not the intended recipient, any dissemination, use, > review, distribution, printing or copying of the > information contained in this e-mail message > and/or attachments to it are strictly prohibited. If > you have received this communication in error, > please notify us by reply e-mail or telephone and > immediately and permanently delete the message > and any attachments. Thank you > > > ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
