Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#6040 closed defect (invalid)

"Use a New Identity" behavior is non-intuitive and can lead to mistaken use

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

Description

When the "Use a New Identity" button is clicked, a notice pops up saying "All subsequent connections will appear to be different than your old connections." The "Use a New Identity" button then grays out for several seconds while the new identity is created. However, unless a user waits for the "Use a New Identity" button to not be gray, they will actually be browsing under the old identity. So the popup notification is incorrect, as it makes the user believe the identity has been established.

I think the behavior should be changed so that when the button is clicked, the popup notification lets the user know a new identity is being established. Then once it is established the user should be notified with another popup that the identity has changed.

Child Tickets

Change History (5)

comment:1 in reply to:  description Changed 8 years ago by arma

Replying to keystroke:
However, unless a user waits for the "Use a New Identity" button to not be gray, they will actually be browsing under the old identity.

No, this is incorrect.

Or at least, it is supposed to be incorrect.

comment:2 Changed 8 years ago by keystroke

Resolution: invalid
Status: newclosed

Thanks! You're right. I double checked and it turned out I wasn't testing it properly. I wonder why it stays gray for a bit but I guess it's to prevent multiple accidental clicks.

comment:3 Changed 8 years ago by arma

It's to prevent multiple intentional clicks. It hurts the network a tiny bit when you do it, since your client throws away its current circuits and makes new ones. If lots of people clicked it five times a second, the sum would be harmful.

comment:4 Changed 8 years ago by arma

All of that said, you really want to use the 'new identity' button in Torbutton, not the one in Vidalia. The one in Torbutton is better at killing keepalived connections.

comment:5 Changed 8 years ago by arma

I just opened #6042, because I think Torbutton doesn't handle the rate limiting of 'new identity' clicks correctly. Thanks.

Note: See TracTickets for help on using tickets.