C2SP/x509-limbo

Issues

• Test `rfc5280::nc::permitted-dn-match` puts SAN for example.com in the root cert

  #282 opened a day ago
  2

• Create a trophy case

  #270 opened a month ago
  0

• Regression detection follow-ons

  #202 opened 4 months ago
  2

• CI: Protect against test regressions

  #197 opened 4 months ago
  1

• RFE - Expected path in limbo.json

  #195 opened 4 months ago
  1

• Do a proper release + embed `limbo.json` as a release asset

  #188 opened 4 months ago
  0

• Figure out a good way to keep leaf cert keys around

  #186 opened 4 months ago
  0

• Additional testcases

  #174 opened 5 months ago
  2

• Additional harness ideas

  #168 opened 5 months ago
  2

• Communicate "why it matters" on each testcase

  #161 opened 5 months ago
  2

• Add a harness for macOS's `security verify-cert`

  #157 opened 5 months ago
  1

• Track and report harness-found bugs to upstream implementations

  #155 opened 5 months ago
  1

• CI: Enforce that `limbo.json` is up-to-date

  #150 opened 6 months ago
  1

• Render harness results on the site

  #137 opened 6 months ago
  1

• Idea: `conflicts_with` or similar in the schema

  #121 opened 6 months ago
  1

• Render the JSON schema on the site

  #112 opened 6 months ago
  2

• Rustls webpki test harness?

  #88 opened 6 months ago
  2

• Stabilize identifiers

  #87 opened 7 months ago
  0

• Go harness is returning computed result rather than "actual" result

  #63 opened 7 months ago
  0

• Testcase model: allow setting maximum chain-building depth

  #58 opened 7 months ago
  4

• Consider modelling failure reasons into Limbo spec

  #43 opened 8 months ago
  4

• Improve testing around name constraints

  #38 opened 8 months ago
  0

• Support `key_usage` in the harnesses

  #36 opened 9 months ago
  0

• Break up the namespaces a bit

  #32 opened 6 months ago
  1

• Test `cryptography-x509-validation` using our testsuite

  #30 opened 7 months ago
  2

• Schema: support a `tag` field that implies optionality

  #16 opened a year ago
  1

• Define a testcase result model/schema

  #14 opened a year ago
  2

• Idea: add a `limbo` subcommand that generates a reasonably formatted GitHub issue

  #12 opened a year ago
  2

• Add an example harness against a known-good library (go crypto/x509 probably)

  #9 opened a year ago
  0

• Determine a key reuse/output regeneration policy

  #8 opened a year ago
  4

• MVP: Architectural sketch

  #3 opened a year ago
  3

• CI: Enforce testcase schemas

  #2 opened 6 months ago
  3

• Testcase enumeration

  #1 opened 5 months ago
  16