Opened 4 years ago

Closed 4 years ago

#12908 closed enhancement (fixed)

Warn when running a relay and a hidden service in the same process

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: 0.2.5.x-final
Component: Core Tor/Tor Version:
Severity: Keywords: 025-backport tor-hs tor-relay
Cc: txt.file Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


See discussion on #8743; gsathya has a patch there.

Child Tickets

Change History (8)

comment:1 Changed 4 years ago by nickm

Milestone: Tor: 0.2.6.x-finalTor: 0.2.5.x-final

I've put a tweaked version of gsathya's patch in "bug12908_025" in my public repository, and merged it to master. Marking for possible 0.2.5 backport.

comment:2 Changed 4 years ago by bastik

#8743 has no comments at all, it is the wrong ticket. 8734 can't be the ticket either.

I thought Tor would already warn, because everything on a relay is public.

comment:3 Changed 4 years ago by nickm

whoops. #8742.

comment:4 Changed 4 years ago by zax

Should this message be a more generic, "You're sharing a process between Hidden Services and other Tor functions"? People running, for example, a bridge also (quite correctly) get warned but then the message is slightly misleading.

It may also be the case that running multiple Hidden Services under a single process exposes a similar risk of leaking traffic info.

comment:5 Changed 4 years ago by arma

Merging a3fe8b1166 into 0.2.5 sounds fine to me.

There are actually a variety of reasons not to run your hidden service on a relay (or I guess bridge) -- the correlation of public up- and down-times is another one.
and that last one is even a more generic "reason not to use your relay or bridge as anything else".

So I'd be in favor of a more broad warning message here.

comment:6 Changed 4 years ago by nickm

Resolution: implemented
Status: newclosed

Merged into 0.2.5. Please feel free to commit a better warning message if you like.

comment:7 Changed 4 years ago by txt.file

Cc: txt.file added
Milestone: Tor: 0.2.5.x-finalTor: 0.2.4.x-final
Resolution: implemented
Status: closedreopened

Please backport this patch also to 0.2.4. I think that people which are running the current stable branch also want to be warned of insecure settings.

comment:8 Changed 4 years ago by nickm

Milestone: Tor: 0.2.4.x-finalTor: 0.2.5.x-final
Resolution: fixed
Status: reopenedclosed

These aren't getting backported. Recommended solution: upgrade to 0.2.5.x stable releases.

Note: See TracTickets for help on using tickets.