RE: Checking for socket read state

2005-05-31 Thread David Schwartz
Hi all quick question of you guru's. If I wish to check to see if data is ready to be read on my SSL connection do I just use normal select or is there something in the SSL libraries that I need to use? You aren't asking a precise question. For example, if there's data that could be

Getting 'no shared ciphers' while connecting to the server

2005-05-31 Thread Alaka Pathy
Hi All, I'm using Apache 1.3.31 with mod_ssl 2.8.17 and OpenSSL 0.9.7d binaries. I use RSA based self signed certificates for SSL communication. My httpd.conf has the following SSLCipherSuite configured SSLSessionCacheTimeout 600 SSLOptions +StdEnvVars +ExportCertData SSLCipherSuite

RE: Checking for socket read state

2005-05-31 Thread Pj
Ok... Sorry, maybe that was the wrong question altogether... I am trying to signal my blocking connection thread to end while OpenSSL is negotiating a connection with SSL_connect. Is there any way to tell SSL to stop once it enters SSL_connect, perhaps with a non-blocking approach? Pseudocode

RE: Checking for socket read state

2005-05-31 Thread David Schwartz
Ok... Sorry, maybe that was the wrong question altogether... I am trying to signal my blocking connection thread to end while OpenSSL is negotiating a connection with SSL_connect. Is there any way to tell SSL to stop once it enters SSL_connect, perhaps with a non-blocking approach?

openssl configure problems

2005-05-31 Thread zhu dengyu
Hi,everyone. I have set dir = ./CARoot in /usr/local/ssl/openssl.cnf,but when in /usr/local/ssl/misc I do ./CA.sh -newca command, the ca_default dir is still /usr/local/ssl/misc/demoCA. did i make any mistake? :?I?r??? (Z+???1? ?h[??Z+€ ?f?????)z{,?à

Re: how to sign as per PKCS1 v2.0.

2005-05-31 Thread Suram Chandra Sekhar
Hi, Thank you very much for the reply. I understood the schemes in PKCS#1v2.1. But some protocols wants the signature scheme as that defined in PKCS#1v2.0 as it has only one encoding method defined EMSA_PKCS1v1.5. How can I do this using Openssl 0.9.7c? Regards Suram At 09:35 PM 5/30/2005,

Re: how to sign as per PKCS1 v2.0.

2005-05-31 Thread Dr. Stephen Henson
On Tue, May 31, 2005, Suram Chandra Sekhar wrote: Hi, Thank you very much for the reply. I understood the schemes in PKCS#1v2.1. But some protocols wants the signature scheme as that defined in PKCS#1v2.0 as it has only one encoding method defined EMSA_PKCS1v1.5. How can I do this

SSLWRITE fails on HP-UX

2005-05-31 Thread Adam Mlodzinski
Hi there, I recently built the w3c libwww library with ssl support using openssl. I went through the pain of doing this on AIX, Linux, Solaris, HPUX and Windows. On all of the platforms, my builds are using the new libraries okay (so far - keeping my fingers crossed), except, that is, for HPUX.

Re: SSLWRITE fails on HP-UX

2005-05-31 Thread Lance Nehring
What does the chatr command show for your executable? Do the shared libraries have execute permissions? Adam Mlodzinski wrote: Hi there, I recently built the w3c libwww library with ssl support using openssl. I went through the pain of doing this on AIX, Linux, Solaris, HPUX and Windows. On

RE: SSLWRITE fails on HP-UX

2005-05-31 Thread Adam Mlodzinski
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lance Nehring What does the chatr command show for your executable? Do the shared libraries have execute permissions? Thanks for the quick reply - much obliged. If I chatr on openssl, I get the output below. Looks like I've

RE: SSLWRITE fails on HP-UX

2005-05-31 Thread Adam Mlodzinski
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lance Nehring What does the chatr command show for your executable? Do the shared libraries have execute permissions? On a more useful note, here's the output of chatr from my build system. The openssl libs are listed, but how

Re: how to sign as per PKCS1 v2.0.

2005-05-31 Thread Suram Chandra Sekhar
Hi, Thank you very much for the reply. I still have some confusion w.r.t to the version of the draft (PKCS#1 v2.0 and PKCS#1 v2.1 specification). I was referring to rfc3447 (PKCS#1 v2.1) and the older draft PKCS #1: RSA Cryptography Specifications Version 2.0. rfc3447(PKCS#1 v2.1) section 9.2