re CC and evercookie: if you read this very thread, and the ones linked you'd wonder why you asked this question, not trying to sound rude but could think of no other words to call this (thus the Demon/Meddler in my title).
Because there was no need for any change log. IIRC ccleaner was already cleaning at least 98% (est.), if not all*, of the problem areas at the time of the revelation of the Evercookie
…and now covers all aspects of the "cookie burst"
note: by using DuckDuckGo (thanks @hazelnut) instead of google/yahoo/bing you can, in settings, turn off referrer from search engines
Nergal, if that first "meddling" comment was directed at me, then I find it strange you would say that. Yesterday, I did indeed read this thread and the others linked and I came back to re-read them again this morning.
I have yet to find any definitive statement that CC will actually handle all evercookies. Maybe I am stupid and too dense to see it, but it certainly alludes me. I am an Engineer and I deal with facts and realities, not suppositions, "should" and/or "maybe."
It is for these reasons I was requesting a qualified statement of fact.
I have yet to find any definitive statement that CC will actually handle all evercookies. Maybe I am stupid and too dense to see it, but it certainly alludes me. I am an Engineer and I deal with facts and realities, not suppositions, "should" and/or "maybe."
As an engineer you should define your terms.
What did you mean by Evercookies.
What will they be tomorrow.
It is my understanding that the original known evercookies have evolved. They are not static.
Are you really asking for an assurance that the current version of CCleaner will handle all future cookies that may arrive through all browsers including those not yet developed ?
Do you as an engineer give categorical assurances about what may happen in the future ?
so I will just say this in the plainist words possible, and ones that are peppered throughout the entirity of all on these posts,
as well as the SUPERSIMPLE answer given in the FAQ which the OP linked in her initial post
CCleaner,at the time the Evercookie was first publicized and (granting that the make up of the EC is the same) now, removes all known traces of evercookie.
Honestly I think the FAQ really sums this up best
Does CCleaner combat regenerative cookies like EverCookie?
Yes.
perhaps we should change the words "combat regenerative cookies like EverCookie" to "completly remove all known traces of Evercookies and other EverCookie-like regenerative cookies", and this would avoid the confusion that seems to be abound.
Dogatmyfeet - easy now. Let's try to keep it polite. "Can't we all just get along?"
I think the answer to your question is there's no official claim by CCleaner that it will handle cleaning all evercookies (why would we be interested in "some"?). That doesn't mean it doesn't - or does, AFAICT.
Alan_B -what's wrong, man?!? Don't beat a newbie up. Maybe he could've phrased his question better, but your rhetoric about "will handle all future cookies..." What kind of a statement is that? How can any software claim to deal w/ any issue that hasn't been invented? The rest is just being contenscious. Help a brother out.
- DAMF - CCleaner apparently does find some evercookies. Maybe all in the (for now) normal hiding places, but AFAICT there's no official claim by any official Periform representatinve that CCleaner cleans all (known, at the present) evercookies.
I suppose one could intentionally go to sites known to be using them & try to get them set in all places listed on research sites, in the 12 - 15 or so places they can be stored & see what CCleaner finds. [one evercookie can be in 1, 2 or all 12 - 15 places at same time] My understanding from reading is, one cookie isn't usually stored in all possible locations. But to know if ANY cleaner can find all locations, something would have to exist in all locations. That would be a bit of work - just verifying they exist in all known locations, or creating them. Again, a bit of work
Alan_B -what's wrong, man?!? Don't beat a newbie up.
Sorry - I was not beating up a newbie.
I was responding as one software engineer to another engineer who required a statement of fact upon capability of defending against malware that is changing and therefore unknown.
What's the official statement of Piriform / CCleaner that states such? Maybe not listing all the locations as you did, but...
As w/ any product or business, non specific statements / claims like, "We do it all;" We clean up everthing;" "We're # 1," are legally & technically meaningless.
FYI, as I mentioned earlier, it doesn't find / clean webappstore.sqlite for me in Firefox, although I intentionally caused data to be saved there. Bleach Bit finds it, but it can't handle profiles in non-default locations (for now). Just sayin. I doubt any cleaning prgm could handle all locations that evercookies can be hidden (now), 100% of the time.
Since evercookies are set by scripts, their developers can continually change where they're hidden. Yes, they're hacking the browsers. They were from the moment they ignored browser settings of "disable all cookies," but set them anyway, like ANY OTHER malicious script. Browsers devs may plug that hole & trackers / data miners will find another way. They SHOULD be thrown in jail / fined HEAVILY, just like someone hacking a credit card co. But for $ome rea$on, authorities & brow$er dev$ have looked the other way, so far.
If you, ever, want an official statement (i.e. beyond the word of a moderator) then you will have to be extremely patient, as they rarely if ever take part in the conversations here.
Evercookie Developers can only change to locations that the client (your webbrowser) has access to. The above list is those locations
As I said, from any sort of "product features" (admittedly, often vague) statement, CCleaner apparently doesn't officially handle evercookies, in a reasonably complete way - as evercookies are known to exist / behave, at present. I know it doesn't (appear to) handle them completely for me.
As java scripts, they can do anything that any java script might be able to do, within the browser, or from a browser to the system or to other apps. They can do what ever the hell they want, w/in the confines of js abilities. Just because the developer of evercookie & other companies that are now using the technology have been "playing fairly nice" up to now (maybe to avoid jail), in no way predicts what they may stoop to in the future. I imagine true hackers will take it & really start doing some damage.
CCleaner really needs to deal with the Firefox user profile file "webappsstore.sqlite" if Piriform even know of it. I use a batch file and BleachBit to delete it.
We haven't been able to find any problems cleaning "webappsstore.sqlite". This is part of the Cookies cleaning for FF. Please, let us now which cookie in particular that you haven't been able to clean.
As far as evercookie (http://samy.pl/evercookie/), we also haven't found any issues. This is true for all supported browsers.
Please make sure that the following rules are also cleaned before going back to the evercookie page:
Thanks MrT Official Bug Fixer Bug Fixers (trying to make Login123, now "title-less", feel better)
I intentionally loaded some data in webappstore.sqlite in one "test" profile (located in same user acct as CCleaner was started under). It couldn't find that file. That profile was in the default location for FF. It didn't have an evercookie in it, but it had data. There're not many cleaners I know of that inspect the data inside, say an index.dat file, & decide if it needs / doesn't need cleaning. In fact, most times if files on the app's "to clean" list, exists at all - even empty - they find / delete them.
I'm not biased toward BleachBit. I use CCleaner far more often, but BB, for instance, did find that webappstore.sqlite file, in this case. I really don't know what the problem was.
Thanks MrT Official Bug Fixer Bug Fixers (trying to make Login123, now "title-less", feel better)
Thanks anna24. Very considerate of you. Back on topic, I avoid the more agressive "cleaners" out there. One little goof up, long time to fix it. CCleaner has always been good enough.