Re: [GENERAL] Authenticate with hash instead of plaintext password?

2012-12-16 Thread Murray Cumming
On Sun, 2012-12-16 at 17:51 +0100, Peter Bex wrote: > On Sun, Dec 16, 2012 at 05:38:37PM +0100, Murray Cumming wrote: > > On Sun, 2012-12-16 at 17:24 +0100, Peter Bex wrote: > > > What's the use of that? > > [snip] > > > > I would not be storing the p

Re: [GENERAL] Authenticate with hash instead of plaintext password?

2012-12-16 Thread Murray Cumming
On Sun, 2012-12-16 at 17:24 +0100, Peter Bex wrote: > On Sun, Dec 16, 2012 at 04:54:30PM +0100, Murray Cumming wrote: > > libpq lets me open a connection by specifying a password: > > http://www.postgresql.org/docs/9.2/static/libpq-connect.html#LIBPQ-PARAMKEYWORDS > > &g

[GENERAL] Authenticate with hash instead of plaintext password?

2012-12-16 Thread Murray Cumming
libpq lets me open a connection by specifying a password: http://www.postgresql.org/docs/9.2/static/libpq-connect.html#LIBPQ-PARAMKEYWORDS Is there any way to specify a hash of the password when connecting, instead of providing the password itself? My Web UI asks the user for a PostgreSQL userna

[GENERAL] Disable unix-domain sockets?

2012-10-25 Thread Murray Cumming
I'd like to avoid having to specify the unix socket directory when starting local instances of postgres, due to the new restrictions on the characters that can be in its path http://archives.postgresql.org/pgsql-bugs/2012-09/msg00012.php (only partly solved by a recent commit): This needs to be sp