Feature #6383

New Identity feature in the web browser

Added by intrigeri 2013-10-21 09:03:51 . Updated 2014-03-19 07:34:14 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2013-10-21
Due date:
% Done:

100%

Feature Branch:
winterfairy:bugfix/torbutton-new-identity
Type of work:
Code
Blueprint:

Starter:
0
Affected tool:
Browser
Deliverable for:

Description


Subtasks

Feature #6384: Filtering proxy for the Tor control port Resolved

80


History

#1 Updated by winterfairy 2013-10-30 05:29:48

This is a regression. Torbutton’s new identity feature worked in Tails 0.20.1 and previous versions. Now it is greyed out. The only other way to get a new identity is to restart Tails (Vidalia’s button doesn’t count), which mostly isn’t practical. => High priority?

And the ticket should be named “Torbutton new identity feature”. I couldn’t figure out how to rename it myself.

#2 Updated by winterfairy 2013-10-30 05:33:53

And add to known issue with this release, maybe?

#3 Updated by intrigeri 2013-11-01 03:18:21

  • Subject changed from Torbutton new circuit feature to New Identity feature in the web browser

#4 Updated by intrigeri 2013-11-01 03:23:57

winterfairy wrote:
> And add to known issue with this release, maybe?

Done.

#5 Updated by sajolida 2013-11-02 05:28:14

A workaround for the time being is to:

1. Close the web browser.
2. Right-click on the Vidalia icon and choose “New identity”.
3. Open the web browser again.

#6 Updated by fivalpea 2013-12-04 23:51:12

Bug still exists in 0.22~RC1 . I believe it is related to giving only admin access to tor control port (I tried to find the quote from .21 release but could not). This is a very annoying bug, and will be a security issue for many users who do not restart the browser each time, or even assume that because “new identity” is greyed out, it is not necessary.

#7 Updated by winterfairy 2014-02-11 09:48:29

  • Status changed from Confirmed to In Progress
  • Assignee set to anonym
  • Target version set to Tails_0.23
  • QA Check set to Ready for QA
  • Feature Branch set to winterfairy:bugfix/torbutton-new-identity

I believe I have fixed this issue, see branch “winterfairy:bugfix/torbutton-new-identity” (based on devel). It is made possible through a control port proxy that only allows SIGNAL NEWNYM.

#9 Updated by intrigeri 2014-02-21 19:41:49

  • Category set to 176

#10 Updated by anonym 2014-03-01 11:18:58

  • Status changed from In Progress to Fix committed
  • Assignee deleted (anonym)
  • QA Check changed from Ready for QA to Pass

Merged!

#11 Updated by anonym 2014-03-19 07:34:13

  • Status changed from Fix committed to Resolved