The canonical field and clear-signing are recommended in tandem, per: https://datatracker.ietf.org/doc/html/draft-foudil-securitytxt-12 The signature can be verified by running: gpg --verify security.txt Expected output: Signature made Wed 12 Jan 2022 05:47:18 AM PST using EDDSA key E34085E7EEE484DA3BDAFE2F4AD3678F4A2C291C issuer "kcgen@users.noreply.github.com" Good signature from "kcgen (GitHub key) <kcgen@users.noreply.github.com>" [ultimate]
36 lines
1.1 KiB
Text
36 lines
1.1 KiB
Text
-----BEGIN PGP SIGNED MESSAGE-----
|
|
Hash: SHA256
|
|
|
|
# What is this file?
|
|
|
|
# security.txt is a proposed standard which allows websites to
|
|
# define security policies. The security.txt file sets clear
|
|
# guidelines for security researchers on how to report
|
|
# security issues. security.txt is the equivalent of
|
|
# robots.txt, but for security issues.
|
|
|
|
# This file conforms to draft RFC:
|
|
# https://datatracker.ietf.org/doc/html/draft-foudil-securitytxt-12
|
|
|
|
Canonical: https://github.com/dosbox-staging/dosbox-staging/blob/main/security.txt
|
|
|
|
# The DOSBox Staging team is comprised of volunteers focussing
|
|
# on various aspects of the project. Please inform the team as
|
|
# a whole by reporting security issues via Discord:
|
|
|
|
Contact: https://discord.gg/WwAg3Xf
|
|
|
|
Preferred-Languages: en
|
|
|
|
# Acknowledgements:
|
|
# nobody reported security issues to dosbox-staging yet
|
|
|
|
|
|
-----BEGIN PGP SIGNATURE-----
|
|
|
|
iJUEARYIAD0WIQTjQIXn7uSE2jva/i9K02ePSiwpHAUCYd7b5h8ca2NnZW5AdXNl
|
|
cnMubm9yZXBseS5naXRodWIuY29tAAoJEErTZ49KLCkcy7ABAN14t4FBNIQZHf7T
|
|
Jd9HOn2F3kFkDOyPQjMqUhjF86DFAQDAbnd/0msNW9CDD0J8oh6SgIgBC4eDgnLA
|
|
kt2Nosy9AQ==
|
|
=QUWN
|
|
-----END PGP SIGNATURE-----
|