Update preferred contact method for the security team.

Thanks to Salvatore Bonaccorso for the patch.

Closes: #738607
git-svn-id: svn://anonscm.debian.org/ddp/manuals/trunk/developers-reference@10375 313b444b-1b9f-4f58-a734-7bb04f332e8d

diff --git a/debian/changelog b/debian/changelog
index f104ce240f1b791c9f1fe2b850fad7395a5e8abd..b471aa54e2cc1e6a30d05dfef46ca636f9a3520f 100644 (file)
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+developers-reference (3.4.12) UNRELEASED; urgency=medium
+
+  * Update preferred contact method for the security team. Closes: #738607
+    Thanks to Salvatore Bonaccorso for the patch.
+
+ -- Raphaël Hertzog <hertzog@debian.org>  Fri, 21 Feb 2014 10:25:00 +0100
+

 developers-reference (3.4.11) unstable; urgency=low
 
   * Team upload.
 developers-reference (3.4.11) unstable; urgency=low
 
   * Team upload.

diff --git a/pkgs.dbk b/pkgs.dbk
index 814c6ff8d129b15f00da1b411c7e94393aace207..873c42c4e7d0678c609153727434f581e58401f8 100644 (file)
--- a/pkgs.dbk
+++ b/pkgs.dbk
@@ -843,10 +843,9 @@ fixing them themselves, sending security advisories, and maintaining
 <para>
 When you become aware of a security-related bug in a Debian package, whether or
 not you are the maintainer, collect pertinent information about the problem,
 <para>
 When you become aware of a security-related bug in a Debian package, whether or
 not you are the maintainer, collect pertinent information about the problem,

-and promptly contact the security team, preferably by filing a ticket in
-their Request Tracker.
-See <ulink url="http://wiki.debian.org/rt.debian.org#Security_Team"></ulink>.
-Alternatively you may email &email-security-team;.
+and promptly contact the security team by emailing &email-security-team;. If
+desired, email can be encrypted with the Debian Security Contact key, see
+<ulink url="https://www.debian.org/security/faq#contact"/> for details.

 <emphasis role="strong">DO NOT UPLOAD</emphasis> any packages for
 <literal>stable</literal> without contacting the team.  Useful information
 includes, for example:
 <emphasis role="strong">DO NOT UPLOAD</emphasis> any packages for
 <literal>stable</literal> without contacting the team.  Useful information
 includes, for example: