The revoked certificate still being used in CCleaner Cloud

Thumprint(SHA1) F4BDA9EFA31EF4A8FA3B6BB0BE13862D7B8ED9B0

Serial Number: 4B48B27C8224FE37B17A6A2ED7A81C9F

Not Before: Aug 12 00:00:00 2015 GMT

Not After : Oct 10 23:59:59 2018 GMT

Revocation Status : Revoked on <‎Tuesday, ‎September ‎19, ‎2017>

Signing Time: 10/5/2017 11:44 PM

agent_installer.msi

Signing Time: 9/13/2017 4:30 PM

CCleanerCloudAgent.exe

1.7.0.3214

Signing Time: 9/13/2017 4:30 PM

CCleanerCloudAgent.exe

1.7.0.3214

Signing Time: 9/13/2017 4:30 PM

CCleanerCloudHealthCheck.exe

1.7.0.3214

Hi NonConvergentWaveform,

We are working as fast as we can to replace this. We have rebuilt the build infrastructure and have updated our build signing process to be more secure. We are currently doing final testing on a version built using this new infrastructure that will replace these certificates and we expect it to be released as early as next week.

Hi NonConvergentWaveform,

We are working as fast as we can to replace this. We have rebuilt the build infrastructure and have updated our build signing process to be more secure. We are currently doing final testing on a version built using this new infrastructure that will replace these certificates and we expect it to be released as early as next week.

I see. I guess since this process signs installers in real time (with user adjustments like install times limits, and installer expiration) more care is needed to re-implement then simply swapping out the key. I wasn't sure if this overlooked since it didn't seem to be documented anywhere.

A new CCleaner Cloud installer has been released : v1.08.3400.

To correct my earlier comment: existing CCleaner Cloud agents were updated automatically with the new certificates last week, this is just the initial installer for adding new machines as agents.