[openssl-users] SSL_CTX_set_cert_verify_callback and certificate access

2019-01-09 Thread Corey Minyard
I'm working on an application using openssl, and I would like to set some things up for verification based upon information in the certificate.  Unfortunately, from what I can tell, there is no way to do this.  (Maybe it's not a good idea.  Not sure.) What I would like to do is pull out some

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

2019-01-09 Thread Daniel Kahn Gillmor
On Wed 2019-01-09 04:16:05 +, Jordan Brown wrote: > On 1/8/2019 7:44 PM, Viktor Dukhovni wrote: >> You could just provide a free-form emergency string parameter that >> users are advised to not change unless some major advance makes it >> necessary. At that time, advice can be published as to

Re: [openssl-users] possible C bugs in ecp_nistp521

2019-01-09 Thread Billy Brumley
> I would expect that correct results would be provided for all valid > inputs (including those inputs that are not otherwise constrained). > As such, I would class this as a bug in OpenSSL. These functions are not part of the public OpenSSL API so that's just not how it works. There is a ton of

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

2019-01-09 Thread Jordan Brown
On 1/8/2019 8:21 PM, Viktor Dukhovni wrote: > How do you plan to offer a built-in menu of algorithms that have not > yet been added to OpenSSL? I'm a bit confused as to why we would need to - if the underlying OpenSSL doesn't support a particular algorithm, then there's no need to disable it.