On Wed, Dec 30, 2020 at 08:30:38AM +0100, Theo Buehler wrote: > While I have no objection to doing something along these lines, I dislike > how "all" is singled out in this new list. It's really not recommended. > > I would just keep the order as it was (I see no issue with mentioning > aliases first) or use strict alphabetical order of all keywords. The > newly introduced order is not obvious. Sure, new diff merely turning the sentence into a list.
OK? Index: ./lib/libtls/man/tls_config_set_protocols.3 =================================================================== RCS file: /cvs/src/lib/libtls/man/tls_config_set_protocols.3,v retrieving revision 1.8 diff -u -p -r1.8 tls_config_set_protocols.3 --- ./lib/libtls/man/tls_config_set_protocols.3 22 Jan 2020 06:46:34 -0000 1.8 +++ ./lib/libtls/man/tls_config_set_protocols.3 30 Dec 2020 13:23:02 -0000 @@ -99,9 +99,19 @@ This value can then be passed to the .Fn tls_config_set_protocols function. The protocol string is a comma or colon separated list of keywords. -Valid keywords are tlsv1.0, tlsv1.1, tlsv1.2, tlsv1.3, all (all supported -protocols), default (an alias for secure), legacy (an alias for all) and -secure (currently TLSv1.2 and TLSv1.3). +Valid keywords are: +.Pp +.Bl -tag -width "tlsv1.3" -offset indent -compact +.It Dv tlsv1.0 +.It Dv tlsv1.1 +.It Dv tlsv1.2 +.It Dv tlsv1.3 +.It Dv all Pq all supported protocols +.It Dv default Pq an alias for secure +.It Dv legacy Pq an alias for all +.It Dv secure Pq currently TLSv1.2 and TLSv1.3 +.El +.Pp If a value has a negative prefix (in the form of a leading exclamation mark) then it is removed from the list of available protocols, rather than being added to it.
