[guardian-dev] GilgaMesh (was Re: FireChat moved off iOS proprietary mesh to their own xp mesh protocol?)

[Chris Ballinger]

Unfortunately, Apple doesn't provide any APIs for programmatically
connecting to Wifi networks, nor changing your Bluetooth advertisement
name. The MC framework reverse engineering is very interesting, but may be
a bit too heavy weight, and is subject to Apple changing the internals at
any time.

On Fri, Oct 3, 2014 at 2:37 AM, Michael Rogers <michael at briarproject.org>
wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 02/10/14 21:07, Chris Ballinger wrote:
> > However, I think it would be beneficial to utilize other transports
> > for Android<-->Android and iOS<-->iOS for increased overall range /
> > mesh quality. The iOS MultipeerConnectivity framework uses Wifi /
> > Bluetooth in a proprietary/closed way and will never interoperate
> > with Android (by design). Android supports Wifi Direct in a more
> > open fashion, but it will never interoperate with iOS because Apple
> > likes to be stubborn.
>
> Someone reverse-engineered the wifi parts of the Multipeer
> Connectivity Framework - it's a combination of Bonjour for service
> discovery, self-signed X.509 certs for mutual auth, and DTLS with a
> magic byte prepended for data transfer. It should be possible to
> create a compatible Android library.
>
>
> https://nabla-c0d3.github.io/blog/2014/08/20/multipeer-connectivity-follow-up/
>
> I don't have time to work on this right now, but it would make a good
> Masters project.
>
> Wi-Fi Direct legacy mode is another promising path for
> interoperability - one peer creates a standard access point with a
> random SSID and password, the other peer connects to it as a standard
> client. So if you can pass the SSID and password from the AP to the
> other peer (e.g. via a QR code, or by encoding them in the AP's
> Bluetooth device name), the other peer just needs an API for
> connecting to wifi access points. Which hopefully even Apple supports?
>
> Cheers,
> Michael
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.12 (GNU/Linux)
>
> iQEcBAEBCAAGBQJULm5gAAoJEBEET9GfxSfMulkH/2vkFjvYu4qherR61JJ2UhzT
> LgeTKZpaJG8qmbPCLbS8Jq2ScUQQrzisQWB2PIiZAGXTsPPXXnBwXxMdxVVlH3Km
> +zi1fAI6O3ofh2iIG5ofSzAW5zVWg4+TD5hh2ueYm90fkoSipctRfLQPJm4Hm519
> LcwLqH6x6j4H7d0VECtOP+H8NA6F2b5D0uvUYh4lWMakYle+nDLrU42P7Mbgh0oL
> AiA+uoyq0qAafFHT0SManfyww7pYvR0LWLM4OXWqX9MBikRonAXK/m442jZbzWV9
> Fhl0HFzn6rsCcJt42K5++aZeJIbSPgVAwFXKxFUBW+vhvPn+FFQsVwVf9pHe0FM=
> =MB0g
> -----END PGP SIGNATURE-----
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mayfirst.org/pipermail/guardian-dev/attachments/20141003/6644f163/attachment.html>