| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | rajkumar820999(at)gmail(dot)com |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: ERROR: (host) should be replaced by (hostnogssenc). |
| Date: | 2020-05-24 16:07:04 |
| Message-ID: | 7753.1590336424@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
PG Doc comments form <noreply(at)postgresql(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2020-05-25 05:23:36 | Re: descriptions of pg_stat_user_functions and pg_stat_slru |
| Previous Message | PG Doc comments form | 2020-05-24 12:44:21 | ERROR: (host) should be replaced by (hostnogssenc). |