)]}'
{
  "commit": "c20e3b282c26205f39a89a23664245475d4d7cbc",
  "tree": "874ba9eab6060d17acb67bbeea1adb83241ca8f4",
  "parents": [
    "d0191fe059fc73ff70af31de1fb99f2d2298242c"
  ],
  "author": {
    "name": "Matt Caswell",
    "email": "matt@openssl.org",
    "time": "Wed May 09 10:45:46 2018 +0100"
  },
  "committer": {
    "name": "Matt Caswell",
    "email": "matt@openssl.org",
    "time": "Fri May 11 14:51:08 2018 +0100"
  },
  "message": "Fix mem leak in sslapi test\n\nThe recent change in behaviour where you do not get a NewSessionTicket\nmessage sent if you established the connection using a PSK caused a mem\nleak to be triggered in sslapitest. It was actually a latent bug and we\nwere just lucky we never hit it before. The problem is due to complexity\nwith the way PSK sessions were set up in the early_data tests. PSK session\nreference counting was handled differently to normal session reference\ncounting. This meant there were lots of special cases in the code where\nwe don\u0027t free a session if it is a PSK. It makes things easier if we just\nhandle PSK reference counts in the same way as other session reference\ncounts, and then we can remove all of the special case code.\n\nReviewed-by: Viktor Dukhovni \u003cviktor@openssl.org\u003e\n(Merged from https://github.com/openssl/openssl/pull/6198)\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1db3998e519ffbc986de16db65ff12a4a72dc844",
      "old_mode": 33188,
      "old_path": "test/sslapitest.c",
      "new_id": "efce84d2d9460b2959265701be8df8e7018979c4",
      "new_mode": 33188,
      "new_path": "test/sslapitest.c"
    }
  ]
}