Re: [error] Certificate Verification: Error (34): unhandled critical extension

Bonjour Peter Sylvester, >>Extensions are ignored in the root. >>Without telling what critical extensions you have, it is difficult to help. I had some extensions set to critical in my Sub CA certificates, i have re generated all the sub CA certificates and now it works fine. Thats rite that

RE: openssl 1.0.0 issue with sendmail

> From: owner-openssl-us...@openssl.org On Behalf Of David Carvalho > Sent: Wednesday, 09 June, 2010 06:06 > I am having trouble since I replaced my e-mail server (hardware and to Fedora 12). > Basically I'm using almost the same sendmail.mc file than in the previous server

certs with the same Subject Name

I have 2 different certs with the same subject name in a CA dir: lrwxrwxrwx 1 chris chris 23 2010-06-10 14:35 0721e1e6.0 -> other.pem lrwxrwxrwx 1 chris chris 18 2010-06-10 14:35 0721e1e6.1 -> ssl.pem when I try to establish an ssl connection: openssl s_client -verify 10 -connect example.com

RE: Segfault when encrypting

Hannes Schuller wrote: > > I'm very puzzled here. Why do you sign the reply and then sign a hash > > of the signature? You say "Message encryption successful", but that's > > a signature you're doing, not an encryption. > I was under the impression that RSA_private_encrypt and > RSA_public_encr

RE: is openssl library thread safe

See http://lmgtfy.com/?q=openssl+thread+safe From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org] On Behalf Of Arunkumar Manickam Sent: Thursday, June 10, 2010 8:18 AM To: openssl-users@openssl.org; openssl-...@openssl.org Subject: is ope

Header file confliction for Openssl 1.0 and winsock2.h

Winsock.h file is included in dtls1.h, and also dtls1.h included in ssl.h, without any conditions. This will make the project which use Windows socket and openssl get a lot of compiling errors. Nowadays most people on Windows use winsock2.h instead of winsock.h, by defining WIN32_MEAN_AND_LEAN, etc

Re: Segfault when encrypting

"David Schwartz" wrote: > > Hannes Schuller wrote: > > > hash = (unsigned char *)malloc(RSA_size(rsa) * sizeof(unsigned > > char)); ciphertext = (char *)malloc(RSA_size(rsa) * sizeof(char)); > > signature = (char *)malloc(RSA_size(rsa) * sizeof(char)); > > if (ciphertext != NULL && signature !=

Re: is openssl library thread safe

Hi, Thus wrote Arunkumar Manickam (arun.c...@gmail.com): > Is openssl library thread safe so that it can be used in an multithreaded > environment as is. http://www.openssl.org/support/faq.html#PROG1 Regards, Martin __ Open

Re: Preamble Change with PKCS12 -> PEM

On Wed, Jun 09, 2010, Robinson, Richard L (Rick) wrote: > I was evaluating openssl-1.0.0a and performed a PKCS12 conversion to PEM > using the following command: > > openssl pkcs12 -in myfile.p12 -nodes -out myfile.pem > > However, I noticed that in the resulting PEM file the preamble for

Re: is openssl library thread safe

Hi, Yes, it is thread safe if you define and initialize necessary locking functions at startup: http://www.openssl.org/docs/crypto/threads.html Regards, AW Arunkumar Manickam pisze: Hi, Is openssl library thread safe so that it can be used in an multithreaded environment as is. Thanks, Aru

RE: compilation problem for xscale.

My apologies to all for mis-remembering what package the issue was relating to - it was with an iscsi target (IET, which is certainly GPL!). I was working with both openssl and IET when I had this problem, and for some reason I associated it with openssl instead of IET. Sorry for the extra noise!

is openssl library thread safe

Hi, Is openssl library thread safe so that it can be used in an multithreaded environment as is. Thanks, Arun