From 0058b766b91f08b34dcef3c7bb55b216099f3f66 Mon Sep 17 00:00:00 2001 From: Garrett D'Amore Date: Sat, 9 Nov 2024 15:24:43 -0800 Subject: TLS configuration changed to use discret _set_tls and _get_tls functions. This is simpler, and more reliable than using socket options. --- docs/ref/migrate/nng1.md | 17 ++++++++++++----- 1 file changed, 12 insertions(+), 5 deletions(-) (limited to 'docs/ref/migrate') diff --git a/docs/ref/migrate/nng1.md b/docs/ref/migrate/nng1.md index d98b79f0..7a6698d0 100644 --- a/docs/ref/migrate/nng1.md +++ b/docs/ref/migrate/nng1.md @@ -33,14 +33,21 @@ The `NNG_OPT_WSS_REQUEST_HEADERS` and `NNG_OPT_WSS_RESPONSE_HEADERS` aliases for Just convert any use of them to `NNG_OPT_WS_REQUEST_HEADERS` or `NNG_OPT_WS_RESPONSE_HEADERS` as appropriate. -## TLS Options +## TLS Configuration -The support for configuring TLS via `NNG_TLS_AUTH_MODE`, `NNG_OPT_TLS_CA_FILE`, `NNG_OPT_TLS_SERVER_NAME`, -and similar has been removed. Instead configuration must be performed by allocating +The support for configuring TLS via `NNG_OPT_TLS_CONFIG`, `NNG_TLS_AUTH_MODE`, `NNG_OPT_TLS_CA_FILE`, +`NNG_OPT_TLS_SERVER_NAME`, and similar has been removed. + +Instead configuration must be performed by allocating a `nng_tls_config` object, and then setting fields on it using the appropriate functions, -after which it may be configured on a listener or dialer using the `NNG_OPT_TLS_CONFIG` option. +after which it may be configured on a listener or dialer using the [`nng_listener_set_tls`] +or [`nng_dialer_set_tls`] functions. + +Likewise, when using the streams API, use the [`nng_stream_listener_set_tls`] or +[`nng_stream_dialer_set_tls`] functions. -Note that TLS configuration is now available in ``, rather than the supplemental header. +Note that the declarations needed for TLS configuration are now available in ``, +rather than the supplemental header. ## Option Functions -- cgit v1.2.3-70-g09d2