)]}'
{
  "commit": "416920c6566dca4ddf2951001bdef9c8aaf52a26",
  "tree": "0c89598e18d082f05e640e29a8d02bb2e80864e9",
  "parents": [
    "c43c2829ec89e92971d78a63575e7d4b8737be11"
  ],
  "author": {
    "name": "Michael Brown",
    "email": "mcb30@ipxe.org",
    "time": "Wed Jun 17 15:38:01 2026 +0100"
  },
  "committer": {
    "name": "Michael Brown",
    "email": "mcb30@ipxe.org",
    "time": "Wed Jun 17 15:43:54 2026 +0100"
  },
  "message": "[tls] Prefer X25519 as a key exchange mechanism\n\nIn TLS version 1.3, the expected flow is that the client offers at\nleast one key share in the initial ClientHello, so that key exchange\ncan take place as soon as the ServerHello is received (without\nrequiring a HelloRetryRequest and a second round trip).\n\nWe cannot viably offer key shares for all supported groups, since the\nFFDHE groups have large public key values.  The most likely approach\nwill be that we offer a single key share for our most preferred group.\n\nExperiments suggest that X25519 is currently the most widely supported\nkey exchange group.  Make this the most preferred group to maximise\nthe chance that a (future) TLS version 1.3 handshake will avoid the\nextra round trip for a HelloRetryRequest.\n\nSigned-off-by: Michael Brown \u003cmcb30@ipxe.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fbaaa3b37d47051214814329dcb1174fced41acf",
      "old_mode": 33188,
      "old_path": "src/crypto/mishmash/oid_p256.c",
      "new_id": "bdac65811e59859bd8cd97145ff7ca3190ce92e1",
      "new_mode": 33188,
      "new_path": "src/crypto/mishmash/oid_p256.c"
    },
    {
      "type": "modify",
      "old_id": "f757d859f5005b9801d468bf93fb2514e4240c3f",
      "old_mode": 33188,
      "old_path": "src/crypto/mishmash/oid_p384.c",
      "new_id": "0ac3bc1e29399499a2762efba52992438bb060a7",
      "new_mode": 33188,
      "new_path": "src/crypto/mishmash/oid_p384.c"
    }
  ]
}
