Re: Successor of MD5 authentication, let's use SCRAM - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Successor of MD5 authentication, let's use SCRAM
Date
Msg-id CA+TgmoZ4R_-4qywbYbbDJGE5LjkizyYCg-VGoyCBBTu8t8L=RA@mail.gmail.com
Whole thread Raw
In response to Re: Successor of MD5 authentication, let's use SCRAM  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Successor of MD5 authentication, let's use SCRAM
List pgsql-hackers
On Thu, Sep 12, 2013 at 11:33 AM, Magnus Hagander <magnus@hagander.net> wrote:
> Well, undocumented and OpenSSL tend to go hand in hand a lot. Or,
> well, it might be documented, but not in a useful way. I wouldn't
> count on it.

The OpenSSL code is some of the worst-formatted spaghetti code I've
ever seen, and the reason I know that is because whenever I try to do
anything with OpenSSL I generally end up having to read it, precisely
because, as you say, the documentation is extremely incomplete.  I
hate to be critical of other projects, but everything I've ever done
with OpenSSL has been difficult, and I really think we should try to
get less dependent on it rather than more.

> I fear starting to use that is going to make it even harder to break
> out from our openssl dependency, which people do complain about at
> least semi-regularly.

+1.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers
Next
From: Robert Haas
Date:
Subject: Re: Possible memory leak with SQL function?