)]}'
{
  "commit": "3fdca1e1370ffe89980927cdef0583bebcd8caaf",
  "tree": "30ec395081409d7cea5338cf4f486eaabd14e53d",
  "parents": [
    "052b30b0a8eec8db5b18ad49effdf2a9ba4c1e1a"
  ],
  "author": {
    "name": "Marcel Holtmann",
    "email": "marcel@holtmann.org",
    "time": "Tue Apr 28 09:04:55 2009 -0700"
  },
  "committer": {
    "name": "Marcel Holtmann",
    "email": "marcel@holtmann.org",
    "time": "Tue Apr 28 09:31:39 2009 -0700"
  },
  "message": "Bluetooth: Fix connection establishment with low security requirement\n\nThe Bluetooth 2.1 specification introduced four different security modes\nthat can be mapped using Legacy Pairing and Simple Pairing. With the\nusage of Simple Pairing it is required that all connections (except\nthe ones for SDP) are encrypted. So even the low security requirement\nmandates an encrypted connection when using Simple Pairing. When using\nLegacy Pairing (for Bluetooth 2.0 devices and older) this is not required\nsince it causes interoperability issues.\n\nTo support this properly the low security requirement translates into\ndifferent host controller transactions depending if Simple Pairing is\nsupported or not. However in case of Simple Pairing the command to\nswitch on encryption after a successful authentication is not triggered\nfor the low security mode. This patch fixes this and actually makes\nthe logic to differentiate between Simple Pairing and Legacy Pairing\na lot simpler.\n\nBased on a report by Ville Tervo \u003cville.tervo@nokia.com\u003e\n\nSigned-off-by: Marcel Holtmann \u003cmarcel@holtmann.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "75ebbe2221a30b53b657f36defffe52d0026afba",
      "old_mode": 33188,
      "old_path": "net/bluetooth/hci_conn.c",
      "new_id": "375f4b4f7f79a25c328523227ba17679b8b29092",
      "new_mode": 33188,
      "new_path": "net/bluetooth/hci_conn.c"
    }
  ]
}