)]}'
{
  "commit": "35e07a80d8c8b35c390467f485a9be4202ed9ec1",
  "tree": "dcc34a4d5d94879df0c5f8f87b4760f1a119fdfc",
  "parents": [
    "bc70ca75b1b2530b718ccc3ec2b31fe535bd7481"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Thu May 01 11:05:14 2025 -0400"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Fri May 02 10:01:22 2025 -0700"
  },
  "message": "Remove some dead code from SSL_CTX_use_certificate_chain_file\n\nSSL_CTX_use_certificate_chain_file has some extra logic where, if\nSSL_CTX_use_certificate succeeds but leaves an error in the error queue,\nit fails anyway.\n\nThe comment claims it\u0027s because, on cert/key mismatch, it succeeds and\nleaves an error. When the function was added in upstream\u0027s\nb3ca645f479b1f0bcfa1d1a65c955e8b7ff33de6, this appears to have been\ntrue.\n\nHowever, years later upstream\u0027s 6049399bafac74bd809ffac2108e8d5d284cd720\nadded an ERR_clear_error and made SSL_CTX_use_certificate behave more\nconsistently. Now the behavior is that installing a certificate silently\nclears any pre-existing mismatched keys, so this case no longer exists.\nThe recently-added tests also demonstrate this behavior.\n\nChange-Id: I4c7de44046f10bc653f8f1fd86aff0d6956b2b1a\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/79009\nAuto-Submit: David Benjamin \u003cdavidben@google.com\u003e\nReviewed-by: Adam Langley \u003cagl@google.com\u003e\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0b55a9d9505876a6035e8c689363dc98bc2e1af8",
      "old_mode": 33188,
      "old_path": "ssl/ssl_file.cc",
      "new_id": "1fe01abfe6d00ab6ac4c78316e8809bd86f198f1",
      "new_mode": 33188,
      "new_path": "ssl/ssl_file.cc"
    }
  ]
}