If you take a look, it says: Failed to download configuration. Revoke.Ģ 20:24:24.020 2412 8068 S0!! CheckCustomFile(): C:\Program Files\TeamViewer\TeamViewer.json: file checksum could not be validatedĢ 20:24:24.020 2412 8068 S0!! CustomConfigurationJson::CheckSignatures: signature not ok Result: 1, Http code: 404Ģ 20:24:24.020 2412 8068 S0 CustomConfigurationUpdater::DownloadRevisionNumber: No configuration available. Using Proxy: 0Ģ 20:24:24.020 2412 8068 S0!! CustomConfigurationUpdater::DownloadRevisionNumber: Failed to download configuration. 2 20:24:24.020 2412 8068 S0!! CheckCustomFile(): C:\Program Files\TeamViewer\TeamViewer.json: file checksum could not be validated 2 20:24:24.020 2412 8068 S0!! CustomConfigurationJson::CheckSignatures: signature not ok 2 20:24:24.020 2412 8068 S0!! CheckCustomFile(): C:\Program Files\TeamViewer\TeamViewer.json: file checksum could not be validated 2 20:24:24.020 2412 8068 S0!! CustomConfigurationJson::CheckSignatures: signature not ok Result: 1, Http code: 404 2 20:24:24.020 2412 8068 S0 CustomConfigurationUpdater::DownloadRevisionNumber: No configuration available. Using Proxy: 0 2 20:24:24.020 2412 8068 S0!! CustomConfigurationUpdater::DownloadRevisionNumber: Failed to download configuration. Logs like these might be normal? But they sure look suspicious to me. Just a theory and I am by no means that familiar with TV. My guess is someone DDOS'd TV's DNS servers, then hijacked the DNS and redirected people to their own, fake, teamviewer update server, which pushed out an "update" for TV which has the security stripped out, so passwords and 2FA no longer work. You'll see TV seems to be trying to download an update to TV's configuration and install it - but it's failing because of a bad checksum? Logs are full of this and it only started in the last few days - never before. While you're looking in logs, look for updates or checksum failures.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |