Re: Securing "make check" (CVE-2014-0067)

Поиск
Список
Период
Сортировка
От Bruce Momjian
Тема Re: Securing "make check" (CVE-2014-0067)
Дата
Msg-id 20140305001027.GA28321@momjian.us
обсуждение исходный текст
Ответ на Re: Securing "make check" (CVE-2014-0067)  (Noah Misch <noah@leadboat.com>)
Ответы Re: Securing "make check" (CVE-2014-0067)  (Noah Misch <noah@leadboat.com>)
Список pgsql-hackers
On Sat, Mar  1, 2014 at 01:35:45PM -0500, Noah Misch wrote:
> Having that said, I can appreciate the value of tightening the socket mode for
> a bit of *extra* safety:
> 
> --- a/src/test/regress/pg_regress.c
> +++ b/src/test/regress/pg_regress.c
> @@ -2299,4 +2299,5 @@ regression_main(int argc, char *argv[], init_function ifunc, test_function tfunc
>          fputs("\n# Configuration added by pg_regress\n\n", pg_conf);
>          fputs("max_prepared_transactions = 2\n", pg_conf);
> +        fputs("unix_socket_permissions = 0700\n", pg_conf);

Pg_upgrade has this exact same problem, and take the same approach.  You
might want to look in pg_upgrade/server.c.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + Everyone has their own god. +



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

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: Changeset Extraction v7.9.1
Следующее
От: Haribabu Kommi
Дата:
Сообщение: Re: The behavior of CheckRequiredParameterValues()