)]}'
{
  "commit": "3a035dc523e60a0212e1adbbada3b6d6ed4e657e",
  "tree": "fa0330cfb33055b1c9fe8b4b501878b82ff3fa52",
  "parents": [
    "2d7adaea91627b77b3d560d12703191fa5c434c0"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Thu Nov 30 16:05:27 2023 -0500"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Fri Dec 01 00:35:10 2023 +0000"
  },
  "message": "Name the hash functions in the Kyber implementation\n\nWhen I was experimenting with different hash functions, it was useful to\nsplit them out, and I think this is clearer anyway. E.g. there are two\nuses of SHAKE-256 in the round3 submission, but the spec gives them\ndifferent names.\n\nXOF doesn\u0027t get its own abstraction because we need to stream data out\nof it.\n\nML-KEM similarly names things, though it will replace the KDF with a\nhash J that only gets applied to the rejection value.\n\nChange-Id: I67f1ac0216e05f61557023229572ff5fb36ed529\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/64407\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5d7971f1b8d04524a6e1601f69a6b5a808125b0c",
      "old_mode": 33188,
      "old_path": "crypto/kyber/kyber.c",
      "new_id": "e9e3a919808536a91adaaac04da6cc7460f6c6dc",
      "new_mode": 33188,
      "new_path": "crypto/kyber/kyber.c"
    }
  ]
}