Re: [tor-bugs] #10518 [Tor]: local tor client policy remotely modified

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#10518: local tor client policy remotely modified
------------------------+------------------------------
     Reporter:  mr-4    |      Owner:
         Type:  defect  |     Status:  new
     Priority:  normal  |  Milestone:
    Component:  Tor     |    Version:  Tor: 0.2.4.18-rc
   Resolution:          |   Keywords:
Actual Points:          |  Parent ID:
       Points:          |
------------------------+------------------------------

Comment (by mr-4):

 Replying to [comment:1 cypherpunks]:
 > It sounds like the exit node in question happens to be rejecting the
 site/port/whatever you want to access or he tried out this exit policy and
 decided to change it back.
 I doubt that. The node in question is "stable" and a "guard" and has also
 been running for a long time (I use it for that kind of traffic for more
 than 2 years now).

 > It's not related to your local tor client's "policy". It's related to
 the exit node's ExitPolicy.
 Yeah, that's right, but is it possible that my tor client could have that
 node's exit policy "changed" in its local copy/consensus?

 I presume that node's policy is downloaded and kept in /var/lib/tor, so if
 the local copy has been changed somehow, then I am going to get this kind
 of behaviour, right (which is the reason I submitted this report)?

 I don't see any sense in the operator of that node changing its node
 policy for 10-15 seconds (bearing in mind that that same policy has been
 like that for years!) only to then change it back to what it was.
 Something is fishy and I don't like it!

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/10518#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs