)]}'
{
  "commit": "f0bdf5c9a10ba7172001aece1ed4908830eebea2",
  "tree": "a8b323ac20148d4a8ef0bbce6b2ccbae828fc6dd",
  "parents": [
    "6be491b7bb57c3950d4fbb97fdd4a141e3fa4d63"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Thu Oct 31 14:50:38 2019 -0400"
  },
  "committer": {
    "name": "CQ bot account: commit-bot@chromium.org",
    "email": "commit-bot@chromium.org",
    "time": "Thu Oct 31 19:20:03 2019 +0000"
  },
  "message": "Discard user_canceled alerts in TLS 1.3.\n\nWarning alerts do not exist in TLS 1.3, but RFC 8446 section 6.1\ncontinues to define user_canceled as a signal to cancel the handshake,\nwithout specifying how to handle it. JDK11 misuses it to signal\nfull-duplex connection close after the handshake. As a workaround, skip\nuser_canceled as in TLS 1.2. This matches NSS and OpenSSL.\n\nBug: b/135941563\nChange-Id: I7ef546f1f166741b9f112686c75e6757331948f0\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/38605\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": "660be0aa53cd4e0ffc72996542e6500bbe97ca46",
      "old_mode": 33188,
      "old_path": "ssl/test/runner/runner.go",
      "new_id": "fc68ce9ecaabbd88c8cbd108641c905d79969a84",
      "new_mode": 33188,
      "new_path": "ssl/test/runner/runner.go"
    },
    {
      "type": "modify",
      "old_id": "c1f9e7f86223b0012cd3a893cfb54bbe72c2e525",
      "old_mode": 33188,
      "old_path": "ssl/tls_record.cc",
      "new_id": "464c5c5acde0d28d0ad9a6a8a353675aca67f37e",
      "new_mode": 33188,
      "new_path": "ssl/tls_record.cc"
    }
  ]
}