)]}'
{
  "commit": "55e9dce37ddf3ab358ba1d1e9eef4ee4bd8174a6",
  "tree": "e850e9052d4db68905cb6c444e269ed7c719301e",
  "parents": [
    "06b42aa94b65806b4f8c5fc893ef97a2f491fb32"
  ],
  "author": {
    "name": "David McCullough",
    "email": "david_mccullough@au.securecomputing.com",
    "time": "Wed Mar 15 21:08:51 2006 +1100"
  },
  "committer": {
    "name": "Herbert Xu",
    "email": "herbert@gondor.apana.org.au",
    "time": "Tue Mar 21 20:14:10 2006 +1100"
  },
  "message": "[CRYPTO] aes: Fixed array boundary violation\n\nThe AES setkey routine writes 64 bytes to the E_KEY area even though\nthere are only 60 bytes there.  It is in fact safe since E_KEY is\nimmediately follwed by D_KEY which is initialised afterwards.  However,\ndoing this may trigger undefined behaviour and makes Coverity unhappy.\n\nSo by combining E_KEY and D_KEY into one array we sidestep this issue\naltogether.\n\nThis problem was reported by Adrian Bunk.\n\nSigned-off-by: Herbert Xu \u003cherbert@gondor.apana.org.au\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fb1b961a2e2f185143fbbea09e2e6a43606b72fb",
      "old_mode": 33188,
      "old_path": "arch/x86_64/crypto/aes.c",
      "new_id": "6f77e7700d329506a453b21984f7fb15efe51b88",
      "new_mode": 33188,
      "new_path": "arch/x86_64/crypto/aes.c"
    },
    {
      "type": "modify",
      "old_id": "0a6a5c14368684937bf8ca9b4bd866fea06d0e15",
      "old_mode": 33188,
      "old_path": "crypto/aes.c",
      "new_id": "a5017292e06633337f0e83a78a01432c09f5d4c9",
      "new_mode": 33188,
      "new_path": "crypto/aes.c"
    }
  ]
}