Two weeks ago Viktor Dukhovni wrote:
Actually, SHA-2 SHOULD NOT (yet) be used for signing certificates.
Many TLSv1 clients don't support SHA-2 and servers must present
SHA-1 certificates except when TLSv1.2 clients indicate SHA-2 support.
Fielding multiple certificates with different
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
Any plans for Keccak / SHA-3?
http://www.nist.gov/itl/csd/sha-100212.cfm
Cheers,
Paul
_
Paul A. Suhler, PhD | Firmware Engineer | Quantum Corporation | Office:
949.856.7748 |
Oops. Forgot the
;-)
From: owner-openssl-us...@openssl.org [mailto:owner-openssl-us...@openssl.org]
On Behalf Of Paul Suhler
Sent: Tuesday, October 02, 2012 8:38 PM
To: openssl-users@openssl.org
Subject: SHA-3?
* PGP Bad Signature, Signed: 10/2/2012 at 8:38:22 PM
Any plans
Perhaps it's related to CVE-2011-4576:
https://kc.mcafee.com/corporate/index?page=contentid=KB75138actp=LIST
and
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4576
The SSL 3.0 implementation in OpenSSL before 0.9.8s and 1.x before 1.0.0f does
not properly initialize data structures for
Where is the draft User Guide for 2.0 available, please? The most recent one
that NIST has is for 1.2.3, dated about two weeks ago.
Thanks,
Paul
_
Paul A. Suhler, PhD | Firmware Engineer |
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi, developers.
I assume that the X9.31 key gen algorithm will be FIPS 140-2 certified, as it
was in the FIPS module version 1.2. Is the KAT for X9.31 key generation
covered by the PRNG testing in fips_rand_selftest.c::do_x931_test(), as an
I haven't tried your build process, but is the following still in
ssl_lib.c::SSL_CTX_new()
/* Disable TLS v1.2 by default for now */
ret-options |= SSL_OP_NO_TLSv1_2;
Paul
_
Hi, everyone.
(This got no response on the developers list, so I'll retry it here.)
Should EVP_Cipher() be used? I've found an inconsistency in its return
values: For the cipher EVP_aes_256_gcm, successful decryption returns
the length of the input. (That's what aes_gcm_cipher()
One related caveat. I've found that if OPENSSL_NO_FP_API is defined, then
there will be some undefined symbol errors at compile time; some references to
FILE, etc. are not conditionalized out.
However, I've done an embedded port to a non-standard OS, so your mileage may
vary.
Paul
Hi, all.
This question is perhaps best answered by Steve Henson, but I'll address
it to this list.
I've found that using openssl-SNAP-20110526, we send a Client Hello with
a signature_algorithms extension that apparently contains duplicate
entries.
If I understand RFC 5246 correctly,
Hi, everyone.
I've been trying to use the TortoiseCVS client (on WinXP) to access
cvs.openssl.org. When I go to the Revision tab, select Choose branch
or tag, and click on Update list I get a failure with the following
nearly-useless message:
In C:\Documents and Settings\suhlerp\My
Is anyone else having trouble opening openssl-SNAP-20110411.tar.gz
ftp://ftp.openssl.org/snapshot/openssl-SNAP-20110411.tar.gz and
openssl-SNAP-20110412.tar.gz
ftp://ftp.openssl.org/snapshot/openssl-SNAP-20110412.tar.gz ? I can
extract the .tar file, but then 7Zip says that it can't be opened as
I'm forwarding this to the users list so that others won't be confused
by the documentation as I was.
Paul
-Original Message-
From: owner-openssl-...@openssl.org
[mailto:owner-openssl-...@openssl.org] On Behalf Of Paul Suhler
Sent: Wednesday, October 13, 2010 11:10 AM
To: openssl
Hi, everyone.
I've found that when a server built with
openssl-1.0.1-stable-SNAP-20101004 receives a Client Hello from a client
specifying TLS 1.0 (version = 0x0301), the connection is rejected for a
bad version. This appears to be implemented in ssl3_get_client_hello()
by:
if
I haven't seen that, but I have seen Chrome (on MacOS 10.5.8) complain
about the validity of certificates that don't bother Firefox.
Paul
___
Paul A. Suhler | Firmware Engineer | Quantum Corporation | Office:
949.856.7748 | paul.suh...@quantum.com
] On Behalf Of Paul Suhler
Sent: Saturday, February 27, 2010 6:17 AM
To: openssl-users@openssl.org; openssl-users@openssl.org
Subject: RE: Verify with RSA Public Key Fails
Hi, Mounir.
I misspoke. The value of the public exponent is in fact 3.
Any idea what is the purpose of the padding check
public key, replace the value of the
private exponent you are using by the value of the corresponding public
exponent.
If my guess is correct, then you should be able to verify the signature
correctly.
Cheers,
--
Mounir IDRASSI
IDRIX
http://www.idrix.fr
On 2/27/2010 3:00 AM, Paul Suhler wrote
Hi, everyone.
In Openssl 0.9.8i, I'm trying to take an RSA public exponent and public
modulus, assemble them into an RSA key, and use that to verify a
signature for a message. However, EVP_VerifyFinal() always fails,
apparently because of the wrong use of padding.
My code:
RSA *
Hi, everyone.
I'm trying to enable session caching, but my server doesn't seem to send
a session ID.
According to
http://www.openssl.org/docs/ssl/SSL_CTX_set_session_id_context.html, all
I have to do is invoke SSL_CTX_set_session_id_context() with a pointer
to a string (or binary data) and the
. Stephen Henson
Sent: Sat 8/8/2009 3:46 AM
To: openssl-users@openssl.org
Subject: Re: BIO definitions missing in 0.9.8k
On Fri, Aug 07, 2009, Paul Suhler wrote:
Hi, all.
I'm trying to upgrade from 0.9.8i to 0.9.8k for an embedded application.
There are two new files in crypto/bio
Hi, all.
I'm trying to upgrade from 0.9.8i to 0.9.8k for an embedded application.
There are two new files in crypto/bio that are having undefined symbols,
and I can't find the symbols defined anywhere in the code:
bio_asn1.c:
BIOC_C_SET_EX_ARG
BIO_C_SET_PREFIX
BIO_C_GET_PREFIX
BIO_C_GET_SUFFIX
Hi.
Using OpenSSL 0.9.8i, I'm getting a memory leak when I create a CSR. My
process is taken more-or-less from the Viega, et al. book:
Initial:
X509_REQ_new() to get the request structure
OPENSSL_malloc(1) to add a byte to the request for the version
RSA Key:
RSA_new() for an RSA structure
-users@openssl.org
Subject: Re: Memory Leak Creating a CSR
On Sat, May 30, 2009, Paul Suhler wrote:
Hi.
Using OpenSSL 0.9.8i, I'm getting a memory leak when I create a CSR.
My process is taken more-or-less from the Viega, et al. book:
No idea what that version is but the one in demos/x509
That's how FIPS 140 certification works. If *any* change is made to the thing
that was certified, then it must reviewed and re-certified. If the change is
small, then the review process can be short. The certifying lab has to ensure
that the change didn't intentionally or unintentionally
25 matches
Mail list logo
