)]}'
{
  "commit": "63007cec70bd21e96b0486c3cacfd8af205ae51c",
  "tree": "8fb04ef8f3a77deea4a8c428a29b4d078982c9b5",
  "parents": [
    "3f0df23b0b9eee22e76a24b396a33fbd036d6904"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Thu Aug 01 13:50:07 2019 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Thu Aug 01 13:50:07 2019 +0300"
  },
  "message": "Mail: fixed duplicate resolving.\n\nWhen using SMTP with SSL and resolver, read events might be enabled\nduring address resolving, leading to duplicate ngx_mail_ssl_handshake_handler()\ncalls if something arrives from the client, and duplicate session\ninitialization - including starting another resolving.  This can lead\nto a segmentation fault if the session is closed after first resolving\nfinished.  Fix is to block read events while resolving.\n\nReported by Robert Norris,\nhttp://mailman.nginx.org/pipermail/nginx/2019-July/058204.html.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "939fb1a51905a137c705f1d25c327eab2acfbfa9",
      "old_mode": 33188,
      "old_path": "src/mail/ngx_mail_smtp_handler.c",
      "new_id": "f1017e0d89fc6fd66756ce125db03e722ec1ec12",
      "new_mode": 33188,
      "new_path": "src/mail/ngx_mail_smtp_handler.c"
    }
  ]
}