)]}'
{
  "commit": "e9cb2ec832bc3225f617551c5bb2ba9170c74abc",
  "tree": "cceed812bcfd707655dca9ef55b907ff86b24a07",
  "parents": [
    "30789da28e0124c0523adc0b7bfb83737015dba6"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@chromium.org",
    "time": "Sat Aug 22 11:31:33 2015 -0400"
  },
  "committer": {
    "name": "Adam Langley",
    "email": "agl@google.com",
    "time": "Mon Aug 31 19:08:06 2015 +0000"
  },
  "message": "Don\u0027t support bidirectional shutdown over DTLS.\n\nBidirectional shutdown doesn\u0027t make sense over DTLS; you can\u0027t reuse the\nunderlying channel after receiving close_notify because the channel is\nunordered. This removes one caller of dtls1_read_bytes.\n\nReally close_notify makes no sense in DTLS. It can\u0027t even protect\nagainst some kind of truncation because it\u0027s all unordered. But continue\nto send it in case anything is (unreliably since the channel is lossy)\nrelying on close_notify to signal some kind of session end. This only\nmakes SSL_shutdown stop trying to wait for one once we\u0027ve already\ndecided to shut down the connection.\n\nBUG\u003d526437\n\nChange-Id: I6afad7cb7209c4aba0b96f9246b04c81d90987a9\nReviewed-on: https://boringssl-review.googlesource.com/5770\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "81e9b0a71e1dafb9954e0b2f5ad2a5738489362e",
      "old_mode": 33188,
      "old_path": "ssl/d1_pkt.c",
      "new_id": "3306368d49264a2b0fd69ef725171c56aa23491c",
      "new_mode": 33188,
      "new_path": "ssl/d1_pkt.c"
    }
  ]
}