[messaging] SafeSlinger's Ephemeral Fingerprint
mwfarb at cmu.edu
Fri Jul 11 12:09:30 PDT 2014
Thanks for sharing that study. It's so hard to pick good channel that can be used reliably by most users. Briar especially looks like an interesting project. If you're interested in a remote key exchange protocol, please get in touch. It would be great to collaborate.
It seems anonymity is an important goal of your project, and rightly so. While a SafeSlinger key exchange does not currently provide anonymity, it would be great to work with more experienced Tor developers like your team to add anonymity to remote key exchange.
Michael W. Farb
Research Programmer, Carnegie Mellon University CyLab
M 412-965-4725 - www.cylab.cmu.edu/safeslinger
On Jul 9, 2014, at 1:25 PM, Michael Rogers <michael at briarproject.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> On 08/07/14 17:06, Michael Farb wrote:
>> I think we can expect the availability and interoperability of
>> more local wireless channels to improve over time. I'd love to see
>> WiFi Direct supported in older devices to broaden its market share.
>> The UX design to use all available wireless channels in some sort
>> of massive discovery mode makes me shudder a little, but we need to
>> do something for those who are getting their standard Internet data
>> channels blocked.
> Hi Michael,
> We've experimented with using Bluetooth and wifi (infrastructure mode,
> not WiFi Direct) for pairwise key exchange in Briar. Although I
> haven't rigorously tested this, it seems that on some devices, the
> discovery success rate is lower when using both Bluetooth and wifi
> than with Bluetooth alone. I guess this could be due to interference
> between the two radios, or the extra processing load causing timeouts
> at some layer of the stack.
> This paper describes some problems and workarounds for using WiFi
> Direct and Bluetooth to connect Android devices:
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
> -----END PGP SIGNATURE-----
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Messaging