Add /.well-known/security.txt (RFC 9116) - #863
Open
kobihikri wants to merge 1 commit into
Open
Conversation
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
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.
Hi, and thank you for Tokio.
This adds a machine-readable
/.well-known/security.txt(RFC 9116) to the site'spublic/dir, so it serves athttps://tokio.rs/.well-known/security.txt(currently 404). It just points automated tooling at the private reporting channelSECURITY.mdalready documents:I verified the
public/passthrough serves at the site root (e.g.tokio.rs/favicon.icoreturns 200), so this file will be served at the well-known path. RFC 9116 recommends refreshingExpiresat least annually — feel free to adjust the date or values.For transparency: I used AI assistance to help identify this and draft the file; I verified the live 404, the serving passthrough, and the SECURITY.md channel myself.