)]}'
{
  "commit": "cfd368fef1b72e9468626ee03ed1992ceb1e8965",
  "tree": "36a3f6c2e953844de902601bdbbe40c3e9d52425",
  "parents": [
    "24ea25827c7b2ea7d7088417bbe575153296021c"
  ],
  "author": {
    "name": "Théo Battrel",
    "email": "theo.battrel@nordicsemi.no",
    "time": "Tue Apr 18 12:27:16 2023 +0200"
  },
  "committer": {
    "name": "Anas Nashif",
    "email": "anas.nashif@intel.com",
    "time": "Thu Jun 08 04:10:58 2023 -0400"
  },
  "message": "Bluetooth: Host: Fix GATT server handling of CCC\n\nGATT server was not doing enough check before udpating the CCC.\n\nFor example, a non-bonded client could update the CCC of a bonded client\nby spoofing his address.\n\nThis fix the issue by dissociating the CCC configuration of a bonded and\na non-bonded peer. To do that, a new field is added to the CCC config:\n`link_encrypted`.\n\nSigned-off-by: Théo Battrel \u003ctheo.battrel@nordicsemi.no\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "940416cceb65be583b229056c354316e890487ca",
      "old_mode": 33188,
      "old_path": "include/zephyr/bluetooth/gatt.h",
      "new_id": "8e626e97570e3d2f4b01cfa3e907e5cd4409993d",
      "new_mode": 33188,
      "new_path": "include/zephyr/bluetooth/gatt.h"
    },
    {
      "type": "modify",
      "old_id": "61b7b12e57f54bc1960c8dcf9378a42cc3b669b5",
      "old_mode": 33188,
      "old_path": "subsys/bluetooth/host/gatt.c",
      "new_id": "5539c4997f3b3c4029b6a88fe1a090be18e321b4",
      "new_mode": 33188,
      "new_path": "subsys/bluetooth/host/gatt.c"
    }
  ]
}