summaryrefslogtreecommitdiff
path: root/Porting/security_template.pod
diff options
context:
space:
mode:
authorJohn Lightsey <john@04755.net>2020-08-25 15:49:05 -0500
committerTodd Rinaldo <toddr@cpan.org>2020-09-10 16:33:43 -0500
commitb135fd4a1ca0074e0baef5764530103cc97cc4fe (patch)
tree36507899fbe1213590228bfd43f82e88beefe316 /Porting/security_template.pod
parentd7cdd6274f87dbbcb0463c7fe8fd16ca3b738026 (diff)
downloadperl-b135fd4a1ca0074e0baef5764530103cc97cc4fe.tar.gz
Document the security team's processes and practices
Add a new perlsecpolicy POD file with detailed descriptions of the security team's vulnerability remediation workflow and the criteria used to distinguish security issues from other types of bugs. This also switches the team's public contact address to perl-security@perl.org, and updates the security contact information shown in github's issue interface.
Diffstat (limited to 'Porting/security_template.pod')
-rw-r--r--Porting/security_template.pod6
1 files changed, 3 insertions, 3 deletions
diff --git a/Porting/security_template.pod b/Porting/security_template.pod
index 9b0b39480b..62334274e8 100644
--- a/Porting/security_template.pod
+++ b/Porting/security_template.pod
@@ -64,8 +64,8 @@ The current version of perl is available from https://www.perl.org/get.html .
FIXME or use the following:
Specifics about the vulnerability were first disclosed to
-C<perl5-security-report>, a closed subscriber mailing list that has a
-subset of the perl 5 committers subcribed to it.
+C<perl-security>, a closed subscriber mailing list that has a
+subset of the perl committers subcribed to it.
=head2 When was the vulnerability discovered?
@@ -78,6 +78,6 @@ FIXME
=head2 How was the vulnerability reported?
FIXME: something like "So-and-so sent email to
-perl5-security-report@perl.org"
+perl-security@perl.org"
=cut