Re: Successor of MD5 authentication, let's use SCRAM

From: Will Crawford <billcrawford1970(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Daniel Farina <daniel(at)heroku(dot)com>
Subject: Re: Successor of MD5 authentication, let's use SCRAM
Date: 2012-10-15 11:21:49
Message-ID: CAJDxst6+sJvdot-MD=vX5jy18dkCVDCm9csQgjgpydteOMhb8w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 14 October 2012 22:17, Daniel Farina <daniel(at)heroku(dot)com> wrote:

> The problem there is that it's a pain to get signed certs in, say, a
> test environment, so "don't check certs" will make its way into the
> default configuration, and now you have all pain and no gain.

This is precisely the issue that Debian deals with in providing the
"default Snake Oil" certificate; software development teams -
especially small shops with one or two developers - don't want to
spend time learning about CAs and creating their own, etc, and often
their managers would see this as wasted time for setting up
development environments and staging systems. Not saying they're
right, of course; but it can be an uphill struggle, and as long as you
get a real certificate for your production environment, it's hard to
see what harm this (providing the "snake oil" certificate) actually
causes.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message lst_hoe02 2012-10-15 11:30:09 Re: WebSphere Application Server support for postgres
Previous Message Pavel Stehule 2012-10-15 10:48:53 Re: proposal - assign result of query to psql variable