Hi, > > Whats in the patchset: > > - for new kernels implementation in mgmtops > > (with kernel patches from "[PATCH v2 0/4] Support for OOB in mgmt interface") > > - for compatibility with older kernels implementation in hciops (mimic mgmt) > > - D-Bus plugin only exposes OOB functionality. In future we could also have > > CreateOOB[Paired]Device (or similar) which would act as > > AddRemoteOobData+CreateDevice. > > What happened to the idea of changing CreateDevice to take a > dictionary as we discussed in irc? I guess this is the main point of > the OOB since with this implementation any process can overwrite the > OOB data of a remote device which is not safe, once we have OOB we > should try to pair to check if the data is really valid. The drawback > is that it breaks the current API but I guess we should be focusing on > BlueZ 5.x pretty soon. We can still have CreateDevice to take a dictionary along with 'direct' API. Keep in mind that OOB data can be used in incoming pairing request as well so a way to provide OOB data for that is needed too. As for security reason we can limit access to those methods to registered agent only but I'm not sure if that would improve security if one has already bogus program running (i.e. it can register itself as agent, possibly after killing agent process) -- BR, Szymon Janc -- 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
