[gnutls-devel] GnuTLS | priority: support allowlisting in configuration file (!1427)

Read-only notification of GnuTLS library development activities gnutls-devel at lists.gnutls.org
Mon Nov 29 12:14:24 CET 2021

Alexander Sosedkin started a new discussion on doc/cha-config.texi: https://gitlab.com/gnutls/gnutls/-/merge_requests/1427#note_746204123

>  The allowlisting mode can be enabled by adding @code{override-mode =
>  allowlist} in the @code{[global]} section.
> -When the allowlisting mode is in effect, it is also possible for the applications to modify the setting through the API.
> +The following functions allow the applications to modify the setting.
>  @showfuncE{gnutls_ecc_curve_set_enabled,gnutls_sign_set_secure,gnutls_sign_set_secure_for_certs,gnutls_digest_set_secure,gnutls_protocol_set_enabled}
> +When the allowlisting mode is in effect, a @code{@@SYSTEM} priority
> +string is automatically constructed from the options in the
> + at code{[overrides]} section.  For this reason, the above functions
> +should be called before the @cde{@@SYSTEM} priority is used.

CI found a typo:

  MAKEINFO gnutls.info
./cha-config.texi:133: unknown command `cde'
./cha-config.texi:133: misplaced {
./cha-config.texi:133: misplaced }

Reply to this email directly or view it on GitLab: https://gitlab.com/gnutls/gnutls/-/merge_requests/1427#note_746204123
You're receiving this email because of your account on gitlab.com.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.gnupg.org/pipermail/gnutls-devel/attachments/20211129/5f192979/attachment.html>

More information about the Gnutls-devel mailing list