Updates security.txt with compliant & up-to-date details
What does this MR do and why?
Updates security.txt with compliant & up-to-date details
-
security@is not a supported disclosure method - We use H1 for our acknowledgements
- To be RFC compliant we need an expiry date (https://securitytxt.org/)
- RFC says canonical points to the security.txt file itself
- Adds some explanatory comments
See also: gitlab-com/www-gitlab-com!108013 (merged)
Screenshots or screen recordings
These are strongly recommended to assist reviewers and reduce the time to merge your change.
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.