)]}'
{
  "commit": "89386ac89bef26888b8d866ebb98b696d82dfde8",
  "tree": "431286dfac192ef6c56129e346fe8dc4394f6548",
  "parents": [
    "1dcdbdad915f282f514624f4c10a5084014d13bd"
  ],
  "author": {
    "name": "Adam Langley",
    "email": "alangley@gmail.com",
    "time": "Tue Oct 12 12:43:14 2021 -0700"
  },
  "committer": {
    "name": "Boringssl LUCI CQ",
    "email": "boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com",
    "time": "Thu Oct 21 19:06:37 2021 +0000"
  },
  "message": "Add magic tag to BoringSSL binaries.\n\nThere are cases where people grep binaries for strings like OpenSSL\nversion strings in order to detect when out-dated versions of libraries\nare being used. With BoringSSL you might find \"OpenSSL 1.1.1\n(compatible; BoringSSL)\", if the linker didn\u0027t discard it, but that\u0027s\nnot very helpful for knowing how up-to-date BoringSSL is because we\nhardly ever change it.\n\nThis change adds a distinct random value to search for that uniquely\nidentifies BoringSSL and includes a rough guide to how old the BoringSSL\ncopy is. The linker will hopefully not discard it because it\u0027s\nrefereneced from |OPENSSL_malloc|.\n\nChange-Id: Ie2259fd17a55d249a538a8a161b0d755396dd7b8\nReviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/49885\nReviewed-by: David Benjamin \u003cdavidben@google.com\u003e\nCommit-Queue: Adam Langley \u003cagl@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "639de32247e086d47d7bd6863a33f3a78ac7cedc",
      "old_mode": 33188,
      "old_path": "crypto/mem.c",
      "new_id": "7b36bfb84a0c26cda7708561ff745415a2407744",
      "new_mode": 33188,
      "new_path": "crypto/mem.c"
    }
  ]
}