Recommend security@postgresql.org as the contact point for security-related bugs.
This commit is contained in:
parent
790c666931
commit
0c109c7187
@ -1,10 +1,14 @@
|
|||||||
If PostgreSQL failed to compile on your computer or you found a bug that
|
If PostgreSQL failed to compile on your computer or you found a bug that
|
||||||
is likely to be specific to one platform then please fill out this form
|
is likely to be specific to one platform, then please fill out this form
|
||||||
and e-mail it to pgsql-ports@postgresql.org.
|
and e-mail it to pgsql-ports@postgresql.org.
|
||||||
|
|
||||||
To report any other bug, fill out the form below and e-mail it to
|
To report non-porting-related bugs, fill out the form below and e-mail it to
|
||||||
pgsql-bugs@postgresql.org.
|
pgsql-bugs@postgresql.org.
|
||||||
|
|
||||||
|
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.
|
||||||
|
|
||||||
If you not only found the problem but solved it and generated a patch
|
If you not only found the problem but solved it and generated a patch
|
||||||
then e-mail it to pgsql-patches@postgresql.org instead. Please use the
|
then e-mail it to pgsql-patches@postgresql.org instead. Please use the
|
||||||
command "diff -c" to generate the patch.
|
command "diff -c" to generate the patch.
|
||||||
|
@ -1,5 +1,5 @@
|
|||||||
<!--
|
<!--
|
||||||
$PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.19 2004/08/24 00:06:50 neilc Exp $
|
$PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.20 2005/01/30 21:31:48 tgl Exp $
|
||||||
-->
|
-->
|
||||||
|
|
||||||
<sect1 id="bug-reporting">
|
<sect1 id="bug-reporting">
|
||||||
@ -309,6 +309,13 @@ $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.19 2004/08/24 00:06:50 neilc E
|
|||||||
<email>pgsql-bugs@postgresql.org</email> mailing list.
|
<email>pgsql-bugs@postgresql.org</email> mailing list.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
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
|
||||||
|
<literal>pgsql-bugs</literal>. Security issues can be
|
||||||
|
reported privately to <email>security@postgresql.org</email>.
|
||||||
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
Do not send bug reports to any of the user mailing lists, such as
|
Do not send bug reports to any of the user mailing lists, such as
|
||||||
<email>pgsql-sql@postgresql.org</email> or
|
<email>pgsql-sql@postgresql.org</email> 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
|
This list is for discussing the
|
||||||
development of <productname>PostgreSQL</productname>, and it would be nice
|
development of <productname>PostgreSQL</productname>, and it would be nice
|
||||||
if we could keep the bug reports separate. We might choose to take up a
|
if we could keep the bug reports separate. We might choose to take up a
|
||||||
discussion
|
discussion about your bug report on <literal>pgsql-hackers</literal>,
|
||||||
about your bug report on <literal>pgsql-hackers</literal>, if the problem needs more review.
|
if the problem needs more review.
|
||||||
</para>
|
</para>
|
||||||
|
|
||||||
<para>
|
<para>
|
||||||
|
Loading…
x
Reference in New Issue
Block a user