[tahoe-lafs-trac-stream] [tahoe-lafs] #1947: Tor clients share their IP with the introducer

[tahoe-lafs]

#1947: Tor clients share their IP with the introducer
--------------------------------+-------------------------------
     Reporter:  leif            |      Owner:  davidsarah
         Type:  defect          |     Status:  new
     Priority:  normal          |  Milestone:  soon
    Component:  code-nodeadmin  |    Version:  1.9.2
   Resolution:                  |   Keywords:  privacy anonymity
Launchpad Bug:                  |
--------------------------------+-------------------------------

Old description:

> I just found out that clients advertise their IP to the introducer!
>
> Storage servers on a hidden service grid will set their `tub.location` to
> their .onion address and send that instead, but clients do not need to be
> connected to so they don't have their own hidden services and won't set
> `tub.location`. (edit: unless they do set it to an unreachable address,
> which `configuration.rst` actually does say Tor clients should do, I
> realized after submitting this ticket.)
>
> I've been running a hidden service grid for a while and just now realized
> (via the screenshots in [https://tahoe-lafs.org/trac/tahoe-
> lafs/ticket/1931#comment:17 this comment]) that the introducer has a list
> of clients. I have not yet restarted my introducer to enable its wui to
> confirm that Tor clients are listing their IPs there, but I don't see why
> they wouldn't be since they don't have `tub.location` set.
>
> Is there any reason clients need to tell the introducer their addresses
> at all?
>
> I think the section of `configuration.rst` that mentions hidden services
> should include a caveat about how Tahoe is not yet actually ready for
> anonymous use, mentioning this issue as well as #1942.
>
> I'm setting the milestone to 1.10 in hopes that this documentation change
> can make the upcoming release.

New description:

 I just found out that clients advertise their IP to the introducer!

 Storage servers on a hidden service grid will set their `tub.location` to
 their .onion address and send that instead, but clients do not need to be
 connected to so they don't have their own hidden services and won't set
 `tub.location`. (edit: unless they do set it to an unreachable address,
 which `configuration.rst` actually does say Tor clients should do, I
 realized after submitting this ticket.)

 I've been running a hidden service grid for a while and just now realized
 (via the screenshots in [https://tahoe-lafs.org/trac/tahoe-
 lafs/ticket/1931#comment:17 this comment]) that the introducer has a list
 of clients. I have not yet restarted my introducer to enable its wui to
 confirm that Tor clients are listing their IPs there, but I don't see why
 they wouldn't be since they don't have `tub.location` set.

 Is there any reason clients need to tell the introducer their addresses at
 all?

 I think the section of `configuration.rst` that mentions hidden services
 should include a caveat about how Tahoe is not yet actually ready for
 anonymous use, mentioning this issue as well as #1942.

 I'm setting the milestone to 1.10 in hopes that this documentation change
 can make the upcoming release.

--

Comment (by zooko):

 I think this is a duplicate of #1010. Could someone verify if that's
 correct, and close this ticket with status "duplicate", and add a comment
 on #1010 asking people who read #1010 to come read this ticket too?

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1947#comment:5>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage