Thanks for the explanation. I am having problem with "Encrypted Alert". At first I thought it's because the Session ID length 0 is not correct. If this is not the problem, I really can't tell where it went wrong from packets I captured. I searched the web and I think "Encrypted Alert" means that the alert is being encrypted. Is there any way I can decrypted the alert message? Can someone give me any hint? Attached is the .cap file. Thanks in advance. Here is what I have.
from Client : Client Hello from Server: Server Hello, Certificate, Server Hello Done from Client : Client Key Exchange, Change Cipher Spec, Encrypted Handshake Message from Server: Change Cipher Spec from Server: Encrypted Handshake Message from Server: Encrypted Alert On Tue, Mar 25, 2008 at 7:32 PM, jimmy bahuleyan <[EMAIL PROTECTED]> wrote: > hh wrote: > > Hi, > > > > I have ported openssl 0.9.8g to our platform in linux. > > When I tried to connect to a server with SSL enabled, it always give me > > "Handshake Failure". > > I checked the packet when "Client Hello" was sent. The session ID > > length is 0. > > I traced the source code in ssl3_get_client_method(), but I really don't > > know where went wrong. > > When is session id assigned? Can anyone help? Thanks in advance. > > > > HH > > > > > > > > Session ID is assigned by server, so client sends a 0 length id (unless > it is resuming a prior session). > > -jb > -- > I used to think I was indecisive, but now I'm not so sure. > ______________________________________________________________________ > OpenSSL Project http://www.openssl.org > User Support Mailing List openssl-users@openssl.org > Automated List Manager [EMAIL PROTECTED] >
encryptedAlert.cap
Description: Binary data
