Re: [openssl-users] crypto/objects/o_names.c problem with Solaris 10 and strict Oracle Studio 12.6 c99

2019-01-17 Thread Dennis Clarke
On 1/17/19 8:25 PM, Michael Wojcik wrote: From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of Dennis Clarke Sent: Thursday, January 17, 2019 18:23 "crypto/objects/o_names.c", line 114: error: undefined symbol: strcasecmp "crypto/objects/o_names.c", line 114: warning: impr

Re: [openssl-users] in the department of "ain't no perfect"

2019-01-17 Thread Jakob Bohm via openssl-users
On 16/01/2019 21:25, Viktor Dukhovni wrote: On Jan 15, 2019, at 10:29 AM, Eliot Lear wrote: I have an application that requires long-lived signatures, perhaps long past the point where the signer's cert has expired. I'd like a way to extract the signature date from a CMS structure. With all t

Re: [openssl-users] crypto/objects/o_names.c problem with Solaris 10 and strict Oracle Studio 12.6 c99

2019-01-17 Thread Michael Wojcik
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of > Dennis Clarke > Sent: Thursday, January 17, 2019 18:23 > > "crypto/objects/o_names.c", line 114: error: undefined symbol: strcasecmp > "crypto/objects/o_names.c", line 114: warning: improper pointer/integer > combinatio

Re: [openssl-users] is there an API to list all the TLS 1.3 cipher suite names?

2019-01-17 Thread Jordan Brown
On 1/14/2019 4:09 AM, Matt Caswell wrote: > This works more "by accident". There is no ciphersuite alias called > "TLSv1.3", so using it as above results in no ciphersuites matched. > Since the TLSv1.3 ciphersuites are on by default anyway that's all > that you get back. >From what you say, and b

[openssl-users] crypto/objects/o_names.c problem with Solaris 10 and strict Oracle Studio 12.6 c99

2019-01-17 Thread Dennis Clarke
Fairly sure I did not run into all these issues with 1.1.1 on the exact same systems but regardless here we are. I *know* that I tested every one of the 'pre' testing versions and have 1.1.1 running fine just about everywhere. So here goes the long story with ye strict C99 compiler : $ env |

Re: [openssl-users] in the department of "ain't no perfect"

2019-01-17 Thread Hubert Kario
On Thursday, 17 January 2019 18:03:55 CET Eliot Lear wrote: > On 17.01.19 17:29, Hubert Kario wrote: > > alternatively, you can save all the certificates and revocation data, bind > > it to the original signature using a timestamp from a TSA and store that > > (that's necessary if you want to be ab

Re: [openssl-users] Compiling FIPS-cable OpenSSL on Windows Server 2012R2

2019-01-17 Thread Chris Fernando via openssl-users
> On Jan 7, 2019, at 11:52, Chris Fernando via openssl-users > wrote: > >> >> On Jan 7, 2019, at 09:20, Chris Fernando via openssl-users >> wrote: >> >> I perused the list archives for all of 2018 and did not see anything current >> relating to this problem, so if this is a question that ha

Re: [openssl-users] Get peer certificate after handshake failure

2019-01-17 Thread Viktor Dukhovni
On Thu, Jan 17, 2019 at 05:39:39PM +, Steven Winfield wrote: > TL;DR: After a failed handshake, caused by our peer’s certificate failing > verification, what is the correct way to get hold of the peer’s certificate? You can't get it after, but you can get it *during* the handshake, by impleme

Re: [openssl-users] Get peer certificate after handshake failure

2019-01-17 Thread Steven Winfield
Hi all, First time posting here so please be gentle ;-) TL;DR: After a failed handshake, caused by our peer’s certificate failing verification, what is the correct way to get hold of the peer’s certificate? A little more detail: I’d like my server applications to be able to log some details abo

Re: [openssl-users] in the department of "ain't no perfect"

2019-01-17 Thread Eliot Lear
On 17.01.19 17:29, Hubert Kario wrote: > > alternatively, you can save all the certificates and revocation data, bind it > to the original signature using a timestamp from a TSA and store that (that's > necessary if you want to be able to prove to some 3rd party that you received > a correctly

Re: [openssl-users] Question regarding OpenSSL compilations

2019-01-17 Thread Salz, Rich via openssl-users
Look at the tricks openssl has to do in order to properly zeroized memory and avoid having the compiler optimize it away. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] in the department of "ain't no perfect"

2019-01-17 Thread Hubert Kario
On Wednesday, 16 January 2019 21:25:32 CET Viktor Dukhovni wrote: > > On Jan 15, 2019, at 10:29 AM, Eliot Lear wrote: > > > > I have an application that requires long-lived signatures, perhaps long > > past the point where the signer's cert has expired. I'd like a way to > > extract the signatur

Re: [openssl-users] Question regarding OpenSSL compilations

2019-01-17 Thread Matt Caswell
On 17/01/2019 14:21, Petrescu Constantin Cezar wrote: > Dear sirs/madams, > > My name is Costin Cezar Petrescu and I am a student at Royal Holloway. I am > intending to conduct some research regarding compilation errors, tricks to fix > compiler mistakes and their affects over cryptographic libr

[openssl-users] Question regarding OpenSSL compilations

2019-01-17 Thread Petrescu Constantin Cezar
Dear sirs/madams, My name is Costin Cezar Petrescu and I am a student at Royal Holloway. I am intending to conduct some research regarding compilation errors, tricks to fix compiler mistakes and their affects over cryptographic libraries. If it is possible, I would like to find more about OpenSSL