> On 16 Mar 2016, at 18:05, Martin Kepplinger <[email protected]> wrote: > > Am 2016-03-15 um 19:07 schrieb Rusty Bird: >> >>> What did *not* work, was starting Torbrowser. That's a hard requirement, >>> and before bebugging it through I ask: Do I miss something when I just >>> allow outgoing connections to >>> >>> * Guard, >>> * Authority, >> >> But the authority IP addresses hardcoded in the Tor client source code >> differ from the authority IP addresses published in the networkstatus >> consensus... >> >> https://github.com/rustybird/corridor/commit/a56d751df399ab1c54f64b0d4dc59f732dc0adc3 >> >> <https://github.com/rustybird/corridor/commit/a56d751df399ab1c54f64b0d4dc59f732dc0adc3>
Is this still an issue? Can you provide an example? The authority addresses are kept up to date in both the tor source code and the network consensus. If you're using an old version of tor, some of the addresses may be outdated. Tim Tim Wilson-Brown (teor) teor2345 at gmail dot com PGP 968F094B teor at blah dot im OTR CAD08081 9755866D 89E2A06F E3558B7F B5A9D14F
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ tor-dev mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
