chore: publish security.txt for ipfs.tech - #324
Open
lidel wants to merge 2 commits into
Open
Conversation
Publishes an RFC 9116 security contact at https://ipfs.tech/.well-known/security.txt, so scanners and researchers looking for a reporting route find security@ipfs.io without digging through repos. The Expires field is set to 2027-08-01 and has to be moved forward before then, or the file is treated as stale.
Replaces the static file with an Astro endpoint so the RFC 9116 Expires field moves forward on its own instead of going stale a year from now. The value is the first of the build month, twelve months out, so repeat builds within the same month stay byte-identical and the deployed CID does not churn.
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
2 participants
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.
Problem
Someone who finds a security bug often uses LLMs and automated tools and its not obvious where to send it. Researchers and scanners check
/.well-known/security.txtfirst, and today that returns 404. So they guess an address, spam multiple emails, bother old maintainers etc.Fix
/.well-known/security.txtwithsecurity@ipfs.ioas the contact and a link to the project policy.Expiresfield at build time, twelve months out, so nobody has to remember to bump a date.1This covers the
ipfs.techdomain only. Per-repo reporting still lives in each repo'sSECURITY.md.Footnotes
RFC 9116, section 2.5.5:
Expiresmust always be present, and its value should be less than a year in the future to avoid staleness. ↩