You have to decide a balance of usefulness to a legitimate operator and privacy concerns. I could just as easily run Wireshark or TCPDump on my relays and get client IP Addresses that way. You are trusting most operators, like me, are the good guys. Of course a client IP isn’t very useful without a way to associate exit traffic to them.
Cordially, Nathaniel
On Mon, Sep 3, 2018 at 4:14 PM arisbe arisbe@cni.net wrote:
Hello ops,
Today I noticed something on NYX that I find disturbing. Page 2 (list of inbound/outbound connections) showed me the IP address of an inbound connection on one of my bridges! Not the authority. This is crazy as these are indicated as <scrubbed>:port for the users protection! I have never seen this before and haven't seen it since. Of course, on low usage bridges, the connection IP address can possibly be disseminated from netstat but that's not the point. It's my sense that this should never happen. I get chills imagining this happening on a guard relay operated by an antagonist ! !
I'm using the default NYX configuration on Ubuntu server 18.04.1 LTS, Tor 0.3.3.9.
Arisbe
-- One person's moral compass is another person's face in the dirt.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays