So far, the developers have kept mum on how the above hiding & un-hiding act is effected (ie. You can block the above web domains using the Windows HOSTS file or a firewall, but this is akin to a whack-a-mole exercise, since Piriform/AVAST can change the URLs at will.Īlso from v () onwards, CCleaner upon every launch auto adds (& re-adds) additional “whitelisted” cookies to keep:ģ) Furthermore, users have complained about sections of “experimental” features mysteriously appearing, disappearing & re-appearing in CCleaner’s GUI between launches, even though they have not updated CCleaner, & the file hashes of the main binaries ( CCleaner.exe, CCleaner64.exe) remain unchanged.
Ccleaner portable paf zip#
Note:- For each version, identical CCleaner.exe & CCleaner64.exe binaries are used for the 3 respective builds from the developer: “Standard” (PUP-bundled) installer, “Slim” (no PUPs) installer, as well as the Portable ZIP archive.Īs such, if CCleaner binaries were to be again tainted at source - ala the Floxif/Nyetya backdoor trojan supply-chain hack (which Piriform, AVAST & practically all malware scanners failed to detect) - ccPortable PAF would be equally compromised as well.Ģ) As for data mining & user privacy issues, CCleaner from v (released: ) onwards is known to connect to various URLs during its runtime, such as:ĬCleaner sends info such as the user’s IP address, ISP name, GPS coordinates, city/country, timezone, CCleaner launch timestamps, views, button clicks, types of junk cleaned from system, other running apps when CCleaner is is use, etc. The wrapper happens to extract the binaries contained in the “Standard” installer build from the developer. Daraghy: “How does the use of ccPortable address the issues of data user collection and bundling that tainted cCleaner to begin with for many of us?”ġ) ccPortable PAF does NOT prevent user data mining by the recent versions of CCleaner, because the PAF wrapper does not modify the binaries obtained from source.
0 kommentar(er)
