Re: [tor-bugs] #32115 [Core Tor/Tor]: Hidden Service in TestingTorNetwork connected to non-Exit Nodes

[Tor Bug Tracker & Wiki]

#32115: Hidden Service in TestingTorNetwork connected to non-Exit Nodes
--+---
 Reporter:  lewis85   |  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  not a bug
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---

Comment (by lewis85):

 Thank you very much for this clarification. I was errouneously referring
 to exit nodes as the nodes responsible to be the first hop for the hidden
 service in the circuit from the hidden service to the rendezvous point. As
 you mentioned, I should expect that the hidden service connects to the
 nodes flagged as "Guard" and this is what is happening in my testing
 environment.
 I am sorry for the confusion, it was my mistake. Thank you very much for
 providing this clarification. It was very helpful.

--
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] #32115 [Core Tor/Tor]: Hidden Service in TestingTorNetwork connected to non-Exit Nodes

[Tor Bug Tracker & Wiki]

#32115: Hidden Service in TestingTorNetwork connected to non-Exit Nodes
--+---
 Reporter:  lewis85   |  Owner:  (none)
 Type:  defect| Status:  closed
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:  not a bug
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by dgoulet):

 * status:  needs_information => closed
 * resolution:   => not a bug


Comment:

 Hidden services do _not_ connect specifically to Exit nodes. They stay
 inside the network.

 They can use Exit nodes as a "Regular" node of the hidden service
 connection process. But there is no concept of "exiting the network" with
 an hidden service.

 Also remember, tor client (which includes hidden service) will pick a
 Guard node and keep it for a while so you will always see the first
 connection to be the same node over and over again.

 With `TestingTorNetwork`, many many timings are changed within tor to
 accelerate many interactions between tor nodes so it is not like the real
 public network where for instance you would keep your Guard for around 3
 months.

--
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] #32115 [Core Tor/Tor]: Hidden Service in TestingTorNetwork connected to non-Exit Nodes

[Tor Bug Tracker & Wiki]

#32115: Hidden Service in TestingTorNetwork connected to non-Exit Nodes
--+---
 Reporter:  lewis85   |  Owner:  (none)
 Type:  defect| Status:  needs_information
 Priority:  Medium|  Milestone:
Component:  Core Tor/Tor  |Version:
 Severity:  Normal| Resolution:
 Keywords:|  Actual Points:
Parent ID:| Points:
 Reviewer:|Sponsor:
--+---
Changes (by nickm):

 * status:  new => needs_information
 * component:  - Select a component => Core Tor/Tor


Comment:

 Why do you expect a hidden service only to connect to exit relays?  Exit
 relays are ones that allow connections outside the Tor network; they are
 not relevant for hidden services.

--
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