)]}'
{
  "commit": "4bddf4587c131d7b8ce8952cd32b284dcda0dd1f",
  "tree": "46aead52a0c4802ba837851df9c5730f30015f17",
  "parents": [
    "5472d60c129f75282d94ae5ad072ee6dfb7c7246"
  ],
  "author": {
    "name": "Jarkko Sakkinen",
    "email": "jarkko@kernel.org",
    "time": "Mon Aug 25 23:32:23 2025 +0300"
  },
  "committer": {
    "name": "Jarkko Sakkinen",
    "email": "jarkko@kernel.org",
    "time": "Fri Oct 10 08:21:45 2025 +0300"
  },
  "message": "tpm: Disable TPM2_TCG_HMAC by default\n\nAfter reading all the feedback, right now disabling the TPM2_TCG_HMAC\nis the right call.\n\nOther views discussed:\n\nA. Having a kernel command-line parameter or refining the feature\n   otherwise. This goes to the area of improvements.  E.g., one\n   example is my own idea where the null key specific code would be\n   replaced with a persistent handle parameter (which can be\n   *unambigously* defined as part of attestation process when\n   done correctly).\n\nB. Removing the code. I don\u0027t buy this because that is same as saying\n   that HMAC encryption cannot work at all (if really nitpicking) in\n   any form. Also I disagree on the view that the feature could not\n   be refined to something more reasoable.\n\nAlso, both A and B are worst options in terms of backporting.\n\nThuss, this is the best possible choice.\n\nCc: stable@vger.kernel.or # v6.10+\nFixes: d2add27cf2b8 (\"tpm: Add NULL primary creation\")\nSuggested-by: Chris Fenner \u003ccfenn@google.com\u003e\nSigned-off-by: Jarkko Sakkinen \u003cjarkko@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ba3924eb13ba8926df50e3007a27317da24078dd",
      "old_mode": 33188,
      "old_path": "drivers/char/tpm/Kconfig",
      "new_id": "99c6fde288105fcc1ea3f30b0387e86e51355fa2",
      "new_mode": 33188,
      "new_path": "drivers/char/tpm/Kconfig"
    }
  ]
}