)]}'
{
  "commit": "f4e4cca43c9937758a8b73506ebe4b65beaa9def",
  "tree": "60e97a9c3edb722b1bb7ce5c58e17d9a1503b4ec",
  "parents": [
    "b657d18b460517e00ee01065ce10581a174534f5"
  ],
  "author": {
    "name": "Rudolf Polzer",
    "email": "rpolzer@google.com",
    "time": "Wed May 27 03:28:06 2026 -0700"
  },
  "committer": {
    "name": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Thu May 28 01:15:51 2026 -0700"
  },
  "message": "AES-CTR-HMAC: Apply the 64 GiB limit to open operations too.\n\nSeal operations already enforced it; however we should not attempt to\ndecode invalid strings, as this AEAD\u0027s security properties do not hold\nif the input is so large that the counter wraps.\n\nChange-Id: Iac64747b09449e06b5c7093abe7a58126a6a6964\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/95927\nReviewed-by: David Benjamin \u003cdavidben@google.com\u003e\nCommit-Queue: Rudolf Polzer \u003crpolzer@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "019d9e6072553aebd849ed6031717fabbbd1a9c3",
      "old_mode": 33188,
      "old_path": "crypto/cipher/e_aesctrhmac.cc",
      "new_id": "2bb1db6ec99bace41a7d925237a4cdc993763e38",
      "new_mode": 33188,
      "new_path": "crypto/cipher/e_aesctrhmac.cc"
    }
  ]
}