Feature #7226

Document the "New identity" feature in the browser

Added by BitingBird 2014-05-12 14:45:11 . Updated 2015-02-24 22:10:42 .

Status:
Resolved
Priority:
Normal
Assignee:
BitingBird
Category:
Target version:
Start date:
2014-06-29
Due date:
% Done:

100%

Feature Branch:
doc/7226-torbrowser_new_identity
Type of work:
End-user documentation
Blueprint:

Starter:
0
Affected tool:
Browser
Deliverable for:

Description

https://tails.boum.org/doc/anonymous_internet/Tor_Browser/index.en.html doesn’t mention this option, while many users ask what is does.


Subtasks

Feature #7709: Document browsing clipboard erasure on "New identity" Resolved

100

Bug #7470: Update warning on new identity now that this feature exists in the browser Resolved

100


Related issues

Related to Tails - Feature #7471: Display a warning notification if the new identity feature is used Rejected 2014-06-29

History

#1 Updated by sajolida 2014-05-13 04:51:29

Sure. It’s not mentioned in the browser doc.

Maybe we could copy the warning from the Vidalia doc:

https://tails.boum.org/doc/anonymous_internet/vidalia/#index4h1

#2 Updated by intrigeri 2014-05-13 05:24:23

> Maybe we could copy the warning from the Vidalia doc:

On the one hand, I’m inclined to trust the Tor Browser’s new identity
feature to separate web contextual identities. And I would hate it
to see people think that with TBB, they’re safe to use this feature,
while in Tails, they have to bother rebooting. So, copying the
Vidalia’s warning feels just wrong.

On the other hand, if we don’t want to dive into the complexity of
explaining that this feature only affects web contextual identities,
copying the warning is the right way to go.

I’m torn.

(Note that the web identities are already isolated from the non-web
ones, thanks to our stream separation setup.)

#3 Updated by BitingBird 2014-06-09 15:34:16

  • Status changed from New to Confirmed

#4 Updated by BitingBird 2014-12-03 17:53:23

  • Status changed from Confirmed to In Progress
  • QA Check set to Ready for QA

#5 Updated by BitingBird 2014-12-03 18:11:37

  • Target version set to Tails_1.2.2
  • Feature Branch set to bitingbird:doc/7226-torbrowser_new_identity

#6 Updated by BitingBird 2014-12-03 18:11:48

  • Assignee set to sajolida

#7 Updated by sajolida 2014-12-11 15:40:44

  • Assignee changed from sajolida to BitingBird
  • QA Check changed from Ready for QA to Dev Needed

Thanks for the patch.

First, I had the same Git problems as with Bug #7118. So please do reset your branch in the same way.

Then, it is not clear to me how your patch answer intrigeri’s concern from comment #2. You are not refering at all to browser state in your patch (cookies, cache, history, etc.) but merely to Tor connections.

I think that it is good to link to the “new identity” section of the TBB design document but it’s pretty hard to read and I’d rather explain what it does to the user in simple terms as well. As we are quite often answering questions about cookies for example, so this is something that people understand and wonder about.

#8 Updated by sajolida 2014-12-11 15:42:15

  • related to Bug #7470: Update warning on new identity now that this feature exists in the browser added

#9 Updated by sajolida 2014-12-11 15:53:22

Ah, and I also wonder how this relates to Bug #7470.

I’m wondering whether we should move the paragraphs that explain the “New identity” features of Vidalia and Tor Browser respectively to the Vidalia and Tor Browser documentation directly. And then have the warning page point there (instead of having it the other way around).

If you think that this is a good idea, please either do it straight away in this branch or create a ticket about it.

#10 Updated by sajolida 2014-12-11 16:49:24

  • Feature Branch changed from bitingbird:doc/7226-torbrowser_new_identity to doc/7226-torbrowser_new_identity

#11 Updated by anonym 2014-12-12 16:41:55

  • Target version changed from Tails_1.2.2 to Tails_1.2.3

#12 Updated by BitingBird 2014-12-19 13:15:48

Yes, it’s probably better to document the “new identity” in the Vidalia and Tor Browser documentation directly. I would like to keep it in the warnings though, but I know that duplicating information is not good, so a link might be good enough. I’ll go back to it.

#13 Updated by BitingBird 2015-01-03 04:37:21

  • related to Feature #7471: Display a warning notification if the new identity feature is used added

#14 Updated by BitingBird 2015-01-08 05:35:44

  • Target version changed from Tails_1.2.3 to Tails_1.3

#15 Updated by BitingBird 2015-01-15 03:26:39

  • Assignee changed from BitingBird to sajolida
  • QA Check changed from Dev Needed to Ready for QA
  • Feature Branch changed from doc/7226-torbrowser_new_identity to bitingbird:doc/7226-torbrowser_new_identity

My new commit improves things. It only documents TBB’s new identity feature, in the TBB-dedicated doc page.

Vidalia’s new identity feature will be documented in vidalia’s doc page, see Bug #7470

#16 Updated by BitingBird 2015-01-20 00:13:15

Built the wiki, everything works - i added a commit on top to change “reboot” to “restart Tails”. Including the image of the “new identity” feature would be great, but i won’t be the one to do it.

#17 Updated by BitingBird 2015-01-26 14:50:00

  • related to Feature #7709: Document browsing clipboard erasure on "New identity" added

#18 Updated by sajolida 2015-02-23 13:17:54

  • related to deleted (Feature #7709: Document browsing clipboard erasure on "New identity")

#19 Updated by sajolida 2015-02-23 13:18:32

  • related to deleted (Bug #7470: Update warning on new identity now that this feature exists in the browser)

#20 Updated by sajolida 2015-02-23 13:23:13

  • Tracker changed from Bug to Feature
  • Assignee changed from sajolida to BitingBird
  • Target version changed from Tails_1.3 to Tails_1.3.2
  • Feature Branch changed from bitingbird:doc/7226-torbrowser_new_identity to doc/7226-torbrowser_new_identity

I pushed fd7437d..06d3f8b on top of that.

That’s too much work for me to merge it without you having a lot at the result first. So postponing to 1.3.1, but we’re almost there!

#21 Updated by BitingBird 2015-02-23 22:02:33

  • Target version deleted (Tails_1.3.2)
  • QA Check changed from Ready for QA to Pass

I had a look at all your commits. I think you really improved what I did and that would be great to merge.

#22 Updated by Tails 2015-02-24 08:18:47

  • Status changed from In Progress to Resolved

Applied in changeset commit:44b8986096ba4816d20bbd310ecf4cc9f29d853e.

#23 Updated by BitingBird 2015-02-24 22:10:42

  • Target version set to Tails_1.3