)]}'
{
  "commit": "33cb77a81e3275e665eabcadcb9f6cb2089e9452",
  "tree": "69bb39c935957cd6b8b33bef48daa4ef071ffa0f",
  "parents": [
    "3e5eff66c291ff556202f2cde0f24cfa3316d657"
  ],
  "author": {
    "name": "Brian Neradt",
    "email": "brian.neradt@gmail.com",
    "time": "Fri Mar 20 18:15:46 2026 -0500"
  },
  "committer": {
    "name": "GitHub",
    "email": "noreply@github.com",
    "time": "Fri Mar 20 18:15:46 2026 -0500"
  },
  "message": "cmake: limit GENERAL_NAME bssl probe (#13008)\n\nCMake can report HAVE_GENERAL_NAME_IN_BSSL_NAMESPACE on plain\nOpenSSL builds. In a build, the probe succeeded with\nOpenSSL 3.x even though SSLLIB_IS_BORINGSSL and SSLLIB_IS_AWSLC were\nboth false. That made OCSP stapling in src/iocore/net/OCSPStapling.cc\ntake the bssl::GENERAL_NAME path, and the final traffic_server link\nfailed with an undefined reference to bssl::GENERAL_NAME_it().\n\nThe probe is not safe to run for non-BoringSSL libraries. OpenSSL 3.x\nheaders allow bssl::GENERAL_NAME_it() to be declared syntactically, but\nlibcrypto only exports the global GENERAL_NAME_it symbol, so a\ncompile-only try_compile can false-positive.\n\nOnly run the probe for BoringSSL-family builds and force the cache\nentry off for plain OpenSSL builds.",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0019aabda8696685a83eb288bad698b1b2753b5e",
      "old_mode": 33188,
      "old_path": "CMakeLists.txt",
      "new_id": "d899e290528ce032581921c5a830083ec1d2828c",
      "new_mode": 33188,
      "new_path": "CMakeLists.txt"
    }
  ]
}