On Mon, Feb 24, 2003, Ravun, Oleg wrote:
> Hi,
> When I try to convert unencrypted private key from PEM format to DER using
> openssl pkcs8 -inform PEM -outform DER -in server.pem -out server.der
> -nocrypt
>
> I get the next message:
>
> Error decrypting key
> 1968:error:0906D06C:PEM routines:
On Mon, 24 Feb 2003 21:31:38 +0100, Folkert van Heusden wrote:
>Nope, won't work either!
>I had something like:
>
>send:
>pthread_mutex_lock(&lock);
>send
>unlock();
>
>and for receive:
>pthread_mutex_lock(&lock);
>receive
>unlock();
>
>well, you get my point.
>And strangel
Are you using the mutex locks with blocking or non-blocking sockets?
Using mutex locks with non-blocking sockets most definitely works.
Folkert van Heusden wrote:
So, my questions are:
- am I doing something and IS openssl threadsafe?
- is there an alternative for openssl doing which
Hi, I am hoping to call SSL_CTX_load_verify_locations() in my app an
arbitrary amount of times, specifying either CAdir or CApath, or both.
Looking at the source it looks like it should work the way I was hoping it
would: namely that a subsequent call to SSL_CTX_load_verify_locations() will
NOT
>So, my questions are:
>- am I doing something and IS openssl threadsafe?
>- is there an alternative for openssl doing which also
>does the key-exchange for me?
YOU> Just implement your own per-connection mutex and you won't
YOU> have any problems.
Nope, won't work either!
I had something like:
s
folkert> I found out (yes, the rought way) that openssl is not
folkert> thread-safe: 2 threads doing encryption & decryption
folkert> concurrent goes horribly wrong.
folkert> So, my questions are:
folkert> - am I doing something and IS openssl threadsafe?
folkert> - is there an alternative for open
On Mon, 24 Feb 2003 20:13:31 +0100, Folkert van Heusden wrote:
>Hi,
>I found out (yes, the rought way) that openssl is not
>thread-safe: 2 threads doing encryption & decryption
>concurrent goes horribly wrong.
Two threads accessing the same connection at the same time won't
work. Otherwis
In message <[EMAIL PROTECTED]> on Mon, 24 Feb 2003 20:13:31 +0100, "Folkert van
Heusden" <[EMAIL PROTECTED]> said:
folkert> I found out (yes, the rought way) that openssl is not
folkert> thread-safe: 2 threads doing encryption & decryption
folkert> concurrent goes horribly wrong.
folkert> So, my
Hi,
I found out (yes, the rought way) that openssl is not
thread-safe: 2 threads doing encryption & decryption
concurrent goes horribly wrong.
So, my questions are:
- am I doing something and IS openssl threadsafe?
- is there an alternative for openssl doing which also
does the key-exchange for
Dr. Stephen Henson wrote:
On Mon, Feb 24, 2003, Rabellino Sergio wrote:
Dear developers,
I had a little (maybe) trouble to get compile the latest release of the
package:
the compiler is telling me about a redefinition of NETSCAPE_ENCRYPTED_PKEY
and NETSCAPE_PKEY
in the file crypto/asn1/n_pkey
On Mon, Feb 24, 2003, Rabellino Sergio wrote:
> Dear developers,
> I had a little (maybe) trouble to get compile the latest release of the
> package:
>
> the compiler is telling me about a redefinition of NETSCAPE_ENCRYPTED_PKEY
> and NETSCAPE_PKEY
>
> in the file crypto/asn1/n_pkey.c at
Dear developers,
I had a little (maybe) trouble to get compile the latest release of the package:
the compiler is telling me about a redefinition of NETSCAPE_ENCRYPTED_PKEY and NETSCAPE_PKEY
in the file crypto/asn1/n_pkey.c at line 96 and 109 ( DECLARE_ASN1_ENCODE_FUNCTIONS_const ).
Comm
12 matches
Mail list logo
