If you're talking about mixing reHIPS with AdroxideHIPS (once it's released), there shouldn't be a problem with compatibility since reHIPS works completely differently and therefore shouldn't get in the way of AdroxideHIPS functionality. While I haven't tested it myself yet, as long as AdroxideHIPS can access the memory of other running programs then there won't be an issue.
I doubt Avast will release any BB/HIPS which is even close to what AdroxideHIPS is being built to do anytime soon because I think they would've done it by now if they wanted to.
Yes, it is in private testing and this is due to it still being in development. Of course I could release a beta version and have it's release launch off quicker but I don't really feel this is appropriate since not only does the first opinion of a companies software stick, but in terms of security software I believe it's important for it to be reliable and functioning correctly.
Once the product is closer to release (I would say the ETA is 1-2 months) I will have some others test it out privately, and if everything is alright then I'll be able to release it to the public (the free version - the premium version will take additional time).
Thank you for your kind words, even more reason not to release it until it's perfect, knowing that friends are waiting! Originally I wasn't going to provide the details until the development stages was closer to release, however... The easiest way to explain how my BB/HIPS product works is by mentioning the Emsisoft Behavior Blocker; for example, AdroxideHIPS can ask the user if they wish to allow a program: to inject code into another program, install a device driver/create & start a Windows Service, modify the Windows Hosts file, modify the Master Boot Record, hijack the browser (e.g. change the Internet Explorer or Google Chrome home-page), install keyboard hooks (used by keyloggers), ransomware protection (e.g. encryption attempts to files), add to start-up (e.g. via the registry, task scheduler, start-up folder, etc.), drop files to protected directories such as the start of it.Windows folder, perform unwanted system modifications (e.g. disabling of Task Manager, Registry Tools, or even UAC), and that's just the
That being said, for every BB/HIPS feature, the user can change the rule-sets to have it auto-allow/auto-block/ask the user - therefore if they want to allow a program to add to start-up but auto-block modifications to the Master Boot Record (and they can have it set to alert them when this action was auto-blocked) then that is fine.
Alongside this, I am working towards dynamic heuristics (which will also be able to be disabled at the users decision) which will log the activity and intervene only when it's very certain that the program is indeed malicious, without needing any static databases to work with.
I hope the wait won't be too long for release, I'm just as excited as you are... I've been studying and working for a long time, hopefully the work will be paid off and count towards something!
Thanks for reading.
