Hi Friends,

 

I am facing a trivial problem with OpenSSL implementation on Windows
platform.

To avoid the compilation of source code, I am using the OpenSSL installation
for Windows platform, available from shininglightpro.com
(http://www.shininglightpro.com/download/Win32OpenSSL-0_9_8g.exe)(Win32
OpenSSL v0.9.8g).

I have created a sample server application which initializes the OpenSSL
library using API SSL_library_init().

Also I am using the following APIs to load the error string
(SSL_load_error_strings, ERR_load_BIO_strings, ERR_load_SSL_strings &
OpenSSL_add_all_algorithms).

Once this is done, I am opening the certificate file and private key file
using APIs SSL_CTX_use_certificate_file & SSL_CTX_use_PrivateKey_file. .The
certificate file and private key file PEM (base 64 encoded).

In addition to this, I have added the following .lib files in the project
setting of VC++ 6.0 (libeay32MD.lib libeay32MDd.lib libeay32MT.lib
libeay32MTd.lib ssleay32MD.lib ssleay32MDd.lib ssleay32MT.lib
ssleay32MTd.lib)

This is working absolutely fine with the sample server application.

The same code does not work i.e. opening the certificate files, when I try
to execute from a Windows NT Service (Ours is an application running as a
service and that service in turn acts as a TCP server which will open SSL
ports for communication with client)

The same set of APIs and certificates does not work
(SSL_CTX_use_certificate_file & SSL_CTX_use_PrivateKey_file) from within a
Windows NT service application).

 

Also, when I try to get the latest SSL error numbers using API
ERR_print_errors_fp, the entire application crashes.

 

I am looking out for any architectural issues with OpenSSL when working with
Windows NT service applications. If anyone has tried implementing OpenSSL in
a Windows NT service, any help in this regard is highly appreciated.

 

Thanks,

Parag

 


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