Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#3545 closed defect (fixed)

Private browsing mode should be disabled in TBB

Reported by: mikeperry Owned by: erinn
Priority: High Milestone: TorBrowserBundle 2.2.x-stable
Component: Applications/Tor bundles/installation Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Firefox private browsing mode currently prevents the user from setting various Torbutton options related to disk storage.

Right now private browsing mode also provides no benefit over default Torbutton settings. Furthermore, it will be relatively easy to take any useful future private browsing mode features we need on a piecemeal basis for the medium term future.

Long term, we've suggested to Mozilla that they provide private browsing mode options that are more compatible with how we want to do things (#3100). If/when this happens, we'll map our options to private browsing mode options.

Child Tickets

Change History (5)

comment:1 Changed 8 years ago by mikeperry

In the UI, the pref is located at prefs->privacy->Permanent Private Browsing Mode.. This appears to trigger a change of browser.privatebrowsing.autostart. Not sure if other prefs are involved? Perhaps you can just toggle that pref in the UI and save off the resulting prefs.js and diff?

comment:2 Changed 8 years ago by mikeperry

Priority: normalmajor

comment:4 Changed 8 years ago by cypherpunks

Now Firefox going to write and delete db's records over long live media. That true for downloads.sqlite. While it running a file download it keeps a record.

If db's file going to grow and shrink for big queued downloads then urls and local paths going to leak.

No such behavior if user_pref("browser.privatebrowsing.autostart", true);

comment:5 in reply to:  4 Changed 8 years ago by mikeperry

Replying to cypherpunks:

Now Firefox going to write and delete db's records over long live media. That true for downloads.sqlite. While it running a file download it keeps a record.

If db's file going to grow and shrink for big queued downloads then urls and local paths going to leak.

No such behavior if user_pref("browser.privatebrowsing.autostart", true);

Thanks. I checked the source and you appear to be right... Created #4017 for this issue. Kind of ridiculous this is the behavior even when browser.download.manager.retention = 0.

Note: See TracTickets for help on using tickets.