)]}'
{
  "commit": "2a24f7206abc4bf7d370d3ae3e5e793eadd74d38",
  "tree": "c07cf2fdbb182b1696735984f9afad0c4f24eb15",
  "parents": [
    "818aaaa5e266bf55bd90aff081db8acfd406a8e7"
  ],
  "author": {
    "name": "Michael Brown",
    "email": "mcb30@ipxe.org",
    "time": "Tue Nov 03 14:34:11 2026 +0000"
  },
  "committer": {
    "name": "Michael Brown",
    "email": "mcb30@ipxe.org",
    "time": "Tue Nov 03 14:34:40 2026 +0000"
  },
  "message": "[crypto] Use tlskey_traffic() to ratchet traffic secrets\n\nFor the HKDF-based key schedule, we currently ratchet the traffic\nsecret based on a repeated call to tlskey_cipher(): generating a\ncipher key for application traffic will also implicitly consume the\ncurrent generation of the traffic secret and replace it with the next\ngeneration.\n\nSwitch to instead ratcheting the traffic secret based on a repeated\ncall to tlskey_traffic().  This is a more natural home for the\nfunctionality: the traffic secret is updated explicitly rather than\nimplicitly.  It also fits more naturally into the structure used by\nthe TLS protocol code, which currently allows received or transmitted\nmessages to explicitly schedule a change of traffic secret.\n\nSigned-off-by: Michael Brown \u003cmcb30@ipxe.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "65bbc6fcbb1dcab925f4aa73ed2ac2332636b951",
      "old_mode": 33188,
      "old_path": "src/crypto/tlskey.c",
      "new_id": "cf820584947bb9a250b24001aaa8ba7df96118c2",
      "new_mode": 33188,
      "new_path": "src/crypto/tlskey.c"
    }
  ]
}