Add RFC 9116 security.txt to static/.well-known/#43
Open
kobihikri wants to merge 1 commit into
Open
Conversation
Adds a machine-discoverable security contact at /.well-known/security.txt, served by Hugo from static/. Points to the existing sops GitHub security- advisory reporting flow. Includes the RFC 9116-mandatory Expires field. Assisted by an AI tool; every line verified against the live site and the sops security policy. Signed-off-by: Kobi Hikri <kobi.hikri@gmail.com>
✅ Deploy Preview for getsops ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this does
Adds
/.well-known/security.txtby placing it instatic/.well-known/security.txt, which Hugo copies verbatim to the published site root.Why
RFC 9116 defines a standard file at
/.well-known/security.txtso a researcher can find where to report a vulnerability. Right now the live file is missing:sops is a secrets-management tool, so a discoverable reporting pointer feels especially fitting. I pointed the file at the existing flow rather than inventing anything:
Contact: https://github.com/getsops/sops/security/advisories/new— the GitHub security-advisory flow the sops README already directs reporters toPolicy:the sops security policyExpires:— RFC 9116 requires this field; set ~1 year out.Verifying it will serve
static/is copied verbatim to the published site — e.g.static/favicons/favicon.icois live athttps://getsops.io/favicons/favicon.ico(200) andstatic/images/...svgathttps://getsops.io/images/...(200). Sostatic/.well-known/security.txtwill publish athttps://getsops.io/.well-known/security.txt. Please double-check on a preview build.Single file, no other changes. Commit is DCO signed-off.
Disclosure: I used an AI tool to help spot this and draft the file. I verified every line myself against the live site and the sops security policy, and I take responsibility for the change. Happy to adjust the
Expiresdate, contact, or policy link to whatever you prefer.