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

From Greg Stark
Subject Re: Successor of MD5 authentication, let's use SCRAM
Date
Msg-id CAM-w4HOP8Wv8WEP5vYHR13c=Z95w_i1k136i=Na8DjvNRd_BhQ@mail.gmail.com
Whole thread Raw
In response to Re: Successor of MD5 authentication, let's use SCRAM  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On Fri, Sep 13, 2013 at 5:31 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> 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 have nothing exciting to add but I happened to be reading this old
thread and thought the above post was relevant again these days.


-- 
greg



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: quiet inline configure check misses a step for clang
Next
From: Tom Lane
Date:
Subject: Re: Why do we allow indexes to contain the same column more than once?