On 11/24/04 02:19 PM, Louis LeBlanc sat at the `puter and typed:
SNIP
Have you tried connecting using s_client? I suggest you try it with
-bugs and possibly also restricting the ciphersuites in use too and
possibly the SSL protocols too.
Now that sheds a little light. It comes through
Howdy,
To test the security of my proprietary HTTPS server, built with OpenSSL
library version 0.9.7d, I ran Nessus version 2.2 against it and it reported
the following alert (as issued by Nessus plug-in ID 11875, described at:
http://cgi.nessus.org/plugins/dump.php3?id=11875 ):
Is there a problem with the install script? The make
and make test showed no errors.
Output from Make Install
Installing fips
Making install in fips/sha1
Sh: syntax error at line 2: `; unexpected
***error code 2
make: Fatal error Command failed for target `install
current
Does anyone has a piece C/C++ code to generate an RSA X509 Self-Signed
Certificate programatically?
I have googled, man(1)ed, and read O'Reilly OpenSSL book and am seeing
different incomplete approaches.
I need to generate the certificatae at run-time in case my server.pem
file is not
On Tue, Nov 30, 2004, Medi Montaseri wrote:
Does anyone has a piece C/C++ code to generate an RSA X509 Self-Signed
Certificate programatically?
I have googled, man(1)ed, and read O'Reilly OpenSSL book and am seeing
different incomplete approaches.
I need to generate the certificatae at
On Tue, Nov 30, 2004, Andrew Kraslavsky wrote:
Howdy,
To test the security of my proprietary HTTPS server, built with OpenSSL
library version 0.9.7d, I ran Nessus version 2.2 against it and it reported
the following alert (as issued by Nessus plug-in ID 11875, described at:
Thanks for the quick reply
Cheers
Dr. Stephen Henson wrote:
On Tue, Nov 30, 2004, Medi Montaseri wrote:
Does anyone has a piece C/C++ code to generate an RSA X509 Self-Signed
Certificate programatically?
I have googled, man(1)ed, and read O'Reilly OpenSSL book and am
On Tue, Nov 30, 2004, Dr. Stephen Henson wrote:
On Mon, Nov 29, 2004, Manfred Faulandt wrote:
Many thanks for the very competent answer. We noticed the UTF8 encoding
but thought about it as a why not? matter (and we didn't look into a
RFC neither).
The CA is a Microsoft Shop
On Tue, Nov 30, 2004, Andrew Kraslavsky wrote:
To test the security of my proprietary HTTPS server, built with OpenSSL
library version 0.9.7d, I ran Nessus version 2.2 against it and it reported
the following alert (as issued by Nessus plug-in ID 11875, described at:
hi,
when I write my program,for example,I want to use openssl's function:BIO_write.
And I write all openssl's header file in my program.
such as:
#include openssl/bio.h#include openssl/err.h#include openssl/x509.h#include openssl/x509v3.h#include openssl/pem.h
but there is always wrong:
Do you have the correct path setup for
the openssl libraries in your compiler ? e.g. -L/usr/local/ssl/lib
Andrew.
alan alan [EMAIL PROTECTED]
Sent by: [EMAIL PROTECTED]
01/12/2004 02:15 PM
Please respond to
[EMAIL PROTECTED]
To
[EMAIL PROTECTED]
cc
First,thanks for your answer.Another,how to set the path for the openssl libraries in my compiler?
I just compiled it like this:
gcc settime.c
I don't kown how to add path.Can you help me again?Thanks![EMAIL PROTECTED] wrote:
Do you have the correct path setup for the openssl libraries in your
12 matches
Mail list logo