securitytxt/security-txt issues and pull requests

#224 - RFC and Website should be consistent

Pull Request - State: open - Opened by JannisBush 30 days ago

#223 - Allow HTML

Issue - State: open - Opened by acjbizar about 2 months ago - 5 comments

#222 - a one-off annual cycle check is impossible within exactly one year

Issue - State: open - Opened by janwillemstegink 6 months ago

#221 - A simple field that company can use to share about the last security-related update being introduced ?

Issue - State: closed - Opened by santrancisco 11 months ago - 4 comments

#220 - Checksum, hashing and notification

Issue - State: open - Opened by Hyperpolymath 11 months ago - 2 comments

#218 - @sirathampitak

Issue - State: closed - Opened by tunsira almost 2 years ago

#217 - Clarification for Canonical field

Issue - State: closed - Opened by DigitalTrustCenter about 2 years ago - 2 comments

#216 - SSH signatures as an alternative to OpenPGP ones

Issue - State: open - Opened by Mikaela over 2 years ago - 3 comments
Labels: future work

#215 - This project appears dead, should someone fork it?

Issue - State: closed - Opened by grintor over 2 years ago - 3 comments

#214 - Specify allowed encryption schemes

Issue - State: open - Opened by technion about 3 years ago - 15 comments
Labels: ▶️ spec, ➡ Encryption:, future work

#213 - Scope field

Issue - State: open - Opened by nightwatchcyber about 3 years ago - 9 comments
Labels: future work

#212 - Use /.well-known/humans.txt URI instead?

Issue - State: closed - Opened by rugk about 3 years ago - 1 comment

#211 - Review my security.txt

Issue - State: closed - Opened by k0nsl over 3 years ago - 4 comments

#210 - Permitted values of Acknowledgments field?

Issue - State: closed - Opened by berkas1 over 3 years ago - 3 comments

#209 - Add a link to the human and machine readable security advisories

Issue - State: open - Opened by santosomar over 3 years ago - 7 comments
Labels: future work

#208 - Should the datetimes use an ISO8601 profile?

Issue - State: closed - Opened by edent over 3 years ago - 2 comments

#207 - Support distinct policies: bug bounty and external vuln disclosure

Issue - State: open - Opened by vladionescu over 3 years ago - 3 comments
Labels: future work

#206 - detached signatures (allow multiple people to sign the security.txt)

Issue - State: open - Opened by herbetom over 3 years ago
Labels: future work

#205 - Example of a signed "security.txt" file Header is Missing Hyphen

Issue - State: closed - Opened by theckman over 3 years ago - 1 comment
Labels: ▶️ spec

#204 - Consider clarifying whether Encryption should point directly to the key

Issue - State: closed - Opened by joker314 over 3 years ago - 1 comment
Labels: ▶️ spec, ➡ Encryption:

#203 - Remove demonstration for file system security.txt files

Pull Request - State: closed - Opened by joker314 over 3 years ago

#202 - Aligning ISO and CERT language with the draft

Issue - State: closed - Opened by nightwatchcyber over 3 years ago

#201 - Defer file systems work to future date

Issue - State: open - Opened by nightwatchcyber over 3 years ago - 3 comments
Labels: future work

#200 - Add "CSAF" field to find OASIS CSAF documents

Issue - State: closed - Opened by nightwatchcyber over 3 years ago - 10 comments
Labels: future work

#199 - Add differentiation between PSIRT and CERT contact

Issue - State: open - Opened by tschmidtb51 over 3 years ago - 2 comments
Labels: future work

#198 - Consider adding "Last Updated" field

Issue - State: closed - Opened by nightwatchcyber over 3 years ago - 1 comment
Labels: future work

#196 - Extension: security.txt in DNS

Issue - State: open - Opened by Addvilz about 4 years ago - 3 comments
Labels: future work

#195 - Add a ability to differentiate security contacts between parts of an application / scope of security.txt

Issue - State: open - Opened by spidererrol about 4 years ago - 1 comment
Labels: future work

#194 - Define if HTTP 30X redirect is allowed what constraints apply

Issue - State: closed - Opened by back2root about 4 years ago - 1 comment

#193 - Additional changes for last call feedback

Pull Request - State: closed - Opened by nightwatchcyber about 4 years ago

#192 - Last call changes

Pull Request - State: closed - Opened by nightwatchcyber about 4 years ago

#191 - Blank lines not covered by ABNF grammar?

Issue - State: closed - Opened by eikendev about 4 years ago - 9 comments
Labels: question

#190 - Last Call: Make Expires field mandatory + add guidance for value

Issue - State: closed - Opened by nightwatchcyber about 4 years ago - 1 comment
Labels: last-call

#189 - Last Call: Address AD feedback

Issue - State: closed - Opened by nightwatchcyber about 4 years ago - 1 comment
Labels: last-call

#188 - Add note regarding the well know namespace

Issue - State: closed - Opened by nightwatchcyber over 4 years ago - 1 comment
Labels: last-call

#187 - Preparing for draft-10

Pull Request - State: closed - Opened by nightwatchcyber over 4 years ago

#186 - Last changes before publishing new version

Pull Request - State: closed - Opened by nightwatchcyber over 4 years ago

#185 - Add language clarifying scope around product vulnerabilities

Issue - State: open - Opened by nightwatchcyber over 4 years ago - 4 comments
Labels: future work

#184 - Discuss embedding the file in desktop or mobile apps

Issue - State: open - Opened by nightwatchcyber over 4 years ago - 2 comments
Labels: future work

#183 - Last call changes

Pull Request - State: closed - Opened by nightwatchcyber over 4 years ago

#182 - Last call: Change language around "directive"

Issue - State: closed - Opened by nightwatchcyber over 4 years ago - 1 comment

#181 - Last Call: Consider adding expiration date field

Issue - State: closed - Opened by nightwatchcyber over 4 years ago - 1 comment

#180 - Last Call Feedback: SecDir review

Issue - State: closed - Opened by nightwatchcyber over 4 years ago - 1 comment

#179 - Last call feedback: S. Moonesamy

Issue - State: closed - Opened by nightwatchcyber over 4 years ago - 1 comment

#178 - Last Call: Consider a separate abuse contact

Issue - State: open - Opened by nightwatchcyber almost 5 years ago - 1 comment
Labels: future work

#177 - HTTPS MUST on IP addresses with certificate validation?

Issue - State: open - Opened by asbjornst almost 5 years ago - 1 comment
Labels: future work

#176 - URI and the percent-encoding

Issue - State: closed - Opened by bortzmeyer almost 5 years ago - 1 comment
Labels: ▶️ spec, ➡ Contact:

#175 - Last Call: Change title of the draft

Issue - State: closed - Opened by nightwatchcyber almost 5 years ago - 1 comment
Labels: last-call