| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
This is a nitpick, but I have picked it.
|
| |
|
|
|
| |
The perl steering council should now be used as a secondary
contact if the security team does not respond to a report.
|
| |
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
Add a SECURITY.md file, so GitHub will
show a 'Report a security vulnerability' pointing
to the Policy when trying to create one issue.
|
