Hi Chen, On Wed, Jan 18, 2012 at 3:17 AM, Ganir, Chen <chen.ganir@xxxxxx> wrote: > Storing the address type in the LTK is not perfect. For this to work properly, you will store the address type only for devices which exchanged keys. What if we have devices which do not do pairing or exchange keys at all ? What if we use the CreateDevice instead of CreatePairedDevice? In that case we will not have the address type for future reconnections. We need to store the device address type in a separate file (for example, addresstypes) and manage it separately from the LTK management. Note that BlueZ is still relying on the kernel LE advertising cache (which is refreshed with either the automatic scanning prior to connection, or with the future background scanning support) for detecting address type for non-bonded devices. We have no plans to change that in near feature, because IIRC it would require changing bluetooth socket API (which would break all current BR/EDR applications). This is an issue separate from LTK storage, if you are interested on pursuing this, feel free to make a proposal. Best Regards, -- Anderson Lizardo Instituto Nokia de Tecnologia - INdT Manaus - Brazil -- 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
