On 10/31/2009 11:59 AM, Rufus wrote: > David E. Ross wrote: >> Is there some way to lock the cookies so that subsequent browsing does >> not change existing entries? With SM 1.1.x, I originally set >> cookies.txt to read-only. When a bug was introduced that caused >> read-only settings to be ignored, I then created a backup file called >> cookies.bak.txt; before launching SM, I would execute a script that >> would copy cookies.bak.txt over cookies.txt. Since cookies are now in >> an squlite database, this won't work. >> >> This is especially wanted while I browse bug reports in the >> bugzilla.mozilla.org database. I had a set of default cookies that >> caused Bugzilla to display in a certain way. If I changed a display, it >> would be only for that one session. Now if I change a display, that >> becomes the default display the next time I enter Bugzilla because my >> cookies are changed. >> >> For example, when I login, I want the short "Find a Specific Bug" >> display. However, if the last thing I did was run an advanced search, >> my next login gives me the long "Advanced Search" display. As another >> example, I want the default for query lists to be by bug number. If I >> do a sort on status, that now becomes my default. >> >> How can I lock a set of default cookies so that they will be in effect >> the next time I launch SeaMonkey? >> > > What I do is to wipe out all cookies (or at least any I don't want to > keep) using the Cookie Manager, then set to "allow all cookies" or > "allow cookies from originating website only" and "accept cookies > normally" and navigate to all of the sites I want to "lock in" - > starting with my Home page. Then close SM. > > Then I reopen SM and go back to the Cookie Manager and delete any delete > any which show up that I don't wish kept. Then close/open, and set > cookies to "accept for current session only". > > After that, SM will retain a stable known set of cookies (within that > set's expiration defaults) at startup, as it will now wipe all newly set > cookies on session exit. This works (I've been doing this for years), > and is another security management method for SM that I often recommend > to colleagues at work. > > I generally do this for new/fresh installs of SM, or when changing site > entry passwords that could be stored in a cookie with a "keep me logged > on" option. You can also set the "ask for other than session cookies" > pref so that you can add more on the fly if you wish, but I don't do > that myself. >
I tried that. However, some of the cookies that I want kept get changed by some of the pages I visit. (This is definitely true when looking at bugzilla.mozilla.org bug reports.) When I then end the session, those changed cookies get deleted. Nothing remains of the original settings for those cookies. No, I haven't tried this with SM 2. The above describes what I experienced with SM 1.1.x. I will try it with SM 2 to see if this situation has changed. -- David E. Ross <http://www.rossde.com/> Go to Mozdev at <http://www.mozdev.org/> for quick access to extensions for Firefox, Thunderbird, SeaMonkey, and other Mozilla-related applications. You can access Mozdev much more quickly than you can Mozilla Add-Ons. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
