Hi Waldek, On Thu, Apr 21, 2011, Waldemar Rymarkiewicz wrote: > If host requires MITM protection notify that to controller in > io capabilities reply even if the remote device requires no bonding. > > If it is not respected, host can get an unauthenticated link key while > it expects authenticated one. > > Signed-off-by: Waldemar Rymarkiewicz <waldemar.rymarkiewicz@xxxxxxxxx> > --- > net/bluetooth/hci_event.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/net/bluetooth/hci_event.c b/net/bluetooth/hci_event.c > index 087953e..3ee0060 100644 > --- a/net/bluetooth/hci_event.c > +++ b/net/bluetooth/hci_event.c > @@ -2369,7 +2369,7 @@ static inline u8 hci_get_auth_req(struct hci_conn *conn) > > /* If remote requests no-bonding follow that lead */ > if (conn->remote_auth == 0x00 || conn->remote_auth == 0x01) > - return 0x00; > + return conn->auth_type & 0x01; > > return conn->auth_type; > } Your other patches seem ok to me, but have you verified this one with the BITE tester? This logic is directly copied from how it is in user space right now and that's something we have arrived at after multiple iterations with the BITE tester over the last few years. So I'd be very careful when changing it. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
