)]}'
{
  "commit": "86c2e62f7428d1e49b0320ea4706704e5a6aca8a",
  "tree": "57efbd52affb3f63ff711111754cf84fe6eedb62",
  "parents": [
    "df091b2df3619badea8b58a46da7b1ffea0fc863"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Fri Sep 20 16:18:00 2024 -0400"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Tue Sep 24 00:44:57 2024 +0000"
  },
  "message": "Rearrange 0-RTT key schedule setup slightly\n\nWe used to sometimes setup the 0-RTTs keys before reverifying the\ncertificate, and sometimes after due to QUIC\u0027s needs, which was why the\nlong comment (see\nhttps://boringssl-review.googlesource.com/c/boringssl/+/38885). That\ncomment is now inaccurate and we consistently haven\u0027t installed 0-RTT\nkeys yet.\n\nUpdate the comment and then avoid splitting up the key setup and the\nreverify step. This shouldn\u0027t have any real consequences, except that\nadding the dummy ChangeCipherSpec messgae now happens *after* setting\nhs-\u003eearly_session, and can potentially even happen after we set\nin_early_data if we want to.\n\nBug: 42290594\nChange-Id: I427c9cd521bd11982be3056a0099150a50dd9558\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/71528\nReviewed-by: Nick Harper \u003cnharper@chromium.org\u003e\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "5478df19b3932077ea6e29ab77b862911e24f49f",
      "old_mode": 33188,
      "old_path": "ssl/handshake_client.cc",
      "new_id": "976e9698cb25d282dc74d0e51607b00f7a9e68e6",
      "new_mode": 33188,
      "new_path": "ssl/handshake_client.cc"
    }
  ]
}