)]}'
{
  "commit": "b83c680d03b302a88fefcddbdce1b753c4c54ca6",
  "tree": "e0fd6010cc37a10c4ddefe289c58fe3828f932b9",
  "parents": [
    "8368050fa9371840d76ea53ed38c3e5a1cb5e3bc"
  ],
  "author": {
    "name": "Adam Langley",
    "email": "agl@google.com",
    "time": "Tue May 03 09:16:21 2016 -0700"
  },
  "committer": {
    "name": "David Benjamin",
    "email": "davidben@google.com",
    "time": "Tue May 03 16:24:50 2016 +0000"
  },
  "message": "Add |CRYPTO_is_confidential_build|.\n\nIn the past we have needed the ability to deploy security fixes to our\nfrontend systems without leaking them in source code or in published\nbinaries.\n\nThis change adds a function that provides some infrastructure for\nsupporting this in BoringSSL while meeting our internal build needs. We\ndo not currently have any specific patch that requires this—this is\npurely preparation.\n\nChange-Id: I5c64839e86db4e5ea7419a38106d8f88b8e5987e\nReviewed-on: https://boringssl-review.googlesource.com/7849\nReviewed-by: David Benjamin \u003cdavidben@google.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "89b0bd14ed6fb55bb2ac676a5be08ef40795cbb7",
      "old_mode": 33188,
      "old_path": "crypto/crypto.c",
      "new_id": "e98e249a7930605ab8dfbdcd7677cfc68ebe11c7",
      "new_mode": 33188,
      "new_path": "crypto/crypto.c"
    },
    {
      "type": "modify",
      "old_id": "b52bcf80f44c596636148a7a0dc438e14d9714f8",
      "old_mode": 33188,
      "old_path": "include/openssl/crypto.h",
      "new_id": "3fd299f42dbd6e10c901221b241d8860e381f224",
      "new_mode": 33188,
      "new_path": "include/openssl/crypto.h"
    }
  ]
}