Re: elog() patch

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: elog() patch
Дата
Msg-id 11871.1015196028@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: elog() patch  (Bruce Momjian <pgman@candle.pha.pa.us>)
Ответы Re: elog() patch  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: elog() patch  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: elog() patch  (Bruce Momjian <pgman@candle.pha.pa.us>)
Список pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: elog() patch
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: elog() patch