On Tue, Jun 15, 2021 at 03:59:18PM +0200, Daniel Gustafsson wrote: > While in there I added IMO missing items to the glossary and acronyms sections > as well as fixed up markup around OpenSSL. > > This only deals with docs, but if this is deemed interesting then userfacing > messages in the code should use SSL/TLS as well of course.
+ <term><acronym>SNI</acronym></term> + <listitem> + <para> + <link linkend="libpq-connect-sslsni">Server Name Indication</link> + </para> + </listitem> It looks inconsistent to me to point to the libpq documentation to get the details about SNI. Wouldn't is be better to have an item in the glossary that refers to the bits of RFC 6066, and remove the reference of the RPC from the libpq page? - to present a valid (trusted) SSL certificate, while + to present a valid (trusted) <acronym>SSL</acronym>/<acronym>TLS</acronym> certificate, while This style with two acronyms for what we want to be one thing is heavy. Could it be better to just have one single acronym called SSL/TLS that references both parts? Patch 0003, for the <productname> markups with OpenSSL, included one SSL/TLS entry. -- Michael
signature.asc
Description: PGP signature
