You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you are in contact with multiple persons, how do you know which share was emitted by which phone? Basically, how do you correctly regroup shares?
On iOS, you don't have access to the BLE advertisement packets MAC address.
On Android you could use the MAC address, assuming the MAC address randomization is synchronized with your EphID change frequency. But I don't know if you can control that, this article suggests that the randomization timer is implemented in the Bluetooth chip firmware.
Did you take these limitations into consideration for this new design? If yes, how do you solve the above problem?
The text was updated successfully, but these errors were encountered:
lbarman
added
bluetooth
Questions and comments regarding use of BT technology/measurements/accuracy of broadcasts
protocol
Questions about the protocol/cryptography
labels
Apr 13, 2020
You are right that for Secret Sharing, we would need to either transmit an additional small identifier or have access the to MAC address of incoming packets. Given Google and Apple's existing engagement with the contact tracing community, we are hopeful they might adopt our proposal and support it as part of their API.
When you are in contact with multiple persons, how do you know which share was emitted by which phone? Basically, how do you correctly regroup shares?
On iOS, you don't have access to the BLE advertisement packets MAC address.
On Android you could use the MAC address, assuming the MAC address randomization is synchronized with your EphID change frequency. But I don't know if you can control that, this article suggests that the randomization timer is implemented in the Bluetooth chip firmware.
Did you take these limitations into consideration for this new design? If yes, how do you solve the above problem?
The text was updated successfully, but these errors were encountered: