pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Jeff Davis <pgsql@j-davis.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Jeff Janes <jeff.janes@gmail.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: k.yudhveer@gmail.com, pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: BUG #16079: Question Regarding the BUG #16064
Date: Thu, 03 Jun 2021 11:02:56 -0700
Message-ID: <2c52f6c582e2fbcea77caa0ae8d83af261522be7.camel@j-davis.com> (raw)
In-Reply-To: <544464.1608576242@sss.pgh.pa.us>
References: <16079-29e9c038e1463751@postgresql.org>
	<20191028154754.GS6962@tamriel.snowman.net>
	<CA+hUKGJw4Ax25=fcCA+DQD=82v2pKu9VGmkYZO8HeH7+-P2Cxw@mail.gmail.com>
	<CABUevEwMcFmXqPJgOQfnUV8XgKtWqHPiccNHY+mPJ0AfeFz-7Q@mail.gmail.com>
	<20201221005825.GQ16415@tamriel.snowman.net>
	<CAMkU=1w4c6NXiKHx-awVw0EeTqqn-Coy_hJGwYkq9WvbEQ1PAw@mail.gmail.com>
	<543836.1608575492@sss.pgh.pa.us>
	<20201221183511.GI27507@tamriel.snowman.net>
	<544464.1608576242@sss.pgh.pa.us>

On Mon, 2020-12-21 at 13:44 -0500, Tom Lane wrote:
> Hm.  I'm less concerned about that scenario than about somebody
> snooping
> the on-the-wire traffic.  If we're going to invent a connection
> setting
> for this, I'd say that in addition to "ok to send cleartext password"
> and "never ok to send cleartext password", there should be a setting
> for
> "send cleartext password only if connection is encrypted".  Possibly
> that should even be the default.

There was a fair amount of related discussion here:


https://www.postgresql.org/message-id/227015d8417f2b4fef03f8966dbfa5cbcc4f44da.camel%40j-davis.com

My feeling after all of that discussion is that the next step would be
to move to some kind of negotiation between client and server about
which methods are mutually acceptable. Right now, the protocol is
structured around the server driving the authentication process, and
the most the client can do is abort.

> BTW, do we have a client-side setting to insist that passwords not be
> sent in MD5 hashing either?  A person who is paranoid about this
> would
> likely want to disable that code path as well.

channel_binding=require is one way to do it, but it also requires ssl.

Regards,
	Jeff Davis







view thread (18+ messages)  latest in thread

Message-ID: <2c52f6c582e2fbcea77caa0ae8d83af261522be7.camel@j-davis.com>
Permalink:  ../2c52f6c582e2fbcea77caa0ae8d83af261522be7.camel@j-davis.com/
Also on:    postgresql.org/message-id/2c52f6c582e2fbcea77caa0ae8d83af261522be7.camel@j-davis.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: pgsql@j-davis.com, tgl@sss.pgh.pa.us, sfrost@snowman.net, jeff.janes@gmail.com, magnus@hagander.net, thomas.munro@gmail.com, pgsql-hackers@postgresql.org
  Subject: Re: BUG #16079: Question Regarding the BUG #16064
  In-Reply-To: <2c52f6c582e2fbcea77caa0ae8d83af261522be7.camel@j-davis.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox