diff options
| author | Johan Hedberg <[email protected]> | 2011-01-19 12:06:48 +0530 |
|---|---|---|
| committer | Gustavo F. Padovan <[email protected]> | 2011-01-19 14:40:42 -0200 |
| commit | 88644bb9fee591b2743a881923263bc28df4cded (patch) | |
| tree | f544155e89e9c622fcc2a59c797e6da659370a13 /net/unix/af_unix.c | |
| parent | 683d949a7fbf33c244670e34d35c460e0d6558cb (diff) | |
Revert "Bluetooth: Update sec_level/auth_type for already existing connections"
This reverts commit 045309820afe047920a50de25634dab46a1e851d. That
commit is wrong for two reasons:
- The conn->sec_level shouldn't be updated without performing
authentication first (as it's supposed to represent the level of
security that the existing connection has)
- A higher auth_type value doesn't mean "more secure" like the commit
seems to assume. E.g. dedicated bonding with MITM protection is 0x03
whereas general bonding without MITM protection is 0x04. hci_conn_auth
already takes care of updating conn->auth_type so hci_connect doesn't
need to do it.
Signed-off-by: Johan Hedberg <[email protected]>
Acked-by: Marcel Holtmann <[email protected]>
Signed-off-by: Gustavo F. Padovan <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions