From: Tom Lane <tgl@sss.pgh.pa.us>
To: rajkumar820999@gmail.com
cc: pgsql-docs@lists.postgresql.org
Subject: Re: ERROR: (host) should be replaced by (hostnogssenc).
In-reply-to: <159032426170.7030.13897325525866864814@wrigleys.postgresql.org>
References: <159032426170.7030.13897325525866864814@wrigleys.postgresql.org>
Comments: In-reply-to PG Doc comments form <noreply@postgresql.org>
	message dated "Sun, 24 May 2020 12:44:21 -0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <7751.1590336424.1@sss.pgh.pa.us>
Date: Sun, 24 May 2020 12:07:04 -0400
Message-ID: <7753.1590336424@sss.pgh.pa.us>
Precedence: bulk

PG Doc comments form <noreply@postgresql.org> writes:
> Under the topic "Encrypting Data Across A Network", I think there seems to
> be a documentation error.

> ERROR: (host) should be replaced by (hostnogssenc).

> The pg_hba.conf file allows administrators to specify which hosts can use
> non-encrypted connections (host) and which require GSSAPI-encrypted
> connections (hostgssenc). Also, clients can specify that they connect to
> servers only on GSSAPI-encrypted connections (gssencmode=require).

I think it's correct as it stands.  hostnogssenc would have the semantics
"hosts that MUST use non-encrypted connections".

If that were actually a useful option, maybe it would be worth lengthening
this description to mention all three options ... but it seems OK as-is to
me.

			regards, tom lane