persian-boy

Can ESET force the Hips to work like an Anti-EXE? I tired a lot of sample with Hips in interactive but because the Exe file could run the final system status is infected...the problem is hips won't react in execution.
Even with Hips in interactive mode, the process will run(if Eset fails to detect it by sig or whatever it has)and it will remain in the process but can't do anything malicious because hips alert you.
Would be good if we let this hips jump on Executable files
 

It's only available for a couple of countries at the moment but I think they are rolling out to more very soon

I'm just guessing, it's probably because the public beta has not been released.
 

Eset needs to update the Hips module and make it work like this:
If a command wants to run via the cmd then Hips(in interactive mode)must show that command line for the user.
I mean not only show an access alert for the cmd also show the command itself and let the user see the command and then ask to allow or block it.
Also, provide an option to add our safe command lines to the Hips rules.
Im sorry for my bad English but I guess you know what I mean.
 

Whats up?
Can we have this feature?or should I rely on my Rehips for cmd? I'm happy because no one cares about this hips