Answering my own question for those searching. Yes, make-ssl-connect@ tracks protocol recommendations. [1] shows that make-ssl-connect@ uses `ssl-make-server-context' with default arguments, meaning an `auto' protocol. The server context docs point to client context docs for the meaning of `'auto'. Quote: "Automatically negotiates the protocol version from those that this library considers sufficiently secure—currently TLS versions 1.0 and higher, but subject to change."
[1]: https://github.com/racket/web-server/blob/ba1b1cf5c49a589f7f4baaa4100db917ed9e1611/web-server-lib/web-server/web-server.rkt#L74 ~slg ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Thursday, December 10, 2020 7:47 PM, Sage Gerard <s...@sagegerard.com> wrote: > I've seen articles say "SSL" when they mean "TLS". When I read the docs for > make-ssl-connect@, it does not clarify what algorithm backs use of HTTPS. > Only that OpenSSL is used. > > Does make-ssl-connect@ track current recommendations like TLS 1.2 or 1.3, or > is it fixed to some version of SSL? > > ~slg -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-users/vxXP0HqAp6LwIb9rfxWNqCSwQCvuqAfyCcIWWB2Up0uuce7hDq-oM3zq8Uno5vkjn06i8oU0MxstBrJlEZUsnnnICb6LDbZ-x6wPh98Bv2I%3D%40sagegerard.com.
