-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Add security.txt #27628
Add security.txt #27628
Conversation
Ref https://securitytxt.org Signed-off-by: Lukas Reschke <lukas@statuscode.ch>
Signed-off-by: Lukas Reschke <lukas@statuscode.ch>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good idea!
I know! Must be some Austrian who had this idea 😉 |
} | ||
|
||
$response = "Contact: https://hackerone.com/nextcloud | ||
Expires: 2021-12-31T23:00:00.000Z |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you plan to extend this manually?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. Dynamic also seems a bit dishonest in case this ever gets changed 🙈 (I was thinking of making each end-of-year release extend this for a year or such)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can also always extend it when a new stable branch is branched of and up it to "in 1 year"
Then it matches the EOL of the major version?
To test:
Ref https://securitytxt.org