)]}'
{
  "commit": "0c8a01ade0e5349f5b0f9afd5e4de622599ae1da",
  "tree": "40b152b5f385b89561df33078bfc57d3ff94c34f",
  "parents": [
    "52808ad8da7f55f3405a5195e0abea811f5136e3"
  ],
  "author": {
    "name": "Lily Chen",
    "email": "chlily@google.com",
    "time": "Thu Oct 08 16:13:52 2026 +0000"
  },
  "committer": {
    "name": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Thu Oct 08 12:35:43 2026 -0700"
  },
  "message": "crypto/x509 MTC: Tighten MTC subjectPublicKeyInfoHash length check\n\nWhen computing the MTC entry hash, we write the subjectPublicKeyInfoHash\nOCTET STRING with a single short-form length byte. Lengths above 127\nrequire a long-form DER length. No EVP_MD outputs more than 127 bytes,\nso this is unreachable, but tighten the check rather than support the\nlong form.\n\nChange-Id: I877df064197c90a14689ec4244be7ba66a6a6964\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/103908\nReviewed-by: David Benjamin \u003cdavidben@google.com\u003e\nAuto-Submit: Lily Chen \u003cchlily@google.com\u003e\nCommit-Queue: Lily Chen \u003cchlily@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d457e1b95d4db8c769065ebd1d16739f0ab84034",
      "old_mode": 33188,
      "old_path": "crypto/x509/x509_mtc.cc",
      "new_id": "abbbbb4354e6225b41cfde55fc7ea607bbee8a91",
      "new_mode": 33188,
      "new_path": "crypto/x509/x509_mtc.cc"
    }
  ]
}
