Hi, On Thu, May 30, 2013 at 11:26 AM, Mikel Astiz <mikel.astiz.oss@xxxxxxxxx> wrote: > From: Mikel Astiz <mikel.astiz@xxxxxxxxxxxx> > > I'm reworking Timo's patch originally submitted as "[RFC] Bluetooth: Fix missing MITM protection when being responding LM". > > The proposal is to use MITM protection for General Bonding exactly as for Dedicated Bonding (patch 2/2). I can't think of any reason why the current implementation has different policies, leading to not using MITM protection for General Bonding even if the I/O capabilities make it possible. > > The proposal is therefore to make both bonding types equal. > > Another alternative would be to toggle this behavior through a mgmt API setting. > > Mikel Astiz (1): > Bluetooth: Use defines instead of integer literals > > Timo Mueller (1): > Bluetooth: Use MITM protection when responding LM > > net/bluetooth/hci_event.c | 23 +++++++++++------------ > 1 file changed, 11 insertions(+), 12 deletions(-) > > -- > 1.8.1.4 > Ping. -- 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
