)]}'
{
  "commit": "b65c32ec5a942ab3ada93a048089a938918aba7f",
  "tree": "d2925b709736bacd96191013a9309f4b875b0c0d",
  "parents": [
    "7b4e88434c4e7982fb053c49657e1c8bbb8692d9"
  ],
  "author": {
    "name": "Maciej S. Szmigiero",
    "email": "mail@maciej.szmigiero.name",
    "time": "Sat May 19 14:23:54 2018 +0200"
  },
  "committer": {
    "name": "James Morris",
    "email": "james.morris@microsoft.com",
    "time": "Mon Jun 25 12:17:08 2018 -0700"
  },
  "message": "X.509: unpack RSA signatureValue field from BIT STRING\n\nThe signatureValue field of a X.509 certificate is encoded as a BIT STRING.\nFor RSA signatures this BIT STRING is of so-called primitive subtype, which\ncontains a u8 prefix indicating a count of unused bits in the encoding.\n\nWe have to strip this prefix from signature data, just as we already do for\nkey data in x509_extract_key_data() function.\n\nThis wasn\u0027t noticed earlier because this prefix byte is zero for RSA key\nsizes divisible by 8. Since BIT STRING is a big-endian encoding adding zero\nprefixes has no bearing on its value.\n\nThe signature length, however was incorrect, which is a problem for RSA\nimplementations that need it to be exactly correct (like AMD CCP).\n\nSigned-off-by: Maciej S. Szmigiero \u003cmail@maciej.szmigiero.name\u003e\nFixes: c26fd69fa009 (\"X.509: Add a crypto key parser for binary (DER) X.509 certificates\")\nCc: stable@vger.kernel.org\nSigned-off-by: James Morris \u003cjames.morris@microsoft.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "7d81e6bb461a330a225658dde9b002b3b24e26bc",
      "old_mode": 33188,
      "old_path": "crypto/asymmetric_keys/x509_cert_parser.c",
      "new_id": "b6cabac4b62ba6b920cb5947c56db5839711bcc7",
      "new_mode": 33188,
      "new_path": "crypto/asymmetric_keys/x509_cert_parser.c"
    }
  ]
}