I am trying to build openssl-0.9.4 on Solaris 5.6 and getting the following
errors from make after running ./config no-threads:
making all in crypto...
( echo "#ifndef MK1MF_BUILD"; \
echo " /* auto-generated by crypto/Makefile.ssl for crypto/cversion.c */";
\
echo " #define CFLAGS
\"cc
Hi,
I have just downloaded the openssl source, and I have som troubles
making the certs sa showed below. Make is failing why??
Output from config -t:
Operating system: 9000/813-hp-hpux11
Configuring for hpux11
/usr/bin/perl ./Configure hpux11
openssl version:
0.9.4
Output from make
The current cvs version(checked about 11 am today) fails make test
on unix for me - with the error:
rc4-64 is an unknown cipher
options are
(Somewhere after exptest)
My last compile was friday, without any problems in make test.
I think that the problem is from a commit by Stephen Henson:
Sue Beggs wrote:
I am trying to build openssl-0.9.4 on Solaris 5.6 and getting the following
errors from make after running ./config no-threads:
making all in crypto...
( echo "#ifndef MK1MF_BUILD"; \
echo " /* auto-generated by crypto/Makefile.ssl for crypto/cversion.c */";
\
echo "
Can anyone see what is wrong with the code below?
Unless I specifically set pX509NameEntry = NULL after every call to
X509_NAME_ENTRY_free(pX509NameEntry), I get an access violation in
libeay32.dll when I do the next call to X509_NAME_ENTRY_create_by_NID(...).
Shouldn't X509_NAME_ENTRY_free(...)
On Tue, Nov 16, 1999 at 04:28:35PM +0100, [EMAIL PROTECTED] wrote:
Can anyone see what is wrong with the code below?
Unless I specifically set pX509NameEntry = NULL after every call to
X509_NAME_ENTRY_free(pX509NameEntry), I get an access violation in
libeay32.dll when I do the next call to
Hello,
I want to learn how the SSL works and I'm trying to write an implementation of
it. I have a problem, though - after I connect to SSL port (443) there is
already data ready to be read from the socket - it's a message which says
"Error: must authenticate before using this service". I
I am having a problem using openssl s_client to
connect to the following server: 156.77.100.189:443
When I try to connect, I get an ssl handshake failure. I
suspect this has something to do with the fact that I am using the supplied test
certificates, but being a total ssl newcomer, I
On Tue, Nov 16, 1999 at 10:30:10PM +, Geoff Thorpe wrote:
Maybe we should have a naming convention for ..._set_... calls too?
There are already such ambiguities for them, e.g. SSL_CTX_set_tmp_rsa
vs. SSL_CTX_set_tmp_dh.
It seems to be a play-off between backwards compatibility, and
OpenCA Version 0.2.0 RELEASED - Major Release
=
OpenCA - The Open Certification Authority Toolkit
(http://www.openca.org)
The OpenCA core team is proud to announce the new release of the OpenCA.
This version incorporates many
As far as I can see 156.77.100.189:443 doesn't send its full certificate
chain => OpenSSL can't verify the server certificate. (Would be nice with
a working verify option...) Connecting with Netscape works fine because
the issuer (RSA Data Security, Secure Server Certification Authority) is
in
Well, it cannot do that for you.
X509_NAME_ENTRY_free() receives the pointer and has write access to change
the place to which the pointer is pointing, it however cannot manipulate
the pointer itself, which is defined in the calling function.
This would only be possible, if the call would
12 matches
Mail list logo
