Hello,
is there a possibility to declare an use own private extensions with the
OpenSSL command line tool (especially the ca and req commands)? I'm out of
ideas and would be glad to get a solution from you.
Best regards
Gerd
_
In message on Wed, 16 Oct 2002
10:07:17 -0500 (CDT), Mark <[EMAIL PROTECTED]> said:
mark> I am using Forte cc for my compiler and get this error. It seems to just
mark> go wacky inside the ifdefs for DEVRANDOM, which I defined since I have
mark> p
My only advice would be to use gcc. I can confirm that gcc 3.2 will
compile openssl on Solaris 8 with no problem. Alternatively, if you
don't mind an out-of-the-box openssl, get the package from
www.sunfreeware.com.
-Original Message-
From: Mark [mailto:[EMAIL PROTECTED]]
Sent: Mittwoch,
I am using Forte cc for my compiler and get this error. It seems to just
go wacky inside the ifdefs for DEVRANDOM, which I defined since I have
patched the system to include /dev/random:
making all in crypto/rand...
cc -I.. -I../.. -I../../include -KPIC -DTHREADS -D_REENTRANT -DDSO_DLFCN
-DHAVE_
Hi,
I'm trying to add session caching to a multi-threaded
SSL client. I've run into a crash when my client,
with caching enabled, is talking to an SSL server
which has caching DISabled.
What I see in the debugger is that if more than one
client connection is coming up, and both are using the
sa
Greetings.
I recently re-compiled my application with OpenSSL 0.9.6g (it was
previously linked with 0.9.6c).
I have a problem with the ''PKCS12_parse'' function that I didn't have
before (platform is Solaris 8).
If my application calls ''PKCS12_parse'' more than once (at different
moments, eve
I have just built another redhat 7.3 machine (default out of the box) using
the same kernel / GCC / openssl etc the same configure options, the only
difference is more memory and a faster CPU in the newer machine
I get the same problem.
make all works, make tests seg faults exactly the same. I a
Hi,
I'm using Openssl 0.9.6g on
Linux. After I've revoked a certificate and generated a CRL, I was wonder what
time source did the Openssl get to stamp in the CRL. After I generated the CRL,
I used "asn1parse" to dump the CRL into ASN1 then in the CRL time
section the openssl used my sys