"Thursday, February 26, 2015 Download of Neoava Guard Beta 3 This has been such a long time, almost like a dead man rising from grave. But just wanted to provide a link to latest setup of NG. Warning: Neoava Guard setup linked is a beta software. It is especially old, from 2007, and has not been update since. So use it at your own risk. This is just for reference and just to keep Neoava Guard available around. http://arman.nayyeri.name/ng-b3-pb-302.exe Such a long time from then! Arman Posted by Arman Nayyeri at 6:52:00 PM" http://neoava.blogspot.co.uk/2015/02/download-of-neoava-guard-beta-3.html
I never used this even on XP because of so many other choices that we enjoyed but i am assuming it isn't compatible for x64 bit machines? Thanks for showing another old favorite.
What the hell, for a moment I became very excited, I thought he developed a version for Win 8! It's not for 64 bit, but I used this HIPS for 8 years on Win XP, together with SSM. It truly was awesome, I had hoped that SpyShelter would become more like NG, in terms of GUI and ease of use.
Does SpyShelter still combine the Firewall rules, and application HIPS rules in the same window? That's a horrible setup in my opinion. I believe the Firewall, and HIPS need separate windows.
Yes...SS still do this. I think becouse of fact that user can manage the all rules (for each detected behaviour) from one list on "Rules" tab. Making separate list only of firewall actions could make some "confusion"...in SS all detected different rule are presented on the list so we'll have sometime few rules for one app. I think it's easier to manage/observe all rule in one place. BTW...you can create your own FW rules, name it and save and then use for single app or group of apps. Such option is useful.
I would still prefer packet filter rules, and HIPS rules have their own window. It just seemed unorganized to me, and took more time to find the packet filter rules I wanted to edit. I will install SpyShelter FW again to see why you think it's better that way. I used Online Armor from 2005-2015 so maybe I just grew accustomed to them being separate like they are in OA.
You mentioned creating your own FW rules... would this allow for VPN security, such as denying internet access on ISP IP and allowing only on VPN IP? I couldn't figure out if SSF will allow this approach just by looking at the various screenshots floating around. Thanks in advance for feedback...
