Hello,
The problem is resolved with the linker option, -Wl,-Bsymbolic, when
building the library.
Here are the details:
On 32-bit Ubuntu 8.04, here is how to build a dynamic library that
statically links with the FIPS-capable crypto library from OpenSSL.
===> cmd.cpp
#include
#include
int
m
Hello,
I have been developing an application using OpenSSL that needs an OCSP
responder, and for testing I use the following command to create the
responder:
openssl ocsp -index ./CA/index.txt -port -rsigner
./CA_resp/certs/responder.pem -rkey ./CA_resp/private/server.key -CA
./CA/ca.pem
My
Btw, on the same machine, 0.9.8r builds fine.
__
OpenSSL Project http://www.openssl.org
User Support Mailing Listopenssl-users@openssl.org
Automated List Manager
Anyone else having problems or know what this is caused by?
set ASM=ml64 /c /Cp /Cx /Zi
perl crypto\md5\asm\md5-x86_64.pl tmp32dll\md5-x86_64.asm
Use of uninitialized value $flavour in pattern match (m//) at
crypto\md5\asm\md5-x86_64.pl line 115.
ml64 /c /Cp /Cx /Zi /Fotmp
I have a custom-written SSL server that TLSv1 clients are not able to connect
to it. The TLSv1 handshake is failing with an SSL_R_NO_SHARED_CIPHER error. I
have a TLSv1 client using SSLv2 headers, and it is sending ciphers using 3-byte
ID numbers (I have a capture if needed - Wireshark display
Oddly enough, once I installed gcc44, it compiled and built and passed
all tests even though I started from make clean and changed no build
switches.
Thanks for the reply
On 02/10/2011 06:38 PM, Carter Browne wrote:
> I did not have any problems in RHEL 5.6 - I did use gcc44 rather than gcc.
>
>
On Thu, Feb 10, 2011 at 05:03:05PM +0100, Mounir IDRASSI wrote:
> I think you misunderstood Matthias's question? He is not asking about how
> to make his own CA accepted (from his post, it appears he already knows how
> to do that), but he is rather asking how to make an end entity server
> cer
> -Original Message-
> From: Mounir IDRASSI
>
> Personally I don't think it is possible currently without a change to
> OpenSSL internals or the use of the verify callback. That
> being said, I
> remember vaguely a post by Dr Stephen Henson related to this where he
> mentioned a planned cha
