Please support Pale Moon 27 Bewertet mit 5 von 5 Sternen

This extension is a Jetpack SDK extension and thus is incompatible with Tycho (Pale Moon 27). The extension will have to be rewritten to use supported technologies such as pure Toolkit or Bootstrap.

Can you make this please?

Configure SDC "hidden setting" and block the Google NID "spy" cookie in FF 47 Bewertet mit 5 von 5 Sternen

Salutes to SDC Developer Ove Sörensen and his brilliant extension. This review is for the benefit of any users who have no objections to taking extra steps for a higher level of cookies policy and privacy. Thanks to input from another SDC reviewer, this review replaces a previous review to correct inaccuracies that failed to address properly the distinction between Local Shared Object (LSO) flash cookies and localStorage (DOM storage, or Web storage).

In my experience, the SDC "hidden setting" allows SDC to function consistently and reliably at the highest level if FF has the following settings in Preferences/Privacy/History:
- Firefox will: Use custom settings for history
- Always use private browsing mode: disable
- Accept cookies from sites: disable

Enable the SDC "hidden setting" -- On the SDC home page, in the last paragraph in the "About this Add-on" section, follow the instructions to create a new boolean key in Firefox/about:config. After enabling the "hidden setting", how cookies behave when you click one of the 3 primary SDC toolbar menu options actually will be very different from what each option's text label indicates. Cookies will conform to the following behaviors:

(1) red icon with the label "after you close its tabs" - SDC and FF actually will block this specific site's cookies every time you connect to this site.

(2) yellow icon with the label "after you close the browser" - SDC and FF always will allow this specific site's cookies temporarily for the session, and this specific site's cookies always will self-destruct when you end the session by either (a) closing this site's tab or (b) quitting Firefox. (Note: if two or more tabs are open in Firefox, or if you have installed another Firefox add-on, such as Tab Mix Plus, which prevents Firefox from quitting when you close the last Firefox tab, you do not have to quit Firefox for the site's cookies to self destruct. You only need to close the site's TAB for the site's cookies to self destruct, and the Firefox browser will remain open with the other tabs(s)).

(3) green icon with the label "never"- SDC and Firefox always will allow this specific site's cookies and will never delete this site's cookies.

Google NID and Google PREF persistent tracking cookies --
The problem: every time you delete the PREF and NID cookies, they reappear within seconds or minutes, even when you have no Internet connection. To remove and block the NID and PREF cookies, remove all google.com cookies. Go to FF/Preferences/Security. Uncheck "Block reported attack sites". Uncheck "Block reported web forgeries". Go to FF/Preferences/Privacy/Exceptions. In the "Address of website:" space bar, type google.com. Click Block. Click Save Changes. Go to Firefox/about:support. Click "Show in Finder". Your current Profile Folder will open in a Finder window. In your Firefox Profile Folder, locate the "cookies.sqlite" file. It contains programming that persistently is re-installing the PREF and NID cookies each time you delete them. Delete the "cookies.sqlite" file. Warning: deleting "cookies.sqlite" will delete all Firefox cookies. Restart Firefox. It will create a fresh "cookies.sqlite" file, which will not re-install the Google NID and PREF cookies unless you do some combination of the following: enable "Block reported attack sites", enable "Block reported web forgeries", log in a Google account, log in a YouTube account, enable google.com cookies for a Google search.

PRIVACY - reasons for disabling "Block reported attack sites" and "Block reported web forgeries" -
"Safe browsing": http://kb.mozillazine.org/Safe_browsing describes how these settings work. After enabling the settings, clicking on a link causes FF to ask a Google server whether that link is suspicious. Google can use such inquiries to track your Internet activities, build a profile on you, and sell, trade, or share your profile with corporations and government agencies. If you enable the settings, the PREF and NID cookies are likely to install in FF even if you have no Internet connection and deleted them in the past few seconds or minutes.
- Browser Spying: http://www.unspyable.com/browser_spying.htm
- Leave Google Behind: https://www.leavegooglebehind.com/how-tos/how-to-eradicate-google-from-firefox/.
- Firefox "block reported attack sites" privacy?: http://kernelreloaded.blog385.com/index.php/archives/firefox-block-reported-attack-sites-privacy/

Three useful web sites quickly will test any link so you can determine whether a link is authentic, secure, risky, or has malware. The three sites do not require you to enable "Block reported attack sites", "Block reported web forgeries", the PREF cookie, the NID cookie, or any other cookies, and the sites do not track you when you run the tests:
- virustotal: https://www.virustotal.com/#url
- SSL Server Test: https://www.ssllabs.com/ssltest/
- GRC Fingerprinting: https://www.grc.com/fingerprints.htm

The NSA and Google tracking cookies --
Several years ago, the U.S. National Security Agency (NSA) began using the Google PREF persistent tracking cookie as a digital beacon to track individual Internet users. To the best of my knowledge, at that time, only the Mozilla Firefox and Google Chrome browsers could catch the PREF cookie. The Google NID persistent tracking cookie is a newer and possibly more technologically advanced tracking cookie than the older-generation Google PREF cookie.

How to determine whether the PREF or NID cookies are in FF 47x --
Go to FF/Preferences/Privacy. Enable the setting "History | Firefox will: Use custom settings for history". Click on "Show Cookies..." In the Cookies window, in the Site column, find the domain name "google.com". On the left-side of "google.com", click the black triangle to expand the column beneath google.com, which will show an indented list of google.com cookies. In the Cookies window, look in the Cookie Name column. If you see the name PREF or NID, your browser has caught a Google persistent tracking cookie.

The Washington Post -- NSA uses Google cookies to pinpoint targets for hacking:
https://www.washingtonpost.com/news/the-switch/wp/2013/12/10/nsa-uses-google-cookies-to-pinpoint-targets-for-hacking/

The Wall Street Journal -- The Google Cookie That Seems to Come Out of Nowhere:
http://blogs.wsj.com/digits/2012/02/28/the-google-cookie-that-seems-to-come-out-of-nowhere/

NSA Using Google Non-Advertising Cookie to Spy:
https://threatpost.com/nsa-using-google-non-advertising-cookie-to-spy/103162/

How to remove the persistent Google PREF super cookie [and now, the persistent Google NID super cookie]:
https://stackoverflow.com/questions/6301114/how-pref-cookie-google-com-appears-in-firefoxput

Dieser Benutzer hat 4 ältere Bewertungen zu diesem Add-on.

ST reviews contain false statements Bewertet mit 4 von 5 Sternen

@Skepp Tikal: It would be really great if you could refrain from posting great walls of text that repeat essentially the same essay on the SDC "hidden setting" over and over again. You've done it at least 7 times now and it serves little purpose to others but to bury other reviews. You may wish to use the time saved to research the subject of cookies a little more. Local shared objects (LSO) are also known as flash cookies, created only by the flash player plug-in. BetterPrivacy manages LSOs only. You've uninstalled the flash plug-in and still use BetterPrivacy, which is utterly pointless. HTML5 introduced a new sort of 'cookie' that has nothing to do with LSOs and nothing to do with regular cookies. This new type is referred to as "Web Storage", but is also referred to as "DOM Storage" or "Local Storage" and it resides in the webappsstore.sqlite file found in your Firefox profile. Notice how Ove documents that SDC manages both regular cookies and "has LocalStorage support". LSO and Local Storage are NOT the same thing. BetterPrivacy does NOT manage Local Storage, but SDC does, so why do you tell us that you disable SDC LocalStorage functionality and instead use "BetterPrivacy to manage _LocalStorage_ flash cookies"? Those aren't the same thing. Again, LocalStorage cookies are NOT flash cookies. There is no such thing as "LocalStorage flash cookies". You are either very confused or simply don't know that Local Storage exists as an entirely different thing from LSOs. As far as I can tell, there is no overlap between SDC and BetterPrivacy. As for your enthusiastic and repeated promotion of the "hidden setting', there are many of us who would like to block the Google NID cookies that slip past SDC's default configuration, but we don't want to change the meaning of the red/yellow/green SDC icons, we don't want to obliterate all our other cookies by deleting cookies.sqlite, and we aren't interested in an unreliable and convoluted workaround of the sort you keep suggesting. None of that should be necessary. There should be no reason to lose the benefits of Firefox's "Block reported attack sites" and "Block reported web forgeries" protections. All we need is for SDC to be enhanced to block all cookies that are not associated with user browser tabs.

A plea to Ove Bewertet mit 4 von 5 Sternen

I've tested SDC and it's almost everything I could want for myself and all the users I support. Much easier to use than any other cookie manager I've tried. The concept is brilliant. My intention was to convert all the Firefox profiles I support from Cookie Monster to SDC, and that's when I learned about background cookies not being managed at all by SDC. Google is the single worst cookie abuser on the planet, so seeing background Google NID cookies go right past SDC was a deal breaker.

Please, Ove, please enhance SDC such that all background cookies and localStorage super cookies are always blocked by default. Can there ever really be any positive use for background cookies/localStorage?

I don't know about other cookie managers, but Cookie Monster fails to delete localStorage super cookies when deleting regular cookies, so I'm eager to change, but that fault isn't as bad as allowing background cookies through.

4 stars because for people who already allow persistent Google cookies, SDC is quite good, but it's fatally flawed for those that don't and for those of us who also worry about extensions, plug-ins, and other Mozilla functionality that do background access to arbitrary other websites.

No access to settings? Bewertet mit 5 von 5 Sternen

Are using this extension for a long time but recenty are having problems with access settings menu i Android?
Please fix the bug...

Recommended Bewertet mit 5 von 5 Sternen

I would definitely recommend this add-on for anyone concerned with cookies and privacy. Set it up and forget all about cookies - they will work fine as long as you stay on a site - and then, poof, they're gone!

Essential but not witout flaws Bewertet mit 4 von 5 Sternen

Really essential for privacy minded folks who keep the browser running for a long time.

Adding domains to the whitelist with the addon icon is somewhat broken. Domains will always be added without a non standard port. I recommend using the Firefox native UI.

Awesome!! Bewertet mit 5 von 5 Sternen

A must have and must say *Thanks so much* this is super great!

to much good Bewertet mit 5 von 5 Sternen

thx

arkayanag Bewertet mit 2 von 5 Sternen

i read a lot and , since installing this add-on, i have to continually reload the page to continue reading.
i cannot find where to remove this add-on

Great but... Bewertet mit 3 von 5 Sternen

...I'll have firefox completely blank, no page is loaded at all. I disabled top sites. I close the last tab, cookies, etc, get removed, but sometimes there will be a persistent google NID and/or mozilla add ons cookie. OSX 10.9.5, fx 47.01.

A Thoughtfully Written, Highly Useful Extension Bewertet mit 5 von 5 Sternen

… and a fine complement to Adblock in my case. I would suggest only one thing, and it wouldn't really be a change so much as an added setting : allowing the user to choose, via toggle switch or something like that in the add-on's settings, whether the extension should function by default as it does now, i.e. immediately destroying a site's cookies when the site is exited, or, at the user's discretion, if it should work the other way around, i.e. leaving a site's cookies intact until/unless the user instructs the add-on to destroy that site's cookies on exit. In other words, giving the user the choice to have new sites default to the GREEN icon rather than the RED icon. Letting the user choose which of those two modes of operation he would prefer to see the extension default to shouldn't involve too much extra coding and would be good for users who, say, have no problem letting 95% of cookies remain and only want to block those from a handful of sites.

That said, I suspect that idea goes against the very ideology, thrust, and/or purpose of the developer in creating this add-on, who would see me tar-and-feathered before implementing it :)

No matter, it's still a full  ★★★★★  rating as is, far as I'm concerned.

Works great Bewertet mit 5 von 5 Sternen

Deletes cookies after all tabs that use them have been closed with a short delay. This works great as an additional measure to avoid tracking without the hassle of other extensions that outright block cookies.

Sites where you want to stay logged in can be easily white-listed.

you want me to manually find and check 2688 cookies and type into the whitelist??? Bewertet mit 2 von 5 Sternen

This is a great idea. When I installed it, i liked the "tutorial" showing what it does and how to undelete/suspended the cookies, but NO LIST of them is available! I can't even begin to use this as I will lose all my important cookies, it would take me days to find them, load the web pages, or type them in.

Suggestion: (a lot to ask, I know...) any possibility of showing a list of the deleted/suspended cookies with checkboxes to move them to whitelist?

Great extension for privacy conscious people Bewertet mit 4 von 5 Sternen

Great extension. My only problem is that it is not possible to configure the extension in firefox for android. It can be installed but the only way to use it is with standard configuration parameters, which means there is no way to avoid the notifications when cookies are deleted.

bug Bewertet mit 3 von 5 Sternen

If you use hundreds of opened (unloaded) tabs as kind of history this addon still allows those sites to be active via their cookies and possibly scripts. Browser start takes much longer than in times of manual cookie management. It sucks and I'm still looking for something better. + It does a decent job in destroying tracking cookies

great add-on Bewertet mit 4 von 5 Sternen

have been using this add on for quite some time and it really does a great job at managing cookies. Just recently though I've realized on linked in does not allow to manage the cookie whatever I choose...any help with that?

Excellent - keeps me in Firefox Bewertet mit 5 von 5 Sternen

This cookie management plugin is brilliant. Unlike others, which require you to manually whitelist every site you need to give cookie permissions to, Self-Destructing Cookies keeps the web running smoothly and your privacy protected by allowing sites to set cookies, but deleting them automatically when you're done using them. The toolbar button makes adding exceptions quick and simple.

This plugin is the #1 reason Firefox is still my default browser.

Ove, thank you so much for this wonderful piece of software.

Get over the setup and enjoy the safety Bewertet mit 5 von 5 Sternen

Yes it deletes all your cookies by default at the start. But that's a good thing in the long run. I would like synchronization of the white list between different machines please, otherwise it's fantastic.

part of the must-have add-ons Bewertet mit 5 von 5 Sternen

This add-on allows you to choose which site can keep cookies and the rest are automatically deleted. It's an excellent tool and, to be honest, this should be a part of the built-in functionality of the browser.

Dieser Benutzer hat eine ältere Bewertung zu diesem Add-on.