8000 Recommend security@postgresql.org as the contact point for security-r… · postgres/postgres@ebe0341 · GitHub
[go: up one dir, main page]
Skip to content

Commit ebe0341

Browse files
tglsfdctglsfdc
committed
Recommend security@postgresql.org as the contact point for security-related bugs.
1 parent bcc1c7b commit ebe0341

File tree

2 files changed

+21
-10
lines changed

2 files changed

+21
-10
lines changed

‎doc/bug.template

Lines changed: 13 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -1,35 +1,39 @@
11
If PostgreSQL failed to compile on your computer or you found a bug that
2-
is likely to be specific to one platform then please fill out this form
2+
is likely to be specific to one platform, then please fill out this form
33
and e-mail it to pgsql-ports@postgresql.org.
44

5-
To report any other bug, fill out the form below and e-mail it to
5+
To report non-porting-related bugs, fill out the form below and e-mail it to
66
pgsql-bugs@postgresql.org.
77

8+
If your bug report has security implications and you'd prefer that it not
9+
become immediately visible in public archives, don't send it to pgsql-bugs.
10+
Security issues can be reported privately to security@postgresql.org.
11+
812
If you not only found the problem but solved it and generated a patch
913
then e-mail it to pgsql-patches@postgresql.org instead. Please use the
1014
command "diff -c" to generate the patch.
1115

1216
You may also enter a bug report at http://www.postgresql.org/ instead of
13-
e-mail-ing this form.
17+
e-mailing this form.
1418

1519
============================================================================
1620
POSTGRESQL BUG REPORT TEMPLATE
1721
============================================================================
1822

1923

20-
Your name :
24+
Your name :
2125
Your email address :
2226

2327

24-
System Configuration
28+
System Configuration:
2529
---------------------
26-
Architecture (example: Intel Pentium) :
30+
Architecture (example: Intel Pentium) :
2731

28-
Operating System (example: Linux 2.0.26 ELF) :
32+
Operating System (example: Linux 2.4.18) :
2933

30-
PostgreSQL version (example: PostgreSQL-7.2.7): PostgreSQL-7.2.7
34+
PostgreSQL version (example: PostgreSQL 7.2.7): PostgreSQL 7.2.7
3135

32-
Compiler used (example: gcc 2.95.2) :
36+
Compiler used (example: gcc 3.3.5) :
3337

3438

3539
Please enter a FULL description of your problem:

‎doc/src/sgml/problems.sgml

Lines changed: 8 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/problems.sgml,v 2.13 2002/01/20 22:19:56 petere Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/problems.sgml,v 2.13.2.1 2005/01/30 21:32:38 tgl Exp $
33
-->
44

55
<sect1 id="bug-reporting">
@@ -289,6 +289,13 @@ $Header: /cvsroot/pgsql/doc/src/sgml/problems.sgml,v 2.13 2002/01/20 22:19:56 pe
289289
<email>pgsql-bugs@postgresql.org</email> mailing list.
290290
</para>
291291

292+
<para>
293+
If your bug report has security implications and you'd prefer that it
294+
not become immediately visible in public archives, don't send it to
295+
<literal>pgsql-bugs</literal>. Security issues can be
296+
reported privately to <email>security@postgresql.org</email>.
297+
</para>
298+
292299
<para>
293300
Do not send bug reports to any of the user mailing lists, such as
294301
<email>pgsql-sql@postgresql.org</email> or

0 commit comments

Comments
 (0)
0