Does https://docs.rs/boring/latest/boring/ssl/struct.SslContextBuilder.html#method.set_curves work for you?

Hi @cjpatton! I believe SslContextBuilder::set_curves applies the curve list to the SSL_CTX template globally for SSL session objects. However, it doesn't allow setting different curves per connection or per SNI at runtime (which we need).

Since BoringSSL doesn't copy the curve list from the context into the SSL object, we need to set the curves directly on each SSL session to support different configurations for different SNIs.

We're talking about deprecating set_curves in favour of set_curves_list. Does that cause problems for you?

Hi @bwesterb. Are you referring to the [SSL_set1_curves_list](https://www.openssl.org/docs/manmaster/man3/SSL_set1_curves_list.html) onto the SSL session itself?

Ideally, we'd like to use the set_curves method directly, to avoid any colon delimited string parsing overhead upon each new SSL session.

https://github.com/google/boringssl/blob/bf4cf6938a77f1aca83ef529dce96681efd1e6c5/ssl/ssl_lib.cc#L1861

Ideally, we'd like to use the set_curves method directly, to avoid any colon delimited string parsing overhead upon each new SSL session.

Have you timed it? If it's significant, we can work with upstream to allow preparsing.

Thanks for the feedback and review @kornelski!

@kornelski Thank you for the help, happy to see build is passing!