New Antiexecutable: NoVirusThanks EXE Radar Pro

Theres just one bug and I think it works well. Sometimes when it starts, you have to wait for it to load or else it will block everything on startup, even other security products. Like mine. A quick fix is to exit the program and let everything load and re-open it again.

 

BTW,
ERP works fine with Comodo CIS 5.12.256249.2599 in Win 8 64 bit. No conflicts at all.

Later...

Bob

 

Hi guys,
I'm just wondering what are the best settings for erp?
Here's a short video showing you my settings, let me know if I should change anything.

link

 

I can't wait for you to release the trial, I suggested this to a friend a few days ago but neither of us could install the free version to try it (Windows 8 64bit). I'm already using way too many security programs but the features look incredibly promising on this one, just need to try it on my test system for any conflicts.

 

Hi MRF71, don't you have any direct link to this movie? I don't want to foul up OS with this downloader

 

Uncheck "Use our download manager and get recommended downloads" and press "DOWNLOAD".

 

I must have beend blind Thank you.

..:: Edit ::..

The only redundant that I see is that you have a few positions on WhiteList CommandLine that is also declared on CommandLine Wildcard as regular expression (I mean Sandboxie), so in my opinion you could remove those from CommandLine, but I might be wrong. Anyone confirm it?
Morover I like LockDown mode, but it depends on your expectations

Regards
Artur

 

What happened was I first whitelisted the command but it gave me an alert later on, so I had to use the wildcard method

 

Indeed that happened few times, because (for example) when you WhiteListed CommandLine Sandboxie action during closing browser you do it for only one particular case, and next time you close browser you'll get almost the same notification. Almost the same, because the final numbers of the string will be different from the last one. So this is why you use WhiteList CommandLine Wildcard. To replace the final numbers (which are changing everytime you take the same action) with asterisk "*".
Generally I think if you remove all WhiteListed CommandLine connected with Sandboxie, nothing harmful will happen (the're not needed anymore), because you have WhiteList CommandLine Wildcard which does the same as CommandLine


..:: Edit_1 ::..

Have a look

http://i.imgur.com/5eHAQCb.jpg

Those above colored you can remove, because those below colored do exactly the same job


..:: Edit_2 ::..

Another question It is quite obvious that ticking Password Protect Closing of EXE Radar Pro is a good idea, because when you close ERP GUI it seems you can run generally everything. But in addition it seems to be favourable decision when you add taskmgr.exe into Password Protected Prosesses because someone/something may close EXERadar.exe process. Don't you think that there would be possibility to declare Password Protected Prosesses not only regarding to .exe files (e.g. services.msc - because it lets someone/something stop running ERPx86Svc from there)?
Keep in mind that my assumption may be totally wrong for I'm unfamiliar with this cases I'm just curious

 

At last!
Trial version of ERP is available!

 

@artoor

Sure, since you handle that colored CommandLine strings using wildcards, you can remove them from the "CommandLine" TAB

In that case you should password protect the executable:
C:\Windows\system32\mmc.exe

Because when you start "services.msc", it is started with this commandline:
"C:\Windows\system32\mmc.exe" "C:\Windows\system32\services.msc"

C:\Windows\system32\mmc.exe is the process that is used to launch services.msc.

@siketa

Yes, finally we released the trial version of ERP

 

Great! Looking forward to trying it. Thanks nvt...

 

Good job NoVirusThanks

 

novirusthanks,

Have you had a chance to try CIS 6 on a Win 7 or 8 64 bit system yet?

Thanks.

Best regards,

Bob

 

@Trespasser

Not yet, but I plan to test CIS6 and ERP tomorrow on Windows 8 x64 Pro and Windows 7 x64 Pro. I will keep you updated here with the results.

 

That is what I need Thanks!

Great! Long-awaited solution has been released

 

@Trespasser

I tested CIS6 and ERP in a Windows 8 x64 Pro OS and I see they works fine togheter (I configured CIS6 as I showed in the previous post). I used the PC for only few hours: browsed Internet, installed Google Chrome, VLC, Winamp and other applications, rebooted the PC few times, and I noted no issues or OS instability so far. I will keep testing them and I will report here any possible issue I may find. Please note, I installed both programs, CIS6 and ERP on a clean Windows 8 installation, no other security software installed. Here is a screenshot: http://postimg.org/image/42srzzv3v/

 

Thanks in advance
Please test Win7 64 compatability also.

 

It would be very helpful for a new user such as myself to have detailed instructions on how to use the commandline list and the commandline wildcard list in the help file. There really isn't much in the help file. I have been whitelisting the commandlines for several of the Windows prompts instead of a complete whitelist for the process; I hope this is the preferrred and secure way of doing that. Is there a post here with detailed instructions on using these features?

 

Wow. That's hard to believe. Now I have to start looking for what may be the true problem. I have a few things I do, after I re-image, before I start adding any security applications...like taking all Windows Updates, set up SRP (but not enable it), enable DEP, and SEHOP. Sandboxie is always a constant for me. The last things I add is an antivirus (maybe) and ERP. I've been experimenting with CIS 5 (which works fine) and 6 looking for a behavior blocker/HIPS, but really they're structured so badly as far as system permissions go (they give free reign to cmd, regsvr32, rundll32, etc.) I thought using ERP along side it would fill in the gap.

Well, time to re-image, once again, and try something different.

Thanks, novirusthanks, for your testing of CIS 6 for me. I very much appreciate it. Sorry for the trouble, dude. At least I know the problem is on my end.

Best regards,

Bob

 

100% compatible, running both now.

Absolutely no problems - Windows 7 64-bit.

 

@1000db: nvt is working on the new help file, which will be available online.
Until it's finished, you can ask for help here.

 

Cheers, may give this a run out when the next CIS build lands

 

Thank you.

 

@NoVirusThanks - I tried to password protect "C:\Windows\System32\appwiz.cpl" and "C:\Windows\SysWOW64\appwiz.cpl", but then I noticed that a user can only add executables to the "Protected Processes" tab.

Can a feature be added for other file types as well?

Do you think this is a good idea?

or

Unnecessary?