)]}'
{
  "commit": "1f64e536a99aec848271e5a43e27a91082575ad2",
  "tree": "4f12dacfe1b100e8e7165976be5a587ef823f490",
  "parents": [
    "a51a00b069e9b5cafb05c8ae48e4c2e5c08d9b13"
  ],
  "author": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue Sep 25 14:00:04 2018 +0300"
  },
  "committer": {
    "name": "Maxim Dounin",
    "email": "mdounin@mdounin.ru",
    "time": "Tue Sep 25 14:00:04 2018 +0300"
  },
  "message": "SSL: logging level of \"no suitable signature algorithm\".\n\nThe \"no suitable signature algorithm\" errors are reported by OpenSSL 1.1.1\nwhen using TLSv1.3 if there are no shared signature algorithms.  In\nparticular, this can happen if the client limits available signature\nalgorithms to something we don\u0027t have a certificate for, or to an empty\nlist.  For example, the following command:\n\n    openssl s_client -connect 127.0.0.1:8443 -sigalgs rsa_pkcs1_sha1\n\nwill always result in the \"no suitable signature algorithm\" error\nas the \"rsa_pkcs1_sha1\" algorithm refers solely to signatures which\nappear in certificates and not defined for use in TLS 1.3 handshake\nmessages.\n\nThe SSL_R_NO_COMMON_SIGNATURE_ALGORITHMS error is what BoringSSL returns\nin the same situation.\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "a11a7e5e3c621733400e7cf56838e5fbe6292206",
      "old_mode": 33188,
      "old_path": "src/event/ngx_event_openssl.c",
      "new_id": "3a0e150d2bf916e6c26338ec48641060774a5eb9",
      "new_mode": 33188,
      "new_path": "src/event/ngx_event_openssl.c"
    }
  ]
}