)]}'
{
  "commit": "779f7d0840a8bac4a0e10f2df4b08cd42df35592",
  "tree": "f619efe9f79984ba14c1913c2f2974650504075d",
  "parents": [
    "ebd8b8965c74ab06bb91f7a00b23822e1f1f26ca"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Fri Aug 26 16:02:49 2022 -0400"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Fri Aug 26 21:25:15 2022 +0000"
  },
  "message": "Add an EVP_HPKE_KEM_enc_len API.\n\nOHTTP concatenates enc to the ciphertext without any length prefix\n(unlike ECH), so an implementation would want to know the length of enc\nfor the chosen KEM. Add an accessor to help with that.\n\nWhile I\u0027m here, fix a couple places where we assumed a specific KEM in\nthe HPKE implementation (although we still only support the one KEM so\nthis is all moot).\n\nThere\u0027s probably something to be said for lifting the length checks out\nof the KEM-specific code and into the wrappers, as we\u0027re assuming\nfixed-width fields anyway. But I\u0027ve left it alone for now.\n\nChange-Id: I634a053faa5e3b35d846b690140333bdc741f92a\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/54065\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\nAuto-Submit: David Benjamin \u003cdavidben@google.com\u003e\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "827ffaab67bfc147af800d2b2db7a8b3cf22db9b",
      "old_mode": 33188,
      "old_path": "crypto/hpke/hpke.c",
      "new_id": "6e3d5e871cbee700bdbd849037025b10cd673141",
      "new_mode": 33188,
      "new_path": "crypto/hpke/hpke.c"
    },
    {
      "type": "modify",
      "old_id": "e2c98557ff65c95588ee7db8abaa4500b1a0ace5",
      "old_mode": 33188,
      "old_path": "include/openssl/hpke.h",
      "new_id": "5b0373db0f3d546afc33a44169359119615dce1d",
      "new_mode": 33188,
      "new_path": "include/openssl/hpke.h"
    }
  ]
}