@ -2182,6 +2182,7 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433
<indexterm zone="ssl-tcp">
<indexterm zone="ssl-tcp">
<primary>SSL</primary>
<primary>SSL</primary>
<secondary>TLS</secondary>
</indexterm>
</indexterm>
<para>
<para>
@ -2193,13 +2194,25 @@ pg_dumpall -p 5432 | psql -d postgres -p 5433
enabled at build time (see <xref linkend="installation"/>).
enabled at build time (see <xref linkend="installation"/>).
</para>
</para>
<para>
The terms <acronym>SSL</acronym> and <acronym>TLS</acronym> are often used
interchangeably to mean a secure encrypted connection using a
<acronym>TLS</acronym> protocol. <acronym>SSL</acronym> protocols are the
precursors to <acronym>TLS</acronym> protocols, and the term
<acronym>SSL</acronym> is still used for encrypted connections even though
<acronym>SSL</acronym> protocols are no longer supported.
<acronym>SSL</acronym> is used interchangeably with <acronym>TLS</acronym>
in <productname>PostgreSQL</productname>.
</para>
<sect2 id="ssl-setup">
<sect2 id="ssl-setup">
<title>Basic Setup</title>
<title>Basic Setup</title>
<para>
<para>
With <acronym>SSL</acronym> support compiled in, the
With <acronym>SSL</acronym> support compiled in, the
<productname>PostgreSQL</productname> server can be started with
<productname>PostgreSQL</productname> server can be started with
<acronym>SSL</acronym> enabled by setting the parameter
support for encrypted connections using <acronym>TLS</acronym> protocols
enabled by by setting the parameter
<xref linkend="guc-ssl"/> to <literal>on</literal> in
<xref linkend="guc-ssl"/> to <literal>on</literal> in
<filename>postgresql.conf</filename>. The server will listen for both normal
<filename>postgresql.conf</filename>. The server will listen for both normal
and <acronym>SSL</acronym> connections on the same TCP port, and will negotiate
and <acronym>SSL</acronym> connections on the same TCP port, and will negotiate