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-use

Re: [openssl-users] Cygwin untar of 1.0.1n gives "tar: A lone zero block at 46120"

avery.a.tara...@securityengineer.pro wrote: >> Was the md5 hash of the archive matching the one on openssl >> website? Yes. It matches. $ tar zxf openssl-1.0.1n.tar.gz tar: A lone zero block at 46120 ~ $ md5sum openssl-1.0.1n.tar.gz 139568bd5a56fa49b72a290d37113f30 *openssl-1.0.1n.tar.gz ~ $

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" wrote: > It seems to build fine, though. > > I downloaded it via different means (directly to a Windows > machine and > on CentOS 6.

[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-user

[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. Therefo

[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 p

[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

[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

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 thin

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 relea

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 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 -outf

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