Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Security Apps
Comodo
Comodo Internet Security 2025 was obliterated by an exploit!
Message
<blockquote data-quote="Andy Ful" data-source="post: 1113799" data-attributes="member: 32260"><p>I know what is happening.</p><p></p><p>With the "All Applications" setting the downloaded AntDM executable ("AntDM...exe") is allowed after one hour, but it creates/executes the "AntDM...tmp" file (temporary file) which is still blocked. The temporary file is blocked because it is newly created, so the creation time is always less than one hour. This block will continue until the AntDM executable is Unrecognized.</p><p></p><p>With the "Executables" setting the downloaded AntDM executable ("AntDM...exe") is allowed after one hour, it creates/executes the "AntDM...tmp" file (temporary file) which is allowed because there is no *.tmp executable type included in the "Executables" group. If you add *.tmp to the "Executables" group, AntDM installation will be blocked just like for "All Applications".</p><p></p><p>From my tests (and yours) it follows that the 1-hour limit works slightly differently for "Executables" and "All Applications" groups because these groups include slightly different executable types (the second group includes the first). However, the time is always counted from the file creation time (manual submission is not required).</p><p>If the Unrecognized executable is allowed after one hour, its newly created copy will be still blocked for one hour.</p><p></p><p>I noticed that the "Executables" group also does not include MSI files, which are included in the "All Applications" group.</p></blockquote><p></p>
[QUOTE="Andy Ful, post: 1113799, member: 32260"] I know what is happening. With the "All Applications" setting the downloaded AntDM executable ("AntDM...exe") is allowed after one hour, but it creates/executes the "AntDM...tmp" file (temporary file) which is still blocked. The temporary file is blocked because it is newly created, so the creation time is always less than one hour. This block will continue until the AntDM executable is Unrecognized. With the "Executables" setting the downloaded AntDM executable ("AntDM...exe") is allowed after one hour, it creates/executes the "AntDM...tmp" file (temporary file) which is allowed because there is no *.tmp executable type included in the "Executables" group. If you add *.tmp to the "Executables" group, AntDM installation will be blocked just like for "All Applications". From my tests (and yours) it follows that the 1-hour limit works slightly differently for "Executables" and "All Applications" groups because these groups include slightly different executable types (the second group includes the first). However, the time is always counted from the file creation time (manual submission is not required). If the Unrecognized executable is allowed after one hour, its newly created copy will be still blocked for one hour. I noticed that the "Executables" group also does not include MSI files, which are included in the "All Applications" group. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
