Skip to content

Add security.txt #262

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 25, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions static/.well-known/security.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
# Unraid Security Policy
# This security.txt file follows RFC 9116 and helps security researchers
# report vulnerabilities.
# For urgent security matters, please email security@unraid.net.
# Reports should include a clear title, description of the issue, steps to
# reproduce, and any potential impact.

Contact: mailto:security@unraid.net
Policy: https://unraid.net/policies
Encryption: https://keys.openpgp.org/vks/v1/by-fingerprint/5461B0B9C1CCFB6E53A6760FC5D4DCC26C348C7B
Preferred-Languages: en
Canonical: https://unraid.net/.well-known/security.txt
Expires: 2030-12-31T23:59:00.000Z
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Shorten the expiration interval
An expiration date in 2030 is overly long. RFC 9116 recommends rotating this file periodically (e.g., every 6–12 months) to ensure the policy stays up to date.

Signature: https://unraid.net/.well-known/security.txt.sig
Comment on lines +8 to +14
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Missing signature file
Your Signature: https://unraid.net/.well-known/security.txt.sig entry requires the accompanying security.txt.sig file. Please include the PGP signature at that path or update the URL to point to an existing signature.