#20532: Make sure directory_initiate_command_rend handles pluggable transports correctly ------------------------------------------+-------------------------------- Reporter: teor | Owner: Type: defect | Status: new Priority: Medium | Milestone: Tor: | 0.3.0.x-final Component: Core Tor/Tor | Version: Severity: Normal | Resolution: Keywords: bridge-client, bridge-bypass | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: ------------------------------------------+--------------------------------
Comment (by teor): A further update from irc: {{{ consensus updates rs and client using infor from ri it's about ipv6 not about generic conflict ... it is when you paste meek bridge line and using plain tor relay ... start tcpdump and watch for ip.addr == 188.138.1.166 then with green onion menu chose tor network setting, choose to use bridge, custom and paster meek 0.0.2.0:2 3C3A6134E4B5B7D1C18AD4E86EE23FAC63866554 url=https://d2zfqthxsdq309.cloudfront.net/ front=a0.awsstatic.com it's fp for it it should to fail sometime during connections tor using this p to get extend info for desc fetching *fp if knows such relay it using relay addr insead of pt }}} 188.138.1.166 is the direct address of the relay 3C3A6134E4B5B7D1C18AD4E86EE23FAC63866554, not the transport address of https://d2zfqthxsdq309.cloudfront.net/ -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20532#comment:3> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs