NoVirusThanks OSArmor: An Additional Layer of Defense

Had for the first time no OSArmor icon in the tray this morning, but could not find much info on the problem:

Code:

Naam van toepassing met fout: OSArmorDevSvc.exe, versie: 1.1.0.0, tijdstempel: 0x5af8c602
Naam van module met fout: unknown, versie: 0.0.0.0, tijdstempel: 0x00000000
Uitzonderingscode: 0xc0000005
Foutmarge: 0x00007ffaafff0000
Id van proces met fout: 0xe5c
Starttijd van toepassing met fout: 0x01d3eda5880f0e13
Pad naar toepassing met fout: C:\Program Files\NoVirusThanks\OSArmorDevSvc\OSArmorDevSvc.exe
Pad naar module met fout: unknown
Rapport-id: bed3011f-a1a9-47a9-a724-8b62d41ea85d
Volledige pakketnaam met fout:
Relatieve toepassings-id van pakket met fout: 

The version I use is:1.4_test65
A reboot solved this for now.

 

Any estimated date for the official stable v1.4 ?

 

I'm wondering that too.

 

Just curious why people need a version that is called "stable". It's just a name. I mean, there are some betas that run better than the so-called "stable" releases of other publishers, and I think that is true of OSA at this point. The only thing truly missing is an autoupdater. Otherwise, it doesn't really matter to me if you call it beta or final release.

 

most people associate "beta" with unfinished, unstable and buggy products
in NVT products case it's more about missing features, but very stable.
can't blame them for the stereotypes.

 

Well, I have never had any issue with OSA, so I agree with you.
But I can't keep the pace with all these test releases, so I'm wondering if I can be exposed to any risk if I don't install a new release

 

Yes I agree, with all these builds being released we really do need a in program updater.

 

Smart findings and posting issues, throwing out good suggestions and laying out possible other matters the developer makes really good use of with inclusion or fixings.

Great Program to come along in a long time of this nature.

Obviously NVT is finalizing and topping out OSA after almost every conceivable and reported snag is been answered and addressed to perfection.

 

Here is a new v1.4 (pre-release) test66:
http://downloads.novirusthanks.org/files/osarmor_setup_1.4_test66.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:

+ Fixed some false positives
+ Improved Block processes located in suspicious folders
+ Improved Block execution of malformed PowerShell commands
+ Block execution of scp\ssh\sftp.exe (located on C:\WINDOWS\System32\OpenSSH\)

To install it, first uninstall the previous build, then reboot (not really needed but may help), and install the new build.

If you find any false positive or issue please let me know.

@jimb949 @imuade

We're definitely very close to release it.

Just want to make sure we fix most FPs before official release.

 

Compliments alone can't express enough our gratitude for all the attention and effort NVT.

 

Agreed!

 

@novirusthanks

To be honest, I really hate this"To install it, first uninstall the previous build, then reboot (not really needed but may help), and install the new build.
"

 

Actually, it's not needed, it's just an advice to avoid possible problems

 

Agreed. Don't believe I've ever done it.

 

I have installed it over the previous versions, and so far ...

 

Mentioned for best practices.
Since the first v4 beta release, i updated every time over the previous versions without issues.

 

Yeah, I had a neighbor who did that a lot. And then -- on a dark & stormy night -- the Install Police broke into her house and took her away. She has never since been seen.

 

A niggle for me is the release date is still stuck at dec 2017 in the installer for each test build.

 

I would like to know if OSA can save the current security configuration before making any changes to the system.

I have already done some system hardening manually (via group policy, regedit etc.) and I'd like to save my current baseline (especially the overlapping settings between OSA and my security scripts) just in case I will have to revert back only the changes that OSA will add to my current configuration...

Is this currently possible, or planned to be implemented?

 

Same too.

Presents never any issues but if it did we can always do the Microsoft shuffle reset/restart routine. Seems they will never accomplish not having users totally reboot for some things to work. I always hoped they could solve that but.............

 

OSA can not save the current Windows security configuration. OSA can save only its own current security configuration.

 

Is there a way to reset the config back to default setting. I don't remember what the default config settings were.

 

Yes, Open Configurator and press reset to Default.