summaryrefslogtreecommitdiff
path: root/pod/perlsecpolicy.pod
diff options
context:
space:
mode:
Diffstat (limited to 'pod/perlsecpolicy.pod')
-rw-r--r--pod/perlsecpolicy.pod6
1 files changed, 3 insertions, 3 deletions
diff --git a/pod/perlsecpolicy.pod b/pod/perlsecpolicy.pod
index ad555f074a..07a702495d 100644
--- a/pod/perlsecpolicy.pod
+++ b/pod/perlsecpolicy.pod
@@ -30,7 +30,7 @@ security team.
You should receive an initial response to your report within 72 hours.
If you do not receive a response in that time, please contact
the security team lead L<John Lightsey|mailto:john@04755.net> and
-the Perl pumpking L<SawyerX|mailto:xsawyerx@cpan.org>.
+the L<Perl steering council|mailto:steering-council@perl.org>.
When members of the security team reply to your messages, they will
generally include the perl-security@perl.org address in the "To" or "CC"
@@ -297,8 +297,8 @@ open and transparent as possible about the state of your security report.
New vulnerability reports will receive an initial reply within 72 hours
from the time they arrive at the security team's mailing list. If you do
not receive any response in that time, contact the security team lead
-L<John Lightsey|mailto:john@04755.net> and the Perl pumpking
-L<SawyerX|mailto:xsawyerx@cpan.org>.
+L<John Lightsey|mailto:john@04755.net> and the the L<Perl steering
+council|mailto:steering-council@perl.org>.
The initial response sent by the security team will confirm your message was
received and provide an estimated time frame for the security team's