Hello,
> We are having a dynamic certificate+key generation utility which
> generates cert+key as and when it gets requests from our component.
> Now we have ported our component to 64-bit but don't want to port this
> utility to 64-bit as we are not sure of stabiltiy of 64-bit openssl
> dlls.
>
>
I posted earlier on a similar topic, and I have since found out that
"no-ssl2" will build openssl without support for SSLv2 ciphers.
Unfortunately, I am using RedHat's Source RPM to do the build, and it
seems to be having an error due to the no-ssl2 flag. You can see the
error below, and trying th
On Mon, Jun 11, 2007, Mikolajczuk, Alan wrote:
> All,
>
> I have an IPv4 OCSP responder setup behind a 6 to 4 gateway. I am make
> requests to the IPv4 address, but when I make a request to the IPv6
> address OpenSSL will time out.
>
> Does OpenSSL support IPv6? Has anyone else run into this pro
All,
I have an IPv4 OCSP responder setup behind a 6 to 4 gateway. I am make
requests to the IPv4 address, but when I make a request to the IPv6
address OpenSSL will time out.
Does OpenSSL support IPv6? Has anyone else run into this problem?
Thanks,
Alan Mikolajczuk
Hi all
We are having a dynamic certificate+key generation utility which
generates cert+key as and when it gets requests from our component.
Now we have ported our component to 64-bit but don't want to port this
utility to 64-bit as we are not sure of stabiltiy of 64-bit openssl
dlls.
What I was
Thanks, that solved it.
On Jun 11, 2007, at 3:11 PM, Richard Whalen wrote:
Make sure that the order when you link them is libssl then libcrypto.
The VMS linker searches object libraries in order (and does not go
back). Since libssl references some routines in libcrypto that may
not be dire
Make sure that the order when you link them is libssl then libcrypto.
The VMS linker searches object libraries in order (and does not go back).
Since libssl references some routines in libcrypto that may not be directly
referenced by your code it is necessary to put libssl before libcrypto in th
