Socket left in CLOSE_WAIT state...

2010-04-21 Thread Matthew Allen
Hi, My code leaves sockets in the CLOSE_WAIT state after I free the SSL connection (running on windows XP with OpenSSL 0.9.8e). After I'm done with the connection I call SSL_shutdown and SSL_free, but that doesn't close the socket on the client side. My code's probably wrong, so tell me what

RE: Socket left in CLOSE_WAIT state...

2010-04-21 Thread Saju Paul
Looks like it needs a BIO_free_all(bio) or something similair. -Original Message- From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]on Behalf Of Matthew Allen Sent: Wednesday, April 21, 2010 5:18 AM To: openssl-users@openssl.org Subject: Socket left in

Re: Socket left in CLOSE_WAIT state...

2010-04-21 Thread Darryl Miles
Matthew Allen wrote: if (Ssl) { SSL_shutdown(Ssl); SSL_free(Ssl); } Yes as the other writer says, you may need to close out the BIO (which is the thing holding the socket descriptor/handle). So the Bio object you created you may need to clean

How to handle Engine Cleanup

2010-04-21 Thread Becky H
Hello - I am using M2Crypto which wraps OpenSSL, but have translated my M2Crypto commands into OpenSSL methods. I do a set of commands to get the certificate and key off the USB eToken. I am unsure how to clean up my engines. Do I need to do all three of the followings commands:

how to interpret the speed result using openssl command line

2010-04-21 Thread 芦翔
Dear all, I input the command speed rc4 under the prompt openssl. The result is as follows:Doing rc4 for 3s on 16 size blocks: 778800 rc4's in 1.53sDoing rc4 for 3s on 64 size blocks: 219433 rc4's in 1.55sDoing rc4 for 3s on 256 size blocks: 52962 rc4's in 1.45sDoing rc4 for 3s on 1024 size

FW: Help! Encryption Absorted

2010-04-21 Thread 芦翔
From: luxiang...@hotmail.com To: openssl-users@openssl.org Subject: Help! Encryption Absorted Date: Wed, 21 Apr 2010 17:52:04 + Dear all, I would like to encrypt my data before they are emitted. I use the following function:EVP_CIPHER_CTX_ex(ctx, EVP_des_ede_cbc(), NULL, key,

Re: Socket left in CLOSE_WAIT state...

2010-04-21 Thread Stuart Weatherby
Shutdown disables the ability to read, write (or both) on a socket. However, shutdown() does not close the socket. to release the socket descriptor back to the OS you also need to call closesocket(); - Original Message From: Matthew Allen l...@sydneyband.com.au To:

Verifying the certificate in PEM format

2010-04-21 Thread Krishna Swarup
Dear Users, My application generated security certificates, which will be in the PEM format. Can anyone help me on using the OpenSSL tool to verify the PEM certificate format? Appreciate Your help, Thank you, Krishna

Help! Encryption Absorted

2010-04-21 Thread 芦翔
Dear all, I would like to encrypt my data before they are emitted. I use the following function:EVP_CIPHER_CTX_ex(ctx, EVP_des_ede_cbc(), NULL, key, iv).Unfortunately, when come to this function, my program jumped into the end omitting all the following encryption operations. The whole program

Re: Socket left in CLOSE_WAIT state...

2010-04-21 Thread Matthew Allen
-- Original Message -- To: (openssl-users@openssl.org) From: Stuart Weatherby (stuart_weathe...@yahoo.ca) Subject: Re: Socket left in CLOSE_WAIT state... Date: 22/4/2010 5:18:48a Shutdown disables the ability to read, write (or both) on a socket. However, shutdown() does not

OpenSSL and Python

2010-04-21 Thread gary clark
Hello, I am porting my code to a new server. I have installed Python 2.5.2 working on a linux box. The problem is I need to know what version of pyOpenSSL and OpenSSL libs are compatible with this version of linux. I'm seeing the below: python Python 2.5.2 (r252:60911, Sep 30 2008, 15:41:38)

Re: OpenSSL and Python

2010-04-21 Thread Antoine Pitrou
Le mercredi 21 avril 2010 à 16:06 -0700, gary clark a écrit : ImportError: /usr/local/lib/python2.5/site-packages/OpenSSL/crypto.so: undefined symbol: PyUnicodeUCS2_Decode This is a Python problem, not an unicode one. I suggest posting on comp.lang.python. Basically, you should use the

Re: OpenSSL and Python

2010-04-21 Thread gary clark
Appreciated. Garyc --- On Wed, 4/21/10, Antoine Pitrou solip...@pitrou.net wrote: From: Antoine Pitrou solip...@pitrou.net Subject: Re: OpenSSL and Python To: openssl-users@openssl.org Date: Wednesday, April 21, 2010, 6:39 PM Le mercredi 21 avril 2010 à 16:06 -0700, gary clark a écrit :

Re: Socket left in CLOSE_WAIT state...

2010-04-21 Thread Stuart Weatherby
According to the doc:  0 indicates the ssl_shutdown function needs to be called again.  1 indicates success -1 indicates failure if  r = ssl_shutdown() == -1   // failure if r == 0   r = ssl_shutdown if r == 1  // failure else //success Stuart - Original Message From: Matthew Allen

RE: Socket left in CLOSE_WAIT state...

2010-04-21 Thread Saju Paul
Since BIO is creating the SSL object somewhere in the call to BIO_new_ssl_connect(Ctx); the cleanup of the SSL object (SSL_shutdown SSL_free) maybe handled by BIO_free_all() begin else printf(BIO_new_ssl_connect failed.\n); BIO_free_all(Bio); /* if (Ssl) {

Re: Win32 OPENSSL_USE_APPLINK usage

2010-04-21 Thread Modem Man
Andy Polyakov schrieb: I actually ended up solving it by removing all uses of BIO_new_fp() in favor of my own custom BIO that I just finished writing earlier this week. Why not BIO_new_file? Yeah, I discovered while analyzing the code that using BIO_new_file() rather than BIO_new_fp()