-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 09/11/14 12:50, George Kadianakis wrote:
I suspect that HS authorization is very rare in the current network, and if we believe it's a useful tool, it might be worthwhile to make it more useable by people.
For what it's worth, the reason I haven't (so far) implemented HS authorization for Briar is that it's inconvenient to manage the list of auth cookies (effectively a second copy of the controlling app's contact list) via the control port. It would be really nice if the controlling app could store the auth cookies itself and supply the relevant cookie when making a SOCKS connection. The SOCKS password field seems like a natural fit, but I think perhaps Tor's already using the username and password for some other purpose? Cheers, Michael -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQEcBAEBCAAGBQJUYjENAAoJEBEET9GfxSfMJz4H/iAHIn02IbkyjFEPYko2IIg/ ms6uTABTHm1VkF+UgrKejlNwYO/aVpPmeWGjohCrbqDbxw1PQdYVBncOyL1pLWa3 KkKYsyfoREGkp0/PR/jsRic3dopzp5wVKC2jT9ujVVrH1+Al1iG6f4feI6kmv4R+ jaXrjd4g57NnLpYlFwB8DMeLm/+Q5tWWp42pjNyy6edL+H06TDOe85ivcYsfzrbb BmMJexNvspKsmN5lDaG402TVnrmHaxJCj/ZaPBvQdEXDjOMQQD4MLM8eZYMY3nYA 23SW3QiXERqdg7jf8l2cLZNZyeTyYhZTRjbkySbsCwRWLN/UgE/s8WYkdbDRo0I= =i490 -----END PGP SIGNATURE-----