Hello On Thu, 2011-01-13 at 00:31 +0200, ext Luiz Augusto von Dentz wrote: > Hi, > > On Wed, Jan 12, 2011 at 2:08 PM, Matti J. Aaltonen > <matti.j.aaltonen@xxxxxxxxx> wrote: > > Initiate authorization check also in cases where the > > security level of an existing connection changes to > > BT_SECURITY_HIGH. > > > > This patch fixes a bug which makes commands bluez-test-device and > > bluez-simple-agent fail, if the latter is given before the connection > > created by bluez-test-device has expired. > > > I don't think this fixes the problem properly, the authentication > request could have been sent before because other levels might require > it, also Im afraid this can break sockets using the same link since > the state got reseted to BT_CONFIG when it could previously be > BT_CONNECTED, what happens if there a socket in use and the link is > set back to BT_CONFIG after connected? Yes. One of our bluetooth specialists suggested a simpler and probably better fix for this. He'll probably send his patch shortly... Thanks, Matti -- 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
