Here is a new v1.4 (pre-release) (test16):
http://downloads.novirusthanks.org/files/osarmor_setup_1.4_test16.exe
*** Please do not share the download link, we will delete it when we'll release the official v1.4 ***
So far this is what's new compared to the previous pre-release:
+ Block execution of .msc scripts (unchecked by default)
+ Block execution of .bat scripts (unchecked by default)
+ Improved some internal rules related to the options added on test15
+ Updated Configurator and "Exclusions Helper" GUI
+ Minor fixes and optimizations
+ Fixed some false positives
To install this pre-release, first uninstall the old one.
@Telos
Thanks for reporting that FP, it should be fixed on test16, please confirm.
@Prorootect
And what about Firefox 55 Nightly edition? Is it in FF Protection?
Yes.
so would you use this cfoc.org list to block all these file types?
The .vb and .ws extensions do not work (are unassigned).
The other important ones, like .pif, .com, .scr, .hta, .jar, .cpl, .cmd, .js, .jse, .wsf, .vbs, .vbe, .ps1 are already covered.
I added .msc and .bat in this test16 build, but be aware that blocking .bat scripts may generate many FPs.
@DavidLMO
Yeah, as
@shmu26 said, it is because the uninstaller does not remove the .db files.
If you do not have saved exclusions or custom-block rules, you can uninstall it, remove the folder "C:\Program Files\NoVirusThanks\OSArmorDevSvc\" and install the new build.
@ozone
Does it protect portable versions of apps in anti-exploit tab?
Yes, here is a screenshot with LibreOffice portable (the exploit payload has been blocked):
Is there some popup that informs us that app which we launch is protected (anti-exploit)?
Not at the moment.
@AtlBo
Thanks for the feedback, much appreciated and glad you like how OSArmor works
Anyone have a quick/simple explanation of how the exploit protection works? I guess nothing can protect from a malicious browser extension, unless it tries to create files, so I am just curious about how far the anti-exploit protection goes.
The Anti-Exploit module accurately monitors child processes executed from vulnerable processes and performs many smart checks and can block the payload of the exploit, see this video for more info:
It does not monitor for browser extensions.
BTW, anyone can explain how the presence of //E: in a script is innately dangerous?
The //E: parameter is used with wscript.exe and cscript.exe and can change the script engine, for example wscript.exe can load a javascript file with .tmp extension with like "wscript.exe //E:JScript C:\file.tmp" and this technique is also used by malware\exploits.
You can read more info here:
Wscript