Hello All,
 
In continuation with the error we have motioned before we have the below query:-
 
If an SSL record has no padding bytes then how does openSSL handle it?
 
Does openSSL consider it as bad padding?
 
In case openSSL handles this kindly mention us in which files of the code we 
can find it?
 
Thanks & Regards,
Lavanya Golla.
 
________________________________

From: [EMAIL PROTECTED] on behalf of Marek Marcola
Sent: Tue 5/29/2007 6:39 PM
To: openssl-users@openssl.org
Subject: Re: Urgent Help in regarding openssl library



Hello,
> We are mailing regrding an error we are getting while implementing
> openssl libraries for our application.
> 
> The error we get is as below:-
> SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac.
> 
> We are using open ssl 0.9.7g. Kinldy can you give us some help or at
> least suggest to us which version of open ssl resolves this problem.
When this happens:
 - connection negotiation (more information required like ssldump info)
 - random in data transfer (SSL_CTX_set_options() with SSL_OP_ALL may
help).

Best regards,
--
Marek Marcola <[EMAIL PROTECTED]>

______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org 
<http://www.openssl.org/> 
User Support Mailing List                    openssl-users@openssl.org
Automated List Manager                           [EMAIL PROTECTED]





The information contained in this electronic message and any attachments to 
this message are intended for the exclusive use of the addressee(s) and may 
contain proprietary, confidential or privileged information. If you are not the 
intended recipient, you should not disseminate, distribute or copy this e-mail. 
Please notify the sender immediately and destroy all copies of this message and 
any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should 
check this email and any attachments for the presence of viruses. The company 
accepts no liability for any damage caused by any virus transmitted by this 
email.
 
www.wipro.com

Reply via email to