Opened 12 years ago

#551 closed defect (Works for me)

Torbutton 1.1 Disables Cookie Culler on different profile

Reported by: bledsoeo Owned by:
Priority: Low Milestone:
Component: Applications/Torbutton Version: 1.1
Severity: Keywords:
Cc: bledsoeo, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

I established a second user profile in Firefox 2.0.0.9 in order to allow the operation of Torbutton 1.1.10 without interfering with
my baseline web browsing extensions.

Regardless of its state of activation, the installation of torbutton 1.1.10 on the second Firefox profile caused my cookie manager
to cease useful function. I keep it set to delete all unprotected cookies upon exit of firefox, but with 1.1.10 installed, all
cookies were retained, and I needed to manually administer my cookies.

Firefox 2.0.0.9
Cookieculler 1.3.1

Please keep in mind, for most of my daily operations, a combination of Cookie Culler, Adblock, Flashblock, Remove It Permanently and NoScript
extensions give me the user experience that I want -

Suppression of tracking cookie installation
Selective execution of Javascripts
Selective execution of flash elements
Suppression of ad clutter
Automated cookie management

Quite frankly, the higher level of security offered by Torbutton 1.1.10 comes at a very high price in terms of ease of use for notmal daily web
browsing. If it could peacefully co-exist with other extensions in different profiles, then I could select the desired level of trade-off
between ease of use and improved security, depending on the tasks I need to perform.

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (1)

comment:1 Changed 11 years ago by mikeperry

flyspray2trac: bug closed.
Works for me on 1.2.0rc5 now. Perhaps the new cookie jar code fixed it?

Note: See TracTickets for help on using tickets.