Re: [openssl-users] The default cipher of executable 'openssl'
Hi Dave,
Thanks for your comments.
I am not really familiar with OpenSSL, so some parts of my descriptions may
not be not very clear.
Right, I am talking about s_server subcommand. You mentioned that there is
no change in this area. However I can easily show something is change using
s_server subcommand. I am using original OpenSSL code to build my 'openssl',
to this change is not from me.
1) 1.0.1l
./apps/openssl s_server -ssl3 -cert certdb/ssl_server.pem -WWW -CAfile
certdb/cafile.pem
Using default temp DH parameters
Using default temp ECDH parameters
ACCEPT
2) 1.0.2
./apps/openssl s_server -ssl3 -cert certdb/ssl_server.pem -WWW -CAfile
certdb/cafile.pem
Using default temp DH parameters
ACCEPT
Note that, in 1.0.2, openssl doesn't print out 'Using default temp ECDH
parameters'.
I checked related code in s_server.c and ssl_conf.c, There are some updates.
Some related code is moved from s_server.c to ssl_conf.c. However I haven't
found the root cause of this change.
I encountered a similar issue when upgrading from OpenSSL 1.0.1l to 1.0.1m.
I paste my analysis and fix below. After I applied my fix, the issue
disappeared.
1) Analysis
File s_server.c was updated in OpenSSL 1.0.1m. Variable 'no_ecdhe' was
uninitialized after the update. This causes the condition of the if
statement (if (!no_ecdheon) {...}) on line 1682 not to be true. Then
ECDHE-RSA-AES256-SHA is not the default temp ECDH parameters of 'openssl
s_server' any more.
2) Fix
273 diff -wruN openssl-1.0.1m.original/apps/s_server.c
openssl-1.0.1m.working/apps/s_server.c
274 --- openssl-1.0.1m.original/apps/s_server.c 2015-03-19
06:37:10.0 -0700
275 +++ openssl-1.0.1m.working/apps/s_server.c 2015-05-25
01:46:35.0 -0700
276 @@ -998,7 +998,7 @@
277int off = 0;
278int no_tmp_rsa = 0, no_dhe = 0, nocert = 0;
279#ifndef OPENSSL_NO_ECDH
280 -int no_ecdhe;
281 +int no_ecdhe = 0;
282#endif
283int state = 0;
284const SSL_METHOD *meth = NULL;
I noticed that the issue in 1.0.2 is not the same as the issue in 1.0.1m.
The issue started to appear in 1.0.2 rather than 1.0.2a.
Thanks,
Aaron
--
View this message in context:
http://openssl.6102.n7.nabble.com/The-behavior-change-of-command-line-utility-openssl-tp58557p58631.html
Sent from the OpenSSL - User mailing list archive at Nabble.com.
___
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] The default cipher of executable 'openssl'
Thanks so much, Viktor. Hence, this is an expected behavior change. In this case I will update my application. Aaron. -- View this message in context: http://openssl.6102.n7.nabble.com/The-behavior-change-of-command-line-utility-openssl-tp58557p58637.html Sent from the OpenSSL - User mailing list archive at Nabble.com. ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] The default cipher of executable 'openssl'
On Thu, Jun 11, 2015 at 11:19:17PM -0700, Aaron wrote: Right, I am talking about s_server subcommand. You mentioned that there is no change in this area. However I can easily show something is change using s_server subcommand. I am using original OpenSSL code to build my 'openssl', to this change is not from me. 1) 1.0.1l ./apps/openssl s_server -ssl3 -cert certdb/ssl_server.pem -WWW -CAfile certdb/cafile.pem Using default temp DH parameters Using default temp ECDH parameters ACCEPT With SSL 3.0, no extension support, thus no supported curves extension, thus ideally no EDCHE support. If ECDHE happened anyway with earlier releases, that was a bug that is perhaps now fixed. 2) 1.0.2 ./apps/openssl s_server -ssl3 -cert certdb/ssl_server.pem -WWW -CAfile certdb/cafile.pem Using default temp DH parameters ACCEPT Note that, in 1.0.2, openssl doesn't print out 'Using default temp ECDH parameters'. To get ECDHE support, use TLSv1.0 or later. -- Viktor. ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Not getting RSA keyword for a key in fips mode
Thanks Steve for the quick reply. On Thu, Jun 11, 2015 at 7:27 PM, Dr. Stephen Henson st...@openssl.org wrote: On Thu, Jun 11, 2015, Gayathri Manoj wrote: Hi All, I am trying to create a pem format key for my existing key by using the below command. openssl rsa -in my_rsa_key -outform PEM -out my_res_newkey_pem The new key format is -BEGIN PRIVATE KEY-. But I am expecting -BEGIN RSA PRIVATE KEY- In nonFIPS mode i am getting -BEGIN RSA PRIVATE KEY- as expected. My openssl version is OpenSSL 0.9.8zf-fips. Please let me know how can I generate the new key in BEGIN RSA PRIVATE KEY format. You can't because the format isn't allowed in FIPS mode because it uses MD5 for key derivation. Steve. -- Dr Stephen N. Henson. OpenSSL project core developer. Commercial tech support now available see: http://www.openssl.org ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Cygwin untar of 1.0.1n gives tar: A lone zero block at 46120
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Was the md5 hash of the archive matching the one on openssl website? On Fri, Jun 12 at 06:49 PM (UTC), Kevin Layer la...@franz.com wrote: It seems to build fine, though. I downloaded it via different means (directly to a Windows machine and on CentOS 6.6) and it did it on all copies. Just curious if anyone else had the issue. I'm running Cygwin 1.7.35 on Server 2008 R2. ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users -BEGIN PGP SIGNATURE- Charset: UTF8 Note: This signature can be verified at https://www.hushtools.com/verify Version: Hush 3.0 wsBcBAEBAgAGBQJVezykAAoJEFXbLWdqxjhau0AIAJm7ouwddcTJixc7U+eqnvZgdLcR etN9VhONFRN0zU6hmdanMUb8WAmHeujUpu+yhvolO9bP21pE7xDtdRRbyrwAwl2vYvzU 68klgLaRE2LeoPy/9iSLnr9Y1i2yXuiVaYC4TtPR4g3vbVryiLjPuVAOJejUKHq9oet1 i9DZyNZvs2X+0Qk65vjLsnN1QS8n22YbsORDV76scJ2XoGjura+Y6gKJ3spJgu8+kU3Z sQTLbnD4zJEniNvjpAbboLRBOFtrj2QnY6N4NdAY4zllwR44He93X+7w3GAEPcrShlnT eD6MnNeG0vkblVpQOEw3APGh0iK5yfl9eNaQUD/ijH0= =XZl9 -END PGP SIGNATURE- ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] Cygwin untar of 1.0.1n gives tar: A lone zero block at 46120
$ tar zxf openssl-1.0.1n.tar.gz tar: A lone zero block at 46120 Perhaps this? http://askubuntu.com/questions/169223/tar-a-lone-zero-block-at-343398 ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
[openssl-users] Cygwin untar of 1.0.1n gives tar: A lone zero block at 46120
It seems to build fine, though. I downloaded it via different means (directly to a Windows machine and on CentOS 6.6) and it did it on all copies. Just curious if anyone else had the issue. I'm running Cygwin 1.7.35 on Server 2008 R2. ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
[openssl-users] [openssl-announce] Forthcoming releases
Forthcoming OpenSSL releases The OpenSSL project team would like to announce the forthcoming release of OpenSSL versions 1.0.2c, 1.0.1o. These releases will be made available on Friday 12th June. They will fix two specific issues: 1) an HMAC ABI incompatibility with previous releases, and 2) make it possible to accept a zero length extension block in a ClientHello. These are not security releases. Yours The OpenSSL Project Team pgptVICsplf5y.pgp Description: PGP signature ___ openssl-announce mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-announce ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
[openssl-users] [openssl-announce] Clarification on forthcoming releases
Clarification on the forthcoming OpenSSL releases = To clarify, the mentioned HMAC ABI incompatibility occurred in recently released versions 1.0.2b and 1.0.1n which are security fixes but which may cause other problems due to the ABI issue. Therefore, the forthcoming releases should be used in preference to 1.0.2b and 1.0.1n. Yours The OpenSSL Project Team pgpCtpQrPHgxa.pgp Description: PGP signature ___ openssl-announce mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-announce ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] OpenSSL version 1.0.2b released
On 11/06/2015 16:47, OpenSSL wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OpenSSL version 1.0.2b released === OpenSSL - The Open Source toolkit for SSL/TLS http://www.openssl.org/ The OpenSSL project team is pleased to announce the release of version 1.0.2b of our open source toolkit for SSL/TLS. For details of changes and known issues see the release notes at: http://www.openssl.org/news/openssl-1.0.2-notes.html OpenSSL 1.0.2b is available for download via HTTP and FTP from the following master locations (you can find the various FTP mirrors under http://www.openssl.org/source/mirror.html): * http://www.openssl.org/source/ * ftp://ftp.openssl.org/source/ The distribution file name is: o openssl-1.0.2b.tar.gz Size: 5281009 MD5 checksum: 7729b259e2dea7d60b32fc3934d6984b SHA1 checksum: 9006e53ca56a14d041e3875320eedfa63d82aba7 The checksums were calculated using the following commands: openssl md5 openssl-1.0.2b.tar.gz openssl sha1 openssl-1.0.2b.tar.gz Yours, The OpenSSL Project Team. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVeZNdAAoJENnE0m0OYESRYscIAKrJik5qyPifnVhWRHVTUXot NYhfl+h+ooHequRyz9ug7Wz3vdUioftuOYlX0eJBBZ+YvskVk27U9tjY+plFnRjq vpdNKfa6bSL9rjztZObupvbCnhYRdDkcJRqLi8HfPb53UlZS/ALIbpDi1FPqIErs Bc7D/toD0nDoQUONLVQw/aSZNWWCaACO09326K2xX/jZGEsQbhCWdlkERfO3RzRW RBN0RnR+k8XBaqy6TRELF1vlYdHe83Dqxg1h3KBTBJ+yOFXvQblPoZO4GnkAyoNA 8EGhbzgWsjg6OIroUbnbbq50avvya/2eDmY+N3gNg5wOrYBNZlWShy91WGZ4378= =rcRW -END PGP SIGNATURE- Note: Why are OpenSSL releases still signed only with MD5 and SHA1? Even the gpg signature of the tarball is SHA1-based. Why isn't there also a detached S/MIME / CMS signature for the tarballs, preferably using a code/object signingcertificate from someone like GlobalSign. i.e. Something that can be verified with the command: old-trusted-openssl smime -verify -inform PEM -in \ openssl-1.0.2b.tar.gz.sig -binary -content \ openssl-1.0.2b.tar.gz -out /dev/null -CAfile \ /etc/ssl/certificates/foo.pem (add option -purpose codesign once implemented by the users old-trusted-openssl). If old-trused-openssl is a recent version, a similar old-trused-openssl cms command can also be used, but verify compatibility with old copies should be maintained for a few years (don't prevent upgrading openssl because the users needs to upgrade openssl). Enjoy Jakob -- Jakob Bohm, CIO, Partner, WiseMo A/S. http://www.wisemo.com Transformervej 29, 2860 Søborg, Denmark. Direct +45 31 13 16 10 This public discussion message is non-binding and may contain errors. WiseMo - Remote Service Management for PCs, Phones and Embedded ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
[openssl-users] OpenSSL version 1.0.1o released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OpenSSL version 1.0.1o released === OpenSSL - The Open Source toolkit for SSL/TLS http://www.openssl.org/ The OpenSSL project team is pleased to announce the release of version 1.0.1o of our open source toolkit for SSL/TLS. For details of changes and known issues see the release notes at: http://www.openssl.org/news/openssl-1.0.1-notes.html OpenSSL 1.0.1o is available for download via HTTP and FTP from the following master locations (you can find the various FTP mirrors under http://www.openssl.org/source/mirror.html): * http://www.openssl.org/source/ * ftp://ftp.openssl.org/source/ The distribution file name is: o openssl-1.0.1o.tar.gz Size: 4546659 MD5 checksum: af1096f500a612e2e2adacb958d7eab1 SHA1 checksum: b003e3382607ef2c6d85b51e4ed7a4c0a76b8d5a The checksums were calculated using the following commands: openssl md5 openssl-1.0.1o.tar.gz openssl sha1 openssl-1.0.1o.tar.gz Yours, The OpenSSL Project Team. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVevjeAAoJENnE0m0OYESRBTYIALl9NdRXPLxB+VZtVFVmOIHq HjC5IMBJCtsNCvUg3dOogSR+ZyrY82jPimxNY1+w5XCOQQ4Ro90Auw9OMoRwRo1y 7Y9+mZkxIrJUdudlNDmfsHw8wE5peThdhZnI9vnTgJSLBKbjqqVsHsxnUJ8dzNsc M2e2qa/poSPapWakfgafRRCblM9C/9zK/++n1m+t2SLHdM1dPanbiOIodnxX7XKp t/6UQzclDAPDpnG74bYPzHTI2rfcruezD8RiB3dNpma9n0uGRjorGEHjn/6PcgFy Rn1vgybhsoXpmQWT9kEQcLeRjgHEwyzxBlmVYnC3SFItlMma3h/bGYniCR89Huo= =WGaf -END PGP SIGNATURE- ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
[openssl-users] OpenSSL version 1.0.2c released
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 OpenSSL version 1.0.2c released === OpenSSL - The Open Source toolkit for SSL/TLS http://www.openssl.org/ The OpenSSL project team is pleased to announce the release of version 1.0.2c of our open source toolkit for SSL/TLS. For details of changes and known issues see the release notes at: http://www.openssl.org/news/openssl-1.0.2-notes.html OpenSSL 1.0.2c is available for download via HTTP and FTP from the following master locations (you can find the various FTP mirrors under http://www.openssl.org/source/mirror.html): * http://www.openssl.org/source/ * ftp://ftp.openssl.org/source/ The distribution file name is: o openssl-1.0.2c.tar.gz Size: 5280670 MD5 checksum: 8c8d81a9ae7005276e486702edbcd4b6 SHA1 checksum: 6e4a5e91159eb32383296c7c83ac0e59b83a0a44 The checksums were calculated using the following commands: openssl md5 openssl-1.0.2c.tar.gz openssl sha1 openssl-1.0.2c.tar.gz Yours, The OpenSSL Project Team. -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQEcBAEBAgAGBQJVevZ0AAoJENnE0m0OYESRAGIIAI+OThnhcwcrZoA3pddNL5+s mVGDd+ZstNkiqLFJSOn2Enh7Hx8xvUwaONvSAGqyiuxgmkyOSmnhc9NeE2LU+knl 8vMqF4hrTWV39JJZkkqqwEv5HRr17IWtzBL3N3/1mygvFmge6SFbGeRPk+XpyP/L 0aEWRzm7g4nq+g4Oa4/HeXsVeEwldMhgHoxbS0R3RHXPOlGb3VjZUDzg+0Nwqt5O q/sncMZAaC2TGauqsAxS19C+7hVEeZdvPKgX+DClf+NMe9+j8gWz1zmD7q5zJSQ8 ZH5+4ifFaVBSn1vuxPK4cLF5j+aUnotmWFkhJ3yZOAt+tYEH95MNB2aP4k2UCgc= =QIqW -END PGP SIGNATURE- ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
Re: [openssl-users] The default cipher of executable 'openssl'
On Fri, Jun 12, 2015 at 01:35:22AM -0700, Aaron wrote: Thanks so much, Viktor. Hence, this is an expected behavior change. In this case I will update my application. Does your test case result in ECDHE being used when you change only the protocol on both ends from ssl3 to tls1? If so, I think this that confirms my hunch. I've not hunted down the specific changes that might have tightened down use of ECDHE in the absense of the relevant extensions (nor even whether the change is in the server or client). So this analysis is disturbingly plausible (an amusing phrase borrowed from another context, too long to explain...). -- Viktor. ___ openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
