)]}'
{
  "commit": "1f05cb491d2161c1bb86e69139fdcdd85f0720ff",
  "tree": "3dc3c7398d2ca3d8823e3e68827dae5df98423a4",
  "parents": [
    "b17e56ba158de9a132e5335438af71b40dedcd08"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Sun Sep 13 19:45:46 2026 -0400"
  },
  "committer": {
    "name": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Tue Oct 20 12:21:42 2026 -0700"
  },
  "message": "Report X509_V_ERR_CERT_CHAIN_TOO_LONG if the chain was too long\n\nThe error code existed, but we weren\u0027t surfacing it. This resolves a\nvery, very old TODO in the codebase.\nd9b8b89bec4480de3a10bdaf9425db371c19145b in upstream OpenSSL did\nsomething similar.\n\nUpdate-Note: If we hit the chain limit, X509_verify_cert will now fail\nwith X509_V_ERR_CERT_CHAIN_TOO_LONG instead of one of\nX509_V_ERR_UNABLE_TO_GET_ISSUER_CERT or\nX509_V_ERR_UNABLE_TO_GET_ISSUER_CERT_LOCALLY.\n\nChange-Id: I02c0dcc7e437bc86417f9fb3520c4d73356c9101\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/103866\nReviewed-by: Lily Chen \u003cchlily@google.com\u003e\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2a79d3d9b16955b51b72671a5f35401cffadbf3a",
      "old_mode": 33188,
      "old_path": "crypto/x509/x509_test.cc",
      "new_id": "6015adc961e77981bf77dd318a60f6dfe70f3d82",
      "new_mode": 33188,
      "new_path": "crypto/x509/x509_test.cc"
    },
    {
      "type": "modify",
      "old_id": "39ee613254c78fa8ebaf04f0f2899cf646036653",
      "old_mode": 33188,
      "old_path": "crypto/x509/x509_vfy.cc",
      "new_id": "21b6a227147b4d074e139510ac6917f37de65799",
      "new_mode": 33188,
      "new_path": "crypto/x509/x509_vfy.cc"
    }
  ]
}
