No it’s not fixed, just tested it, see bug 1379 Any unknown file executed, regardless of whether or not it replaced a previously trusted file, gets added to the trusted files list.
Edit: Not all systems replicate the issue, however several have replicated it.
Edit 2: To clarify, I’m not speaking about the bug where if unknown files replace trusted files they get trusted, that’s a completely different bug than the one I’m talking about in bug 1379.
Although I’d argue it’s more severe, would be most appreciated if that bug could be fixed before updates via internal updater gets pushed to previous versions, although that’s my personal opinion.
FYI: Your reported issue was not a bug. Those files were moved to trusted file automatically because they were marked as trusted in the cloud. This includes clt.exe.
In that case, I’m guessing that there is a slight discordance between cloud state and applied/automatic action.
As for example, an application that’s digitally signed by a trusted vendor could get rated as “Unknown” (if we utilize ‘Lookup’ functionality) and be added to ‘Trusted Files’.
Just curious.
What about this bug and this bug? Sure they are not as critical as “New Dragon 31.1.1 crashes if CIS installed” to be included in Release Notes, but whatever?
Okay, so the people having the issue with clt.exe counted out that leaves only me left with the issue it seems, anyway, you mean to tell me that even a completely new file that isn’t even found in the cloud when looking it up through Malware Search Engine from Comodo | Virus Removal Guidelines is somehow added as trusted in the cloud? That’s some powerful omnipotent whitelisting you’ve got there.