Direct security reports to our guidelines instead of giving (incorrect)

information in our note.

While here fix a minor nit with "e.g.,"

Approved by:	wblock
This commit is contained in:
Eitan Adler 2012-09-02 02:59:43 +00:00
parent bcfcea9dc0
commit 000ef04a07
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=39487

View file

@ -670,7 +670,7 @@
<literal>serious</literal> or <literal>serious</literal> or
<literal>critical</literal>. Do not overreact; refrain <literal>critical</literal>. Do not overreact; refrain
from labeling your problem <literal>critical</literal> from labeling your problem <literal>critical</literal>
unless it really is (e.g. data corruption issues, serious unless it really is (e.g., data corruption issues, serious
regression from previous functionality in -CURRENT) regression from previous functionality in -CURRENT)
or <literal>serious</literal> unless or <literal>serious</literal> unless
it is something that will affect many users (kernel it is something that will affect many users (kernel
@ -683,10 +683,11 @@
because of this.</para> because of this.</para>
<note> <note>
<para>Major security problems should <emphasis>not</emphasis> <para>Security problems should <emphasis>not</emphasis>
be filed in GNATS, because all GNATS information is public be filed in GNATS, because all GNATS information is public
knowledge. Please send such problems in private email to knowledge. Please send such problems according to our
&a.security-officer;.</para> <ulink url="http://security.freebsd.org/#how">security
report guidelines</ulink>.</para>
</note> </note>
</listitem> </listitem>