[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #1859 [Tor Client]: Using 'mytorexitnode.exit' request when mytorexitnode is both exit and client
#1859: Using 'mytorexitnode.exit' request when mytorexitnode is both exit and
client
------------------------+---------------------------------------------------
Reporter: mwenge | Owner:
Type: defect | Status: needs_review
Priority: normal | Milestone:
Component: Tor Client | Version: Tor: 0.2.2.12-alpha
Keywords: | Parent:
------------------------+---------------------------------------------------
Comment(by tractor):
Replying to [comment:21 mwenge]:
> You're right, but the above is a separate bug I think. (And an extremely
good spot!) It will happen any time a someone running a default-configured
Vidalia exit and a client clicks or uses a link ending 'Unnamed.exit'.
They'll end up using their own exit as exit. Ouch.
>
> If the solution to this bug doesn't fix it, it should be opened as a new
bug. It probably merits separate consideration.
>
router_get_by_nickname() returns NULL for Unnamed nickname, default-
configured Vidalia exit relays non affects by this case. Only those relays
with Unnamed flag in consensus.
There are could some another edges which probably missed, that was most
simple for imagination.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1859#comment:24>
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