Opened 4 years ago

Last modified 13 months ago

#17554 new enhancement

Addon to encrypt history and bookmarks

Reported by: cypherpunks Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I remember another ticket about this but cannot find it. Anyway, this addon seems to be the solution: https://addons.mozilla.org/en-US/firefox/addon/link-password/

It can encrypt both TBB history and bookmarks which is great especially considering both are without any kind of protection implemented.

Child Tickets

Change History (2)

comment:1 Changed 4 years ago by cypherpunks

Component: - Select a componentTor Browser
Owner: set to tbb-team

comment:2 Changed 13 months ago by traumschule

Type: defectenhancement

I just installed it and got a tab saying:

Welcome to Link Password 5.0
Hi and sorry for your inconvenience with Link Password in lately.
Long story short, Firefox recently release it Firefox version 57 that totally break the functionality in Link Password and I (Link Password developer) was forced to rewrite the addon from start to working with Firefox 57.
Unfortunately some functionality that exists early has to be change in Link Password 5.0 (due to Firefox 57 changes). The Link Password is now using ext+linkpassword:// as protocol any exiting encrypted bookmark your have should be updated to ext+linkpassword:// next time Firefox restarts.
Checkout the new icon for accessing options for encrypt and decrypt bookmarks folders.
Please leave any feedback or issue you have on https://addons.mozilla.org/firefox/addon/link-password/ and we can see what we can do.
Best Regards Link Password Developer.

A padlock symbol appeared in the toolbar. It offers a dropdown menu to encrypt four kinds of bookmarks. It asks for a password and offers to rename bookmarks to some nonsense. Clicking on an encrypted bookmark opens a tab but the connection never resolves. After decrypting everything is back to normal.

I see no privacy / fingerprinting issues here. Did not test persistence across sessions yet.

Note: See TracTickets for help on using tickets.