From 0c109c7187d7aa53a251f734d64d9c55d8f5977a Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Sun, 30 Jan 2005 21:31:48 +0000 Subject: Recommend security@postgresql.org as the contact point for security-related bugs. --- doc/src/sgml/problems.sgml | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) (limited to 'doc/src/sgml') diff --git a/doc/src/sgml/problems.sgml b/doc/src/sgml/problems.sgml index f48305bc5de..94100815bc8 100644 --- a/doc/src/sgml/problems.sgml +++ b/doc/src/sgml/problems.sgml @@ -1,5 +1,5 @@ @@ -309,6 +309,13 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.19 2004/08/24 00:06:50 neilc E pgsql-bugs@postgresql.org mailing list. + + If your bug report has security implications and you'd prefer that it + not become immediately visible in public archives, don't send it to + pgsql-bugs. Security issues can be + reported privately to security@postgresql.org. + + Do not send bug reports to any of the user mailing lists, such as pgsql-sql@postgresql.org or @@ -324,8 +331,8 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.19 2004/08/24 00:06:50 neilc E This list is for discussing the development of PostgreSQL, and it would be nice if we could keep the bug reports separate. We might choose to take up a - discussion - about your bug report on pgsql-hackers, if the problem needs more review. + discussion about your bug report on pgsql-hackers, + if the problem needs more review. -- cgit v1.2.3