Add .well-known/security.txt file, closes QubesOS/qubes-issues#7022

[parulin]

Copy-pasting @andrewdavidwong content, and following @SaswatPadhi instructions, only changing the expiration date (first proposition was +4 years).

See:

• Provide https://qubes-os.org/.well-known/security.txt qubes-issues#7022
• https://forum.qubes-os.org/t/github-issue-7022-provide-https-qubes-os-org-well-known-security-txt/26972

[andrewdavidwong]

Suggestion: If you intend for this pull request to resolve the associated issue and would like for it to be linked to the issue automatically, you can put Closes QubesOS/qubes-issues#XXXX in the PR and/or commit message (where XXXX is the issue number). Closes is one of several special keywords that GitHub will recognize. If and when the PR is merged, GitHub will automatically close the associated issue.

[mfc]

testDeploy

[mfc]

PipelineRetry

[mfc]

website / pipeline breaks, maybe jekyll can't handle the new /.well-known/ folder?

https://securitytxt.org/ says that as fallback one can put security.txt in the root directory of the website if making a /.well-known/ folder isn't possible. should we do that instead?

or is someone able to troubleshoot?

[SaswatPadhi]

website / pipeline breaks, maybe jekyll can't handle the new /.well-known/ folder?

No, the failures are unrelated to /.well-known/. You can see this in the log:

For the Links > Internal check, the following failures were found:

* At ./_site/doc/system-requirements/index.html:392:

  internally linking to #important-updates; the file exists, but the hash 'important-updates' does not

* At ./_site/doc/system-requirements/index.html:394:

  internally linking to #important-updates; the file exists, but the hash 'important-updates' does not


HTML-Proofer found 2 failures!