Обсуждение: pgsql: Add an officially exported libpq function to encrypt passwords,

Log Message:
-----------
Add an officially exported libpq function to encrypt passwords, and
modify the previous \password patch to use it instead of depending
on a not-officially-exported function.  Per discussion.

Modified Files:
--------------
    pgsql/doc/src/sgml:
        libpq.sgml (r1.199 -> r1.200)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/libpq.sgml.diff?r1=1.199&r2=1.200)
    pgsql/src/bin/psql:
        command.c (r1.156 -> r1.157)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/command.c.diff?r1=1.156&r2=1.157)
    pgsql/src/bin/scripts:
        createuser.c (r1.24 -> r1.25)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/bin/scripts/createuser.c.diff?r1=1.24&r2=1.25)
    pgsql/src/interfaces/libpq:
        exports.txt (r1.5 -> r1.6)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/exports.txt.diff?r1=1.5&r2=1.6)
        fe-auth.c (r1.108 -> r1.109)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/fe-auth.c.diff?r1=1.108&r2=1.109)
        libpq-fe.h (r1.122 -> r1.123)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/interfaces/libpq/libpq-fe.h.diff?r1=1.122&r2=1.123)

Am Freitag, 23. Dezember 2005 02:16 schrieb Tom Lane:
> Add an officially exported libpq function to encrypt passwords, and
> modify the previous \password patch to use it instead of depending
> on a not-officially-exported function.  Per discussion.

I was working on a more-or-less identical patch (but didn't find an Internet
connection on the train until just now) but called the function
PQencryptPassword, which seems to be more in line with the other function
names.  (We tend to use lower_case_names for internal functions.)  What is
the strategy there?

Peter Eisentraut <peter_e@gmx.net> writes:
> Am Freitag, 23. Dezember 2005 02:16 schrieb Tom Lane:
>> Add an officially exported libpq function to encrypt passwords, and
>> modify the previous \password patch to use it instead of depending
>> on a not-officially-exported function.  Per discussion.

> I was working on a more-or-less identical patch (but didn't find an Internet
> connection on the train until just now) but called the function
> PQencryptPassword, which seems to be more in line with the other function
> names.  (We tend to use lower_case_names for internal functions.)  What is
> the strategy there?

I have no objection to that name if you want to change it.

            regards, tom lane