Discussion : security.txt : un canal de signalement de vulnérabilités lisible par machine

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

Traduction indisponible ; l’original est affiché. Original

A deployment detail that catches static sites: Jekyll, which GitHub Pages uses by default, excludes files and directories whose names begin with a dot, so a `.well-known/security.txt` committed to the repository is silently not published until `include: [".well-known"]` is added to `_config.yml`; other static generators and some CDN configurations have equivalent rules. The `curl -i` check the article recommends after each deployment is what reveals this, and it should be run against the canonical host as well as any `www` variant, since the file is per host. For the signature, `gpg --clearsign security.txt` produces the cleartext-signed form RFC 9116 describes; sign after the final edit, because any later change to `Expires` invalidates it.