)]}'
{
  "commit": "c81965a8add1d1fee7a2b1d1502b4af513726c6c",
  "tree": "ebb1ff79389fece9136eab1f33ba454d87500452",
  "parents": [
    "2bcb3151384b8c117d7b1c260a04b525cd568e0f"
  ],
  "author": {
    "name": "Adam Langley",
    "email": "agl@google.com",
    "time": "Wed Aug 08 09:25:36 2018 -0700"
  },
  "committer": {
    "name": "CQ bot account: commit-bot@chromium.org",
    "email": "commit-bot@chromium.org",
    "time": "Wed Aug 08 17:09:36 2018 +0000"
  },
  "message": "Set PBKDF2 limit in PKCS#12 to 100M.\n\nThe previous limit was |UINT_MAX|. Windows limits to 600K, but that\u0027s\nalready causing issues. This seems like a balance between being\ncompletely crazy and still large enough not to have to worry for a long\ntime. It\u0027s still probably too large for backend systems wanting to\nprocess arbitrary PKCS#12, but I don\u0027t think any fixed value will\nsatisfy all desires.\n\nChange-Id: I01a3f78d5f2df086f8dbc0e8bacfb95153738f55\nReviewed-on: https://boringssl-review.googlesource.com/30424\nCommit-Queue: David Benjamin \u003cdavidben@google.com\u003e\nReviewed-by: David Benjamin \u003cdavidben@google.com\u003e\nCQ-Verified: CQ bot account: commit-bot@chromium.org \u003ccommit-bot@chromium.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "811ab16714d4705699b927c40812e9cca1ae2d4f",
      "old_mode": 33188,
      "old_path": "crypto/pkcs8/pkcs8_x509.c",
      "new_id": "65389636fa01aa95828f8d9253090dda187e9699",
      "new_mode": 33188,
      "new_path": "crypto/pkcs8/pkcs8_x509.c"
    }
  ]
}