)]}'
{
  "commit": "8a558aa2fc6172396a41e853cc5c6e3109a98f56",
  "tree": "3b296986c80eb539d74b9a934aaf49afbcdb872b",
  "parents": [
    "30742686c6958159ab392129a51d57e1ba1f67a2"
  ],
  "author": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Thu Jan 11 16:55:56 2024 -0500"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Thu Jan 11 22:37:49 2024 +0000"
  },
  "message": "Do not condition CRYPTO_is_RDRAND_capable on __RDRND__\n\nOn some AMD processors, we will act as if the hardware is\nRDRAND-incapable, even it actually supports it, to workaround some bugs\nwhere their RDRAND would return all ones. However, this works by\nclearing the RDRAND bit, and the static capability check bypasses this.\n\nThat means, when compiling binaries for an RDRAND-capable baseline CPU,\nwe might end up disabling the workaround. Thanks to Brian Smith for\nnoticing this.\n\nFortunately, we believe this had no real impact and the workaround was\nactually redundant with other parts of our PRNG logic. See\nhttps://crbug.com/boringssl/675#c2 for a more detailed analysis.\n\nFixed: 675\nChange-Id: I91d844cfaafb22eb29254f81fb6719588937a4a8\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/65267\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\nAuto-Submit: David Benjamin \u003cdavidben@google.com\u003e\nReviewed-by: Bob Beck \u003cbbe@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e9da01065fe13c8171ab52e9c902eab389703c48",
      "old_mode": 33188,
      "old_path": "crypto/internal.h",
      "new_id": "31647113a677c86dc328e83f9689c2eea8ddf2eb",
      "new_mode": 33188,
      "new_path": "crypto/internal.h"
    }
  ]
}