On Thu, Apr 29, 2021 at 5:06 PM Stephen Frost wrote:
>
> Greetings,
>
> * Magnus Hagander (mag...@hagander.net) wrote:
> > On Thu, Apr 29, 2021 at 7:08 AM Peter Eisentraut
> > wrote:
> > > On 28.04.21 16:09, Alvaro Herrera wrote:
> > > > Looking at it now, I wonder how well do the "hostno" option
On Wed, Apr 28, 2021 at 07:51:43AM +0200, Peter Eisentraut wrote:
> I propose the attached patch to shake up the wording in the connection type
> section of pg_hba.conf.sample a bit. After the hostgssenc part was added
> on, the whole thing became a bit wordy, and it's also a bit inaccurate for
>
Greetings,
* Magnus Hagander (mag...@hagander.net) wrote:
> On Thu, Apr 29, 2021 at 7:08 AM Peter Eisentraut
> wrote:
> > On 28.04.21 16:09, Alvaro Herrera wrote:
> > > Looking at it now, I wonder how well do the "hostno" options work. If I
> > > say "hostnogssenc", is an SSL-encrypted socket go
On Thu, Apr 29, 2021 at 7:08 AM Peter Eisentraut
wrote:
>
> On 28.04.21 16:09, Alvaro Herrera wrote:
> > Looking at it now, I wonder how well do the "hostno" options work. If I
> > say "hostnogssenc", is an SSL-encrypted socket good? If I say
> > "hostnossl", is a GSS-encrypted socket good? If
On 28.04.21 16:09, Alvaro Herrera wrote:
Looking at it now, I wonder how well do the "hostno" options work. If I
say "hostnogssenc", is an SSL-encrypted socket good? If I say
"hostnossl", is a GSS-encrypted socket good? If so, how does that make
sense?
I think for example if you want to enfo
On 28.04.21 16:20, Tom Lane wrote:
Another thought is to switch the phrase order:
+# - "local" is a Unix-domain socket
+# - "host" is a TCP/IP socket (encrypted or not)
+# - "hostssl" is a TCP/IP socket that is SSL-encrypted
+# - "hostnossl" is a TCP/IP socket that is not SSL-encrypted
+# - "hos
Alvaro Herrera writes:
> Looking at it now, I wonder how well do the "hostno" options work. If I
> say "hostnogssenc", is an SSL-encrypted socket good? If I say
> "hostnossl", is a GSS-encrypted socket good? If so, how does that make
> sense?
Kind of off-topic for this thread, but I wonder if
Peter Eisentraut writes:
> I propose the attached patch to shake up the wording in the connection
> type section of pg_hba.conf.sample a bit. After the hostgssenc part was
> added on, the whole thing became a bit wordy, and it's also a bit
> inaccurate for example in that the current wording f
On 2021-Apr-28, Peter Eisentraut wrote:
> I propose the attached patch to shake up the wording in the connection type
> section of pg_hba.conf.sample a bit. After the hostgssenc part was added
> on, the whole thing became a bit wordy, and it's also a bit inaccurate for
> example in that the curre
On Wed, 2021-04-28 at 07:51 +0200, Peter Eisentraut wrote:
> I propose the attached patch to shake up the wording in the connection
> type section of pg_hba.conf.sample a bit. After the hostgssenc part was
> added on, the whole thing became a bit wordy, and it's also a bit
> inaccurate for exam
I propose the attached patch to shake up the wording in the connection
type section of pg_hba.conf.sample a bit. After the hostgssenc part was
added on, the whole thing became a bit wordy, and it's also a bit
inaccurate for example in that the current wording for "host" appears to
say that it
11 matches
Mail list logo
