First, what do you mean by string? I assume you realize that raw
RSA-encrypted values
(and other modern algorithms like AES and RC4 also) are binary data which
can contain
zero bytes and thus are not C strings; strlen() etc. won't work right. This
would cause
trouble on all platforms, but onl
>From: owner-openssl-users On Behalf Of Kiran G
>Sent: Wednesday, October 30, 2013 00:13
>This is the openssl client output from my desktop:
>$ openssl s_client -connect 192.168.3.152:443 -debug
>CONNECTED(0003)
>write [v3format ClientHello with record and max ver 0300
and no extensions]
W
On Wed, Oct 30, 2013 at 06:13:51PM +, Paul Suhler wrote:
> Note that SHA-1 is being deprecated by NIST for generating new
> signatures. You may want to consider a SHA-2 algorithm (e.g.,
> SHA-224 or SHA-256). In principle it's still okay to *validate*
> legacy signatures, e.g., SHA-1.
Actua
On 10/28/13, Abdul Anshad wrote:
> Hello all,
>
> Could anyone please explain me the whole process for building FIPS capable
> openssl on solaris 10 SPARC architecture ?
Have you checked the user guide at http://www.openssl.org/docs/fips/ ?
Dennis
___
Hello Marcus
On 30.10.2013 19:26, Marcus Schmitt wrote:
nameopt = default_ca
certopt = default_ca
what do this lines should mean in your openssl.cnf?
can you do the following with each of your generated certificates:
openssl x509
Note that SHA-1 is being deprecated by NIST for generating new signatures. You
may want to consider a SHA-2 algorithm (e.g., SHA-224 or SHA-256). In
principle it's still okay to *validate* legacy signatures, e.g., SHA-1.
-Original Message-
From: owner-openssl-us...@openssl.org [mailto:
Hello Walter,
the problem is that the openssl.cnf file already include this line:
This is my file:
===
# OpenSSL configuration file.
#
# Establish working directory.
dir = .
[ ca ]
default_ca = CA_default
[ CA_default ]
ser
Hello,
On 30.10.2013 18:17, Marcus Schmitt wrote:
I have one problem after I created a root-CA, intermediate-CA and a server
certificate. After I configured my apache with the server cert, key and
intermediate cert and importing the root-CA to firefox 24 I received the
following error when I
Hello,
I have one problem after I created a root-CA, intermediate-CA and a server
certificate. After I configured my apache with the server cert, key and
intermediate cert and importing the root-CA to firefox 24 I received the
following error when I browse to the website:
Could not verify this
Hi,
I want the client side don't try to verify the server certificate.
The verify_mode in SSL_ctx_st is set to SSL_VERIFY_NONE. But connection always
terminated after calling x509_verify_cert().
Do you know what happens? The doc says this mode set in client side will
disable verification of ser
Hi all,
I am a HP employee and we use OpenSSL in one of our applications by
creating a static library libssl.a and linking against it. The
application runs on various platforms like Windows, Linux, HP-UX,
OpenVMS and etc.
In one of the customer setup running HP-UX 11.31 ia64, the application
cras
11 matches
Mail list logo