Question about constness of EVP_PKEY* arguments in public API

Hi, I have some piece of software using OpenSSL that works right now on a single thread right now. I am adding a bit more "const" in the code everywhere I can as we want to start using the same code in multithreaded environment, and potentially two threads might sign/verify/encrypt/decrypt usin

Re: TLS 1.3 migration: SSL_set_cipher_list vs SSL_set_ciphersuites and "aliases" of families of cipher like TLSv1.3

> Le 1 avr. 2020 à 15:19, Salz, Rich a écrit : > >> - Do you think any use for supporting some kind of alias for families of >> cipher in SSL_set_ciphersuites, like for example "TLSv1.3" > > Suppose someone finds out that chacha/poly is insecure and the IETF issues a > new RFC that says "TLS

TLS 1.3 migration: SSL_set_cipher_list vs SSL_set_ciphersuites and "aliases" of families of cipher like TLSv1.3

Hi, We are using OpenSSL 1.1.1 for quite some time, and we have been able to migrate over time to the different version of SSL/TLS, up to TLS 1.2 with success. Now we wish to prepare the migration to TLS 1.3. The people used to configure our SSL connection tries to set the cipher list as they