V5 official version

ESET V5 official version released? When？

 

When it's ready. In other words, soon.

 

Marcos, I realize you cant be specific but in the final version will there be some sort on rule set in Automatic mode with rules. Even if it is very basic. thanks

 

Automatic mode has been using pre-defined rules from the very beginning and these will be continually updated by module updates.

 

thanks. One last question, where are the pre-defined rules, I mean as a user can I look at them. Again thank you

 

No, the pre-defined rules are built in.

 

Taking into account HIPS is enabled by default, and an action triggered an internal rule.
How begginers will contribute to detection improvements to the engine?
Will we have an option for submitting files?

 

This feature was first introduced in NOD32 v2 and was called ThreatSense.Net.

 

How about posting the rules somewhere on this forum? So we can have a look at it and see what the HIPS in automatic mode actually protects us against. Panda also posted the behavior blocker rules on their blog for Panda Cloud Antivirus.

 

some observed rules
SelfDefense rules:
block termination/suspend of egui.exe and ekrn.exe.
block access to ESET files for writing and deleting.
No logging or notifications.

Other rules
allow modification of startup settings in Automatic mode.
Block modification of startup settings in policy based mode.
Ask for modifications of startup settings in Interactive mode.
Create allowing rule for modification of startup settings.

These rules inform to the user(logging and notifications)

 

Will the BE be coming out with a new ERAS/console too? Or will this be a bit later?

 

I would like to see the ESET's android in action for the 5th generation.

 

Soon?! Not too soon I hope!

With SSL scanning enabled I can't check emails with TheBat email client.
Turning on "Verification of incoming (outgoing) TCP and UDP packets (cheksum validation)" results in loss of internet connection.

This two problem persist since the first beta version and I informed the developers via email. But after two months these problems are still present.

It will be very irresponsible if you throw the full version with unresolved issues from the beta versions...

I've switched to Look 'n' Stop and EAV because firewall in ESS doesn't work as it should!
Verification of incoming (outgoing) TCP and UDP packets (cheksum validation) should not stop every connection.

 

This was first discovered in v. 4.2, the issue is under investigation. At the moment we're unable to tell if the problem is with TheBat itself or if something can be done on our part to make SSL scanning work in TheBat.

It sounds like you already have TCP Offload chekcsum enabled in your NIC setup. In that case, enabling checksum validation in ESS would break the connectivity as you describe. Don't enable firewall settings that you don't know what they are intended for. If you do, don't wonder that some things may cease working.

 

Maybe you should contact the developers of TheBat. Btw with ESS 4 I didn't have that problem. But now I use the new versions of both ESS and TheBat.

TCP Offload chekcsum is enabled but why then there is no problems with ESS 4?
Whether the old version is not working properly, or new one?

 

I actually had this problem since v4.2 and also found a v4 thread from March where you replied as well.

That's because v5 uses a brand new lightweight driver working at a different filtering level in the OS so checksums are handled differently that at the NDIS layer. The way how LWF work was designed by Microsoft.