.well-known/security.txt: Implement RFC 9116#156
Conversation
|
🚀 PR preview deployed to https://RIOT-OS-riot-os-org-preview-156.surge.sh |
|
Not working as naively expected 😦 https://riot-os-riot-os-org-preview-156.surge.sh/.well-known/security.txt |
Still 404. Is that also in a local setup? |
|
(might be that surge just not allows for .well-known to be exposed) |
|
It is also not in the zip artifact. So I would assume it does not work. But I have no idea who jekyll works :/ |
Yes, at least it works with |
|
OK, so squash, merge, and hope for the best? |
This provides the contact details for reporting security findings as per [RFC 9116][]. [RFC 9116]: https://datatracker.ietf.org/doc/html/rfc9116 Co-authored-by: Teufelchen <9516484+Teufelchen1@users.noreply.github.com> Co-authored-by: Martine Lenders <martine.lenders@tu-dresden.de>
In the "no requests" branch, the `maintainers` variable was not initialized. This fixes it.
Might be, that Githubs upload-artifact action just ignores hidden files. For deployment rsync of |
|
It worked 🎉 |
|
From #156 (comment)
|
This provides the contact details for reporting security findings as per RFC 9116.