[openssl.org #1787] [PATCH] speed -multi buffered output fix

Resent to request tracker. OS: Linux OpenSSL version: 0.9.8i When running speed tests on multiple processes and using buffered output (e.g. to a file), openssl speed rsa1024 -multi 8 result the child processes inherit pending buffered output from the parent process, which in turn they send

ssl3_get_server_hello not threadsafe(?)

Hi, I've a simple program (used as a stress tool) that creates a number of threads, and uses a shared SSL_CTX to create an SSL object for each thread. My understanding of the threading model is that this fits with the intended thread-safety model of the library. Sporadically, I get

Asynchronous WinCE socket I/O (using WSAEventSelect) with Openssl

Hi, Can I know how Asynchronous WinCE socket I/O ( using WSAEventSelect) can be achieved using Openssl? Thanks in advance... BR, Irshad.

[openssl.org #1788] BUG REPORT: OpenSSL 0.9.7, patch included

OS: OpenBSD, Linux OpenSSL version: 0.9.7j - 0.9.7m Snippet from crypto/x509v3/v3_alt.c static int copy_email(X509V3_CTX *ctx, GENERAL_NAMES *gens, int move_p) { [...] if(ctx-flags == CTX_TEST) return 1; if(!ctx || (!ctx-subject_cert !ctx-subject_req)) [...] As you see

PSK-TLS support in OpenSSL

It is required in the project to use the PSK-TLS auth. Offical OpenSSL from openssl.org does not support this authentication. Expecting PSK-TLS release in 0.9.9 Please can anyone tell when will 0.9.9 be released. Thanks, Yathish.H.S Senior Engineer - Software SASKEN BUSINESS DISCLAIMER

Re: PSK-TLS support in OpenSSL

On Tue, 18 Nov 2008 14:25:53 +0100 Yathish Shivanna [EMAIL PROTECTED] wrote: It is required in the project to use the PSK-TLS auth. Offical OpenSSL from openssl.org does not support this authentication. Expecting PSK-TLS release in 0.9.9 Last time I looked it was in CVS version and it was

OpenSSL FIPS 140-2 validation

Good news for developers and vendors of software for the U.S. and Canadian government market where FIPS 140-2 validated cryptography is required. The OpenSSL FIPS Object Module, a software component compatible with the OpenSSL API, has been FIPS 140-2 validated (see certificate #1051 and Security

Re: OpenSSL FIPS 140-2 validation

I dunno who I'm supposed to give feedback to, but this format of FIPS announcement needs some work. First, the subject line doesn't say anything about the version of the FIPS module that has been validated. (In this case, it should be something like OpenSSL FIPS 140-2 validation for module

Re: OpenSSL FIPS 140-2 validation

On Tue, Nov 18, 2008, Kyle Hamilton wrote: Second, it doesn't describe which version of the OpenSSL API that the newly-validated module supports. (in this case, it supports v0.9.8 (and requires 0.9.8i onward), but I dunno about 0.9.7?) Providing compatibility with a version bump in the API

Re: [PATCH] keep CHIL engine from breaking in non-threaded situations [openssl.org #1736]

On Nov 11, 2008, at 12:28 AM, Sander Temme wrote: On Nov 2, 2008, at 9:19 AM, Sander Temme wrote: The following compiles and tests cleanly on trunk and on the latest snapshot of 0.9.8-stable (with offset 1 in e_chil.c). Also attached to prevent line wrap: Ping? Any chance to squeeze

Re: OpenSSL FIPS 140-2 validation

Second, it doesn't describe which version of the OpenSSL API that the newly-validated module supports. (in this case, it supports v0.9.8 (and requires 0.9.8i onward), but I dunno about 0.9.7?) Providing compatibility with a version bump in the API is significant enough that it should be called

Re: OpenSSL FIPS 140-2 validation

On Tue, Nov 18, 2008, Brad House wrote: Second, it doesn't describe which version of the OpenSSL API that the newly-validated module supports. (in this case, it supports v0.9.8 (and requires 0.9.8i onward), but I dunno about 0.9.7?) Providing compatibility with a version bump in the API is

Re: OpenSSL FIPS 140-2 validation

Finally, I'm getting X509_V_ERR_CERT_SIGNATURE_FAILURE errors when in fips mode during SSL negotiation, but the same binary, simply telling it via a config setting not to enter fips mode, works fine. This is to ssl3.vitalps.net:5003, specifically, but I don't have any reason to believe other

RE: OpenSSL FIPS 140-2 validation

The problem is the root CA uses MD2WithRSAEncryption as a signature algorithm and that is prohibited in FIPS mode. I'm pretty ignorant when it comes to FIPS, is this a limitation of the FIPS requirements itself or a limitation of OpenSSL's FIPS validation? The former. FIPS does not

Re: OpenSSL FIPS 140-2 validation

The problem is the root CA uses MD2WithRSAEncryption as a signature algorithm and that is prohibited in FIPS mode. I'm pretty ignorant when it comes to FIPS, is this a limitation of the FIPS requirements itself or a limitation of OpenSSL's FIPS validation? The former. FIPS does not allow the