)]}'
{
  "commit": "7a1c6b25ce8eebf7a955f7453b6c3fb998ebe46f",
  "tree": "2e0f17ce12943208e876d7af5ba540aa07fe8929",
  "parents": [
    "2a704ec5451a38bc7db96b7e5169b8b75cc29a00"
  ],
  "author": {
    "name": "Adam Langley",
    "email": "agl@chromium.org",
    "time": "Wed Dec 17 11:02:58 2025 -0800"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Wed Dec 17 14:28:12 2025 -0800"
  },
  "message": "Add `RAND_maybe_reseed`\n\nWhen we use a jitter entropy source, `RAND_bytes` will need to rejitter\nsometimes. For applications that are extremely latency sensitive, they\nmay need to run a separate thread that polls this function so that a\nreseed never happens on a serving thread.\n\nAt the moment this function does nothing and serves as a reminder for me\nto support this when integrating the jitter stuff.\n\nChange-Id: I23dd201bf39b400dc70b95aa29835f606e508140\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/85847\nReviewed-by: David Benjamin \u003cdavidben@google.com\u003e\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\nAuto-Submit: Adam Langley \u003cagl@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8d533bb4b93d38ad42cb908fbe49bd7b6b444f28",
      "old_mode": 33188,
      "old_path": "crypto/fipsmodule/rand/rand.cc.inc",
      "new_id": "f9e605fe1ea29116811c4bf58d84962e061d4068",
      "new_mode": 33188,
      "new_path": "crypto/fipsmodule/rand/rand.cc.inc"
    },
    {
      "type": "modify",
      "old_id": "1cea36d2720af1935106a85942ea10179c7b914b",
      "old_mode": 33188,
      "old_path": "include/openssl/rand.h",
      "new_id": "9d66a895bfb977659e7992de86219e65e4c61ee7",
      "new_mode": 33188,
      "new_path": "include/openssl/rand.h"
    }
  ]
}
