Opened 7 years ago

Closed 6 years ago

#2644 closed defect (fixed)

Choosing to relay should not default to being an exit

Reported by: StrangeCharm Owned by: chiiph
Priority: Medium Milestone: Vidalia: 0.2.15
Component: Archived/Vidalia Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

In the 'Sharing' tab on Vidalia, there are three choices:
-Run as a client only
-Relay traffic for the Tor network
-Help censored users reach the Tor network

The second option creates an exit node, not just a middleman relay. A user has to manually go to the 'Exit Policies' sub-tab and un-check all the boxes if they only want to be a middleman.

Running a non-exit relay is very easy, requires almost no work, and is unlikely to create trouble for the user. Running an exit takes a much more considerable amount of work, and can make life very difficult if the user isn't expecting it. Since only prepared or experienced users should consider being exits, it makes more sense to make non-exit relays Vidalia's default.

To further reinforce this point, perhaps setting up an exit should be accompanied by a more extensive disclaimer, referencing /Tips for Running an Exit Node with Minimal Harassment/, or a similar resource. I suspect that many folks avoid running relays because they use these default options, receive a nasty letter from their ISP, and don't realize that they can run a non-exit relay instead. Another choice to reduce the pain (and therefore attrition rate) of exits might be to offer the "reduced exit policy' as an option out of the box, rather than forcing the user to find and implement those resources on their own.

Child Tickets

Change History (13)

comment:1 Changed 7 years ago by arma

Summary: Chosing to relay should not default to being an exitChoosing to relay should not default to being an exit

I think we should change the Vidalia sharing window to have four options:

A) Be a client
B) Be a bridge
C) Be a non-exit relay
D) Be an exit relay

That way we let people set up relays without surprising them that there's a hidden tab they ought to know about and click.

comment:2 Changed 7 years ago by chiiph

Milestone: Vidalia-0.3.X

I'm not sure adding an option for non-exit relay will be the best idea.

May be, having all boxes unchecked in "Exit Policies" by default for being a relay, and explain in few words that like that you are just relaying traffic _inside_ the Tor network, and to relay to the outside you'd have to check some or all the checkboxes in the Exit Policies tab. And refer them to more help resources as StrangeCharm suggested.

Opinions?

comment:3 Changed 7 years ago by chiiph

Status: newneeds_review

So, I thought about this a little bit more, and I agree with arma. If a user wants to start contributing by being a relay, he/she might aswell learn a little bit about what's what.
So I've worked on this in my branch chiiph/bug2644_share.

Here's the commitdiff:
https://gitweb.torproject.org/chiiph/vidalia.git/commitdiff/552ea29ed456c9275f075863b15166135ddb3967

comment:4 Changed 7 years ago by chiiph

Resolution: implemented
Status: needs_reviewclosed

comment:5 Changed 7 years ago by chiiph

This will be on 0.3.0-alpha.

comment:6 Changed 6 years ago by rransom

Milestone: Vidalia-0.3.X
Priority: majorcritical
Resolution: implemented
Status: closedreopened
Type: enhancementdefect

Vidalia 0.2.12 still defaults to a fully open exit policy when I set 'Relay traffic for the Tor network'.

comment:7 Changed 6 years ago by Sebastian

eh, it was never promised for 0.2.x, right?

comment:8 Changed 6 years ago by chiiph

Resolution: fixed
Status: reopenedclosed

Exactly.

comment:9 Changed 6 years ago by chiiph

Milestone: Vidalia: 0.2.15
Priority: criticalnormal
Resolution: fixed
Status: closedreopened

It seems that this is one of those features a lot of people think is worth backporting. So I'll work on this for 0.2.15.

comment:10 Changed 6 years ago by chiiph

Status: reopenedneeds_review

The changes for this are in my branch chiiph/feat2644_backport

comment:11 Changed 6 years ago by arma

Looks like this got merged into 0.2.15 but never closed?

comment:12 Changed 6 years ago by arma

See also #4642 for what appears to be a bug in this patch.

comment:13 Changed 6 years ago by chiiph

Resolution: fixed
Status: needs_reviewclosed

This was merged and released with 0.2.15

Note: See TracTickets for help on using tickets.