On 04/10/2017 08:42 AM, Michael Paquier wrote:
As there have been some conflicts because of the commit of SASLprep,
here is a rebased set of patches.


I've committed a modified version of the first patch, to change the on-disk format to RFC 5803, as mentioned on the other thread (https://www.postgresql.org/message-id/351ba574-85ea-d9b8-9689-8c928dd09...@iki.fi).

I'll continue reviewing the rest of the patch on Monday, but one glaring issue is that we cannot add an argument to the existing libpq PQencryptPassword() function, because that's part of the public API. It would break all applications that use PQencryptPassword().

What we need to do is to add a new function. What should we call that? We don't have a tradition of using "Ex" or such suffix to mark extended versions of existing functions. PQencryptPasswordWithMethod(user, pass, method) ?

- Heikki



--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to