Re: [tor-bugs] #20532 [Core Tor/Tor]: Make sure directory_initiate_command_rend handles pluggable transports correctly

[Tor Bug Tracker & Wiki]

#20532: Make sure directory_initiate_command_rend handles pluggable transports
correctly
-+-
 Reporter:  teor |  Owner:
 Type:  defect   | Status:  new
 Priority:  High |  Milestone:  Tor:
 |  0.3.1.x-final
Component:  Core Tor/Tor |Version:
 Severity:  Normal   | Resolution:
 Keywords:  bridge-client, bridge-bypass,|  Actual Points:
  triage-out-030-201612  |
Parent ID:   | Points:  2
 Reviewer:   |Sponsor:
-+-
Changes (by nickm):

 * priority:  Medium => High
 * points:   => 2


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #20532 [Core Tor/Tor]: Make sure directory_initiate_command_rend handles pluggable transports correctly

[Tor Bug Tracker & Wiki]

#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):

 (asn has confirmed this on irc)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #20532 [Core Tor/Tor]: Make sure directory_initiate_command_rend handles pluggable transports correctly

[Tor Bug Tracker & Wiki]

#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: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #20532 [Core Tor/Tor]: Make sure directory_initiate_command_rend handles pluggable transports correctly

[Tor Bug Tracker & Wiki]

#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:
--+
Changes (by asn):

 * milestone:  Tor: 0.2.??? => Tor: 0.3.0.x-final


Comment:

 Assigning this to 0.3.0 since a bridge bypass is important to fix.

 (Also seems like #20528 and #20531 are related tickets)

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #20532 [Core Tor/Tor]: Make sure directory_initiate_command_rend handles pluggable transports correctly

[Tor Bug Tracker & Wiki]

#20532: Make sure directory_initiate_command_rend handles pluggable transports
correctly
--+--
 Reporter:  teor  |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:  bridge-client, bridge-bypass  |  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+--

Comment (by cypherpunks):

 > We have been unable to confirm this

 So you need to close ticket as invalid or not a bug.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

[tor-bugs] #20532 [Core Tor/Tor]: Make sure directory_initiate_command_rend handles pluggable transports correctly

[Tor Bug Tracker & Wiki]

#20532: Make sure directory_initiate_command_rend handles pluggable transports
correctly
--+--
 Reporter:  teor  |  Owner:
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:  Tor: 0.2.???
Component:  Core Tor/Tor  |Version:
 Severity:  Normal|   Keywords:  bridge-client, bridge-bypass
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 When a relay is configured as a bridge, a user reports this can lead to
 direct connections being made to the relay/bridge, even when a pluggable
 transport is configured. We have been unable to confirm this.

 ​https://lists.torproject.org/pipermail/tor-dev/2016-November/011618.html

 We should check directory_initiate_command_rend (the linked connection
 case), and connection_or_connect to make sure it is not possible for a
 connection to go directly to a configured bridge when a transport is set
 up.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs