Re: elog() patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: elog() patch
Date: 2002-03-03 22:53:48
Message-ID: 11871.1015196028@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Can you take care of the echo of entered password too,

I'm unconvinced that that's wrong, and will not change it without
more discussion. (1) The reason it was put in was to allow debugging
of "that's the wrong password" mistakes. (2) The postmaster log
inherently contains a great deal of sensitive information, so anyone
who runs with it world-readable has a problem already. (3) The password
is not emitted unless the message level is a lot lower than anyone would
routinely use. (4) If you're using the recommended MD5 encryption
approach, then what's logged is encrypted; it seems no more dangerous
than having encrypted passwords in pg_shadow.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2002-03-03 22:55:36 Re: elog() patch
Previous Message Bruce Momjian 2002-03-03 22:48:11 Re: elog() patch