)]}'
{
  "commit": "a9319d9b0f5d9cfe01ffd00ac926af86485dc981",
  "tree": "50fd3dc6a84dcd38243676d5bd7376e88c50607e",
  "parents": [
    "2f2d27eb5cd9106893d85d4109ffac4af928c685"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Tue Jan 19 17:44:12 2021 -0500"
  },
  "committer": {
    "name": "CQ bot account: commit-bot@chromium.org",
    "email": "commit-bot@chromium.org",
    "time": "Tue Jan 19 23:17:12 2021 +0000"
  },
  "message": "Fix client 0-RTT handling with ALPS.\n\nWhen offering 0-RTT, the client should check that all carried-over\nvalues are consistent with its preferences. This ensures that parameter\nnegotiation happens independently of 0-RTT. The ALPS version of this\ncheck was a tad too aggressive: a session without ALPS should be treated\nas always compatible.\n\nI\u0027ll follow this with a fix to the draft spec to clarify this.\n\nChange-Id: Ia3c2a60449c555d1d91c4e528215f8e551a90a9f\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/45104\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\nCommit-Queue: Adam Langley \u003cagl@google.com\u003e\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "9dd6a39ae863b3577bc9f68ac8afbb211a0e19c7",
      "old_mode": 33188,
      "old_path": "ssl/t1_lib.cc",
      "new_id": "5ca9610999d310ba72d01d7e1304085c81a5221d",
      "new_mode": 33188,
      "new_path": "ssl/t1_lib.cc"
    },
    {
      "type": "modify",
      "old_id": "2a58be785f8e3c8fb989c66681b59aa43217504f",
      "old_mode": 33188,
      "old_path": "ssl/test/runner/runner.go",
      "new_id": "04d4d3e483e16256b76dcdef0acfdf00ace07c5a",
      "new_mode": 33188,
      "new_path": "ssl/test/runner/runner.go"
    }
  ]
}