[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #1827 [Tor Client]: binding a socket for 18.0.0.1 to learn our interface address is freaking out users
#1827: binding a socket for 18.0.0.1 to learn our interface address is freaking
out users
------------------------+---------------------------------------------------
Reporter: arma | Owner:
Type: defect | Status: new
Priority: normal | Milestone:
Component: Tor Client | Version:
Keywords: | Parent:
------------------------+---------------------------------------------------
Comment(by nickm):
Well, we could use the usual means to discover their DNS server, and if
that's in a non-private network, open a testing UDP connection to that
address. But that would be more error prone.
We could try changing the address to (say) 1.0.0.1 and hope that looks
less disturbing.
If we've opened any TCP sockets to public addresses at all, we could do a
getsockname() on them rather than on a UDP socket. This might be our best
bet. It would mean that we'd have to delay a little before coming up as a
router if we needed to guess our address.
We could file a bug report against "little snitch" and see if they can't
teach their software that connecting() a UDP socket doesn't actually send
any traffic.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1827#comment:1>
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