)]}'
{
  "commit": "b79cc84635ac6012b9ee522e0199ca792d121467",
  "tree": "78fae5752b0f80d7e711c689f2d619ce66eb40c5",
  "parents": [
    "30c4c30d4aa306de0e5869dc9812bf8223aec164"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Wed Dec 07 15:57:14 2016 -0500"
  },
  "committer": {
    "name": "CQ bot account: commit-bot@chromium.org",
    "email": "commit-bot@chromium.org",
    "time": "Thu Dec 08 16:57:57 2016 +0000"
  },
  "message": "Fix SSL_clear\u0027s interaction with session resumption.\n\nPrior to 87eab4902d1003983079881d3ee8a66ec2eaccc2, due to some\nconfusions between configuration and connection state, SSL_clear had the\nside effect of offering the previously established session on the new\nconnection.\n\nwpa_supplicant relies on this behavior, so restore it for TLS 1.2 and\nbelow and add a test. (This behavior is largely incompatible with TLS\n1.3\u0027s post-handshake tickets, so it won\u0027t work in 1.3. It\u0027ll act as if\nwe configured an unresumable session instead.)\n\nChange-Id: Iaee8c0afc1cb65c0ab7397435602732b901b1c2d\nReviewed-on: https://boringssl-review.googlesource.com/12632\nReviewed-by: David Benjamin \u003cdavidben@google.com\u003e\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\nCQ-Verified: CQ bot account: commit-bot@chromium.org \u003ccommit-bot@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "47ecd486b8fac01bce5201bc3d6eabf28099f3e2",
      "old_mode": 33188,
      "old_path": "ssl/ssl_lib.c",
      "new_id": "eed82b064d6c76fea77dc97a39e38600a6e49a0c",
      "new_mode": 33188,
      "new_path": "ssl/ssl_lib.c"
    },
    {
      "type": "modify",
      "old_id": "c2bb990b8c3bcf9492c9910baa8a97b75105feb6",
      "old_mode": 33188,
      "old_path": "ssl/ssl_test.cc",
      "new_id": "9bdaad2c1576f64a02847f0c82bef9ce2fc58c45",
      "new_mode": 33188,
      "new_path": "ssl/ssl_test.cc"
    }
  ]
}
