[openssl.org #2657] Win32: fail to compile - 1.0.1 snapshot 20111211
VisualStudio 2010 perl Configure VC-WIN32 ms\do_ms.bat nmake -f ms\nt.mak .. ml /nologo /Cp /coff /c /Cx /Zi /Fotmp32\vpaes-x86.obj tmp32\vpaes-x86.asm Assembling: tmp32\vpaes-x86.asm tmp32\vpaes-x86.asm(491) : error A2070:invalid instruction operands tmp32\vpaes-x86.asm(527) : error A2070:invalid instruction operands tmp32\vpaes-x86.asm(545) : error A2070:invalid instruction operands tmp32\vpaes-x86.asm(572) : error A2070:invalid instruction operands tmp32\vpaes-x86.asm(616) : error A2070:invalid instruction operands NMAKE : fatal error U1077: 'C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\ml.EXE' : return code '0x1' Stop. ml Microsoft (R) Macro Assembler Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #2639] Resolved: When running pkits-test.pl on 1.0.0e or trunk, three tests fail
Stephen Henson via RT r...@openssl.org writes: According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. I see a related change, to permit use of the old PKITS (with now expired trust anchor). However, the three tests in the new PKITS (1.0.1) still fail for me. (This is with a default build of the trunk on GNU/Linux x86_64 (Debian testing).) __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #2639] Resolved: When running pkits-test.pl on 1.0.0e or trunk, three tests fail
Stephen Henson via RT r...@openssl.org writes: According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. I see a related change, to permit use of the old PKITS (with now expired trust anchor). However, the three tests in the new PKITS (1.0.1) still fail for me. (This is with a default build of the trunk on GNU/Linux x86_64 (Debian testing).) __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #2639] Resolved: When running pkits-test.pl on 1.0.0e or trunk, three tests fail
Stephen Henson via RT r...@openssl.org writes: According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. I see a related change, to permit use of the old PKITS (with now expired trust anchor). However, the three tests in the new PKITS (1.0.1) still fail for me. (This is with a default build of the trunk on GNU/Linux x86_64 (Debian testing).) __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
[openssl.org #2639] When running pkits-test.pl on 1.0.0e or trunk, three tests fail
[bruce.steph...@isode.com - Wed Dec 14 18:45:24 2011]: Stephen Henson via RT r...@openssl.org writes: According to our records, your request has been resolved. If you have any further questions or concerns, please respond to this message. I see a related change, to permit use of the old PKITS (with now expired trust anchor). However, the three tests in the new PKITS (1.0.1) still fail for me. (This is with a default build of the trunk on GNU/Linux x86_64 (Debian testing).) As I indicated there were problems with the PKITS data itself, not OpenSSL. The test data has now been updated (see message from David Cooper in PKITS mailing list). Try downloading it again from NIST site. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #2639] When running pkits-test.pl on 1.0.0e or trunk, three tests fail
Stephen Henson via RT r...@openssl.org writes: [...] As I indicated there were problems with the PKITS data itself, not OpenSSL. The test data has now been updated (see message from David Cooper in PKITS mailing list). Try downloading it again from NIST site. OK, thanks. I thought that might be the case (and was just reading the emails). I guess I must have committed the updated PKITS before the changes were made. __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #2657] Win32: fail to compile - 1.0.1 snapshot 20111211
The same for SNAP-20111213 On 14 December 2011 19:54, Andrey Kulikov via RT r...@openssl.org wrote: ml /nologo /Cp /coff /c /Cx /Zi /Fotmp32\vpaes-x86.obj tmp32\vpaes-x86.asm Assembling: tmp32\vpaes-x86.asm tmp32\vpaes-x86.asm(491) : error A2070:invalid instruction operands tmp32\vpaes-x86.asm(527) : error A2070:invalid instruction operands tmp32\vpaes-x86.asm(545) : error A2070:invalid instruction operands tmp32\vpaes-x86.asm(572) : error A2070:invalid instruction operands tmp32\vpaes-x86.asm(616) : error A2070:invalid instruction operands NMAKE : fatal error U1077: 'C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\ml.EXE' : return code '0x1' Stop. __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #2655] speed sha1 hang up - 1.0.1 snapshot 20111211 - Cygwin
Checked with 1.0.0e - the same problem. speed hangs up with md4 md5 mdc2 and sha1, but works well with sha256 sha512 and whirlpool. I downloaded 8G file via s_server from 1.0.1 snapshot 20111213 - works fine. Seems problem in speed' itself, or, as Andy mentioned - in time calculation. As in addition, even if speed' do not hangs up, each group of block calkulation MAY take significantly more than 3 sec... On 14 December 2011 01:45, Andrey Kulikov via RT r...@openssl.org wrote: Tested on two computers. Both native (i.e. non-VM) Windows7 x64 Professional (without SP1). One has E8600 CPU, the other is laptop with i5 mobile CPU. Both has 8G RAM. Both working stable for a monthes. No abnormalities, no BSODs. gcc version 3.4.4 (cygming special, gdc 0.12, using dmd 0.125) Cygwin DLL version is 1.7.9-1 Package list (output of cygcheck -cd )attached. On 13 December 2011 13:28, Andy Polyakov via RT r...@openssl.org wrote: Program behavior appears to be sane, Is it virtual machine? Which OS is it? What is the host? I.e. VMware, Xen, ...? Have you ever observed anomalies in ping output? Anomalies like it's reporting negative round-trip time? __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #2655] speed sha1 hang up - 1.0.1 snapshot 20111211 - Cygwin
downloaded 8G file via s_server from 1.0.1 snapshot 20111213 - works fine. Using RC4-SHA chipthersuite. __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #2655] speed sha1 hang up - 1.0.1 snapshot 20111211 - Cygwin
Checked with 1.0.0e - the same problem. speed hangs up with md4 md5 mdc2 and sha1, but works well with sha256 sha512 and whirlpool. I downloaded 8G file via s_server from 1.0.1 snapshot 20111213 - works fine. (using RC4-SHA chiphersuite) Seems problem in speed' itself, or, as Andy mentioned - in time calculation. As in addition, even if speed' do not hangs up, each group of block calkulation MAY take significantly more than 3 sec... __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #2655] speed sha1 hang up - 1.0.1 snapshot 20111211 - Cygwin
Checked with 1.0.0e - the same problem. speed hangs up with md4 md5 mdc2 and sha1, but works well with sha256 sha512 and whirlpool. I downloaded 8G file via s_server from 1.0.1 snapshot 20111213 - works fine. Seems problem in speed' itself, or, as Andy mentioned - in time calculation. I merely *implied* that I can *imagine* that interval estimates being problematic in virtual machine, which might explain the phenomena. But the problem occurs on physical machines you say... It's very strange that some algorithms are [more] affected... Anyway, on Cygwin speed.c relies on SIGALRM mechanism, and the thing about it is that there is no native SIGALRM in Win32 (or any asynchronous signals in Unix sense) and it has to be *simulated* by Cygwin dll somehow. I won't be surprised if it turns out that this is where it gets special... Can you test following? Open apps/speed.c in text editor, locate second occurrence of _WIN32 and modify it as #if defined(_WIN32) || defined(__CYGWIN__) Idea is to make it use native Win32 mechanism. Compiler might be complaining about some small things, use your judgment to ignore warnings or to make it compile. __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #2657] Win32: fail to compile - 1.0.1 snapshot 20111211
VisualStudio 2010 perl Configure VC-WIN32 ms\do_ms.bat nmake -f ms\nt.mak .. ml /nologo /Cp /coff /c /Cx /Zi /Fotmp32\vpaes-x86.obj tmp32\vpaes-x86.asm Assembling: tmp32\vpaes-x86.asm tmp32\vpaes-x86.asm(491) : error A2070:invalid instruction operands tmp32\vpaes-x86.asm(527) : error A2070:invalid instruction operands tmp32\vpaes-x86.asm(545) : error A2070:invalid instruction operands tmp32\vpaes-x86.asm(572) : error A2070:invalid instruction operands tmp32\vpaes-x86.asm(616) : error A2070:invalid instruction operands NMAKE : fatal error U1077: 'C:\Program Files (x86)\Microsoft Visual Studio 10.0\VC\BIN\ml.EXE' : return code '0x1' Verify http://cvs.openssl.org/chngview?cn=21845. ml Microsoft (R) Macro Assembler Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. Microsoft Assembler gets *very* limited testing and the official standpoint is to favor nasm. In other words in case of doubt, switch to nasm. __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #2655] speed sha1 hang up - 1.0.1 snapshot 20111211 - Cygwin
Compiler might be complaining about some small things, use your judgment to ignore warnings or to make it compile. It does complain! :-) Attached patch fix the problem on cygwin. Back-ported to 1.0.0e was not break native Win32 (32 bit, VS10) compilation. spped_cygwin.patch Description: Binary data
[openssl.org #1794] [PATCH] SRP in OpenSSL 0.9.9
[peter.sylves...@edelweb.fr - Sun Dec 11 17:51:10 2011]: Enclosed two patches for head and stable to remove unnecessary code for srp and to add some comments to s_client. Applied. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #2655] speed sha1 hang up - 1.0.1 snapshot 20111211 - Cygwin
Compiler might be complaining about some small things, use your judgment to ignore warnings or to make it compile. It does complain! :-) Attached patch fix the problem on cygwin. Does it mean that you can in fact confirm that modified speed.c runs without hanging? I write hanging in quotes, because I wouldn't qualify it as such, because arguably it didn't do anything wrong. BTW, do you get same KBps values? __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #2657] Win32: fail to compile - 1.0.1 snapshot 20111211
Verify http://cvs.openssl.org/chngview?cn=21845. This patch helps! Thanks a lot! ml Microsoft (R) Macro Assembler Version 10.00.30319.01 Copyright (C) Microsoft Corporation. All rights reserved. Microsoft Assembler gets *very* limited testing and the official standpoint is to favor nasm. In other words in case of doubt, switch to nasm. Eh... Missed string in INSTALL.W32: Note that NASM is now the only supported assembler. :-) __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
Re: [openssl.org #2655] speed sha1 hang up - 1.0.1 snapshot 20111211 - Cygwin
It does complain! :-) Attached patch fix the problem on cygwin. Does it mean that you can in fact confirm that modified speed.c runs without hanging? Yes, modified speed.c, being compiled in the same Cygwin environment as before, runs without hanging for all hashes. Interesting, why we do not have such effect fo ciphers and for three selected hashes BTW, do you get same KBps values? Before patch: The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes256 bytes 1024 bytes 8192 bytes sha256 32264.54k75889.08k 133579.66k 166999.63k 177915.57k sha512 17319.36k69456.32k 103750.87k 144978.57k 166290.93k whirlpool22616.29k51999.79k91632.37k 108593.83k99194.67k rc4 423843.86k 533050.06k 558939.38k 597673.15k 604000.56k idea cbc 64826.69k65397.38k67318.14k66839.71k66455.04k aes-128 cbc 95172.64k 107472.19k 110012.39k 176664.53k 177304.57k aes-256 cbc 69245.45k77572.27k79714.56k 128283.83k 128298.72k After the patch: The 'numbers' are in 1000s of bytes per second processed. type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes sha256 32567.32k76673.55k 130986.27k 162825.57k 178479.48k sha512 17374.95k70081.18k 105646.81k 143291.62k 164904.29k whirlpool 22472.70k52594.12k91494.43k 109679.24k 100349.95k rc4 435291.94k 548119.26k 579422.27k 597697.81k 608022.70k idea cbc63872.42k66033.29k66642.98k68983.62k 67100.26k aes-128 cbc 96134.45k 106319.68k 110688.68k 178169.51k 179018.97k aes-256 cbc 69849.36k79412.17k80094.75k 127889.70k 130016.22k __ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
