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 f
On Wed, Dec 30, 2020 at 07:05:47AM +, Jason McIntyre wrote:
> On Wed, Dec 30, 2020 at 02:02:44AM +0100, Klemens Nanni wrote:
> > Manuals like httpd.conf(5) refer to tls_config_parse_protocols(3) the
> > list of supported protocols.
> >
> > Sentences with inlined elements are generally harder t
On Wed, Dec 30, 2020 at 02:02:44AM +0100, Klemens Nanni wrote:
> Manuals like httpd.conf(5) refer to tls_config_parse_protocols(3) the
> list of supported protocols.
>
> Sentences with inlined elements are generally harder to read, especially
> in such pages and/or when they contain comments.
>
>
On Wed, Dec 30, 2020 at 02:09:46AM +0100, Klemens Nanni wrote:
> On Wed, Dec 30, 2020 at 02:02:44AM +0100, Klemens Nanni wrote:
> >default (alias for "secure")
> >legacy (alias for "all")
> without double quotes
>
First time poster, so, Hi!
Been browsing around this TLS topic, cip
On Wed, Dec 30, 2020 at 02:02:44AM +0100, Klemens Nanni wrote:
> default (alias for "secure")
> legacy (alias for "all")
without double quotes
Manuals like httpd.conf(5) refer to tls_config_parse_protocols(3) the
list of supported protocols.
Sentences with inlined elements are generally harder to read, especially
in such pages and/or when they contain comments.
Convert to a proper list that looks like this when rendered:
The tls_c
