Re: [openssl-users] output from: dh, dhparam, pkeyparam

2016-08-10 Thread Benjamin Kaduk
On 08/10/2016 11:00 AM, Jakob Bohm wrote: > On 08/08/2016 16:51, Benjamin Kaduk wrote: >> What Rich said, and also note that it's perfectly valid usage of the >> PEM routines to read one type from a BIO and then go on to read >> another (potentially different) type from the same BIO, as would >>

Re: [openssl-users] output from: dh, dhparam, pkeyparam

2016-08-10 Thread Jakob Bohm
On 08/08/2016 16:51, Benjamin Kaduk wrote: What Rich said, and also note that it's perfectly valid usage of the PEM routines to read one type from a BIO and then go on to read another (potentially different) type from the same BIO, as would happen if they were in the same file concatenated

Re: [openssl-users] output from: dh, dhparam, pkeyparam

2016-08-08 Thread Benjamin Kaduk
What Rich said, and also note that it's perfectly valid usage of the PEM routines to read one type from a BIO and then go on to read another (potentially different) type from the same BIO, as would happen if they were in the same file concatenated after each other. So, attempting to peek and see

Re: [openssl-users] output from: dh, dhparam, pkeyparam

2016-08-06 Thread Salz, Rich
OpenSSL behavior is pretty consistent, when reading a PEM file, everything before the first PEM marker (of the right type!) is ignored. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

[openssl-users] output from: dh, dhparam, pkeyparam

2016-08-06 Thread Johann v . Preußen
since 0.9.6 or before, five (5) example PEM files have been included in the 'crypto/dh' directory of the pkg. these represent bit-sizes from 192 to 4096. certainly 192-/512-/1024-bits are hardly applicable today and that leaves the 2048-/4096-bit files subject to current interest. at that, i am