On Mon, Jan 12, 2009 at 5:53 AM, Marcel Holtmann <marcel@xxxxxxxxxxxx> wrote: > Hi Ville, > >> Here is set of unclean patches for discussion. These are still untested >> and contain issues, but I would like to know if we should continue with >> these or change something radically. Also commit messages are somewhat >> misleading in some places. >> >> Basically idea is to implement connection rejection support for l2cap >> and rfcomm sockets. IOW possibility to check initiator bd-address and >> ask for authorization before accepting connection. >> >> Other goal is to fix encryption and authentication levels to fulfill 2.1 >> requirements. > > so I pushed my re-worked and pending patches to bluetooth-testing.git > now. This adds support for BT_DEFER_SETUP and BT_SECURITY (only the > logic and not the actual socket option). Ville: thanks for the patches, pausing RFCOMM while encryption is disabled is a nice fix. I imagine that if encryption is not quickly re-established we need to drop the RFCOMM link rather than leaving it paused though. We will do some testing of the current rfcomm-pause patches. Nick -- 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
