The code below deadlocks against itself in some systems because
EVP_PKEY_free call CRYPTO_add with CRYPTO_LOCK_EVP_PKEY.
-Costa
--- openssl-0.9.8t/crypto/asn1/x_pubkey.c 2005-07-16 04:13:04.0 -0
700
+++ openssl-0.9.8x/crypto/asn1/x_pubkey.c 2012-05-10 10:51:28.0 -0
When using the following command to connect to an xmpp server which uses a
different hostname to the published ssl certificate and jabber domain openssl
goes into an infinite loop.
$ openssl s_client -starttls xmpp -connect some.jabber.server -debug
CONNECTED(0003)
write to 0x7ff873c1f130
Hello again,
as I promised, here is the optimized code for SHA-256 hash, x86
platform. Should work faster on Core 2/iX up to 20%. This code you are
free to use (or modify) in any form on OpenSSL and GRYPTOGAMS. I guess
you should make it PIC, as any other code for x86 (I didn't make it
Is AES performance expected to be much lower when using the FIPS 2.0
Object Module? Below are the speed results when using AES-128-CBC with
and w/o the FIPS module. The host system is 32-bit Linux using gcc
4.4.3. The host system does not have AES-NI support. No additional
config arguments
Is AES performance expected to be much lower when using the FIPS 2.0
Object Module?
Which CPU? You said it's non-AES-NI-capable, but is it SSSE3-capable? If
yes, then see related note at
http://www.mail-archive.com/openssl-dev@openssl.org/msg29827.html.
Below are the speed results when using
I built both a aix 5.2 / 32 bit version of openssl 1.0.1b and a aix 6.1
/ 64 bit version. I also did a build of the latest openssh. When
testing the 32 bit openssh I had some problems that seem to come from
running ssh-keygen.
The aix 6.1 / 64 bit version runs fine with out problems
[openssl-dev@openssl.org - Fri May 11 02:12:15 2012]:
This is a problem reproducible with s_client / s_server.
OpenSSL 1.0.1b and just reconfirmed present in 1.0.1c.
Server:
openssl s_server -cert spodhuis-smtpmx.crt.pem -key spodhuis-
smtpmx.key.pem
Client:
openssl s_client
[openssl-dev@openssl.org - Fri May 11 14:35:45 2012]:
The code below deadlocks against itself in some systems because
EVP_PKEY_free call CRYPTO_add with CRYPTO_LOCK_EVP_PKEY.
Should be fixed with: http://cvs.openssl.org/chngview?cn=22568
Thanks for the report.
Steve.
--
Dr Stephen N.
According to our records, your request has been resolved. If you have any
further questions or concerns, please respond to this message.
__
OpenSSL Project http://www.openssl.org
Development Mailing
According to our records, your request has been resolved. If you have any
further questions or concerns, please respond to this message.
__
OpenSSL Project http://www.openssl.org
Development Mailing
how come it's not required in all other perlasm modules?
errors do also occure in other perlasm modules, but i'am running this
configure command without asm support which avoids calling other
perlasm modules?
perl Configure debug-VC-WIN64A no-asm --prefix=x64/debug
I have two perl.exe
Thanks for the information, that explains it. The vpaes-x86 module
isn't included in the FIPS module.
The CPU information is:
model name: Intel(R) Core(TM) i7 CPU Q 720 @ 1.60GHz
On 05/11/2012 09:07 AM, Andy Polyakov wrote:
Is AES performance expected to be much lower when
I originally thought my problem was with ssh, so that is what I was
looking it, after I finally found that the problem was with the ssl, I
sent the email to you. After that I did some more testing and found
that by using the no-asm flag during the config everything worked normally.
I guess
13 matches
Mail list logo
