Jump to content

MMx

ESET Staff
  • Posts

    44
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by MMx

  1. It is fixed in versions >= 9.0.130 and >= 9.0.206 (there are two versioning lines, one has 1xy as the third version number, the other has 2xy). Though I can't tell you what will be released when.
  2. Looks like prerelease servers serve exactly the same modules as release until the product is released, sorry for that. The module should be available on release now.
  3. Thank you for reporting this problem. It should be fixed now on prerelease servers (make sure you receive Internet protection module version 1206B).
  4. There is a bug in the beta that causes that website rules are temporarily not applied after reboot. If you make any change to them, they will be applied again until the next reboot. Can you confirm that this is the problem that you're seeing? This should be fixed in the next release.
  5. Try going to Advanced setup, Web and email -> Protocol filtering -> SSL -> Certificates and look for End certificate validity. Switch both options to Ask. Does that make any difference?
  6. Slithereen Guard: Can you please post a screenshot of the error you see on windows 8.1 64 bit?
  7. @Ellie: What settings have you changed in ESS or Sandboxie? I'd like to ask you to start Firefox from Sandboxie, start Task Manager, click More details at the bottom left, then switch to Details tab on the top of the window and see what User name is next to the firefox process.
  8. Doing an upgrade of an older product leaves the old drivers in place until the next reboot, which is what I guessed might have worked around the issue somehow.
  9. Krond: I'd like to ask you to do the following: With ESS8 already installed open regedit, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Tcpip\Parameters\Interfaces and expand it. Open each name in curly braces you see there, and if there's a DWORD value called TcpAckFrequency there, change it to 2. Then right click Interfaces, Export and PM the file to me. Then reboot and see if it makes any difference regarding speed. Thanks.
  10. waledakmal: You wrote that upgrading v6 -> v7 -> v8 solves your issue. Is it still solved after reboot?
  11. The problem with the speedtest should be fixed in Internet protection module 1150B, which is available on prerelease update servers now. I watched a random twitch stream for about 20 minutes without any drops. Do you have any specific instructions how to replicate the issue?
  12. The fixed Internet protection module 1150B should be available on prerelease update servers.
  13. What you're describing here looks more like a problem in the mentioned Java library, since it understands only a subset of allowed IMAP constructs instead of parsing everything the server is allowed to send. In particular the RFC never mentions that the server SHOULD, SHALL or MUST send only the requested items. Somewhat to the contrary it allows the server to send FETCH responses by unilateral decision (see hxxp://tools.ietf.org/html/rfc3501#section-7.4.2). The reason I'm asking for sample code and intended usage is that I can change the protoscan behavior so that it can be used with the Java library. From the communication you sent it is e.g. not clear why the client is requesting only message body and no headers. Are the headers cached client-side? In such case the clients are usually robust enough to handle such counter-intuitive responses. Or was it sent during previous communication? Protoscan attempts to cache such transmissions, and asks for headers only if they're not cached.
  14. Can you be more specific please? What kind of trouble are we talking about? Do you have a sample code that causes this behavior? What is your planned usage for the library? Thanks.
  15. This should be fixed in Internet protection module 1113 that will make it to prerelease update servers in about two weeks. If you would like to test it sooner, you can find it in the attachment.
  16. Webslinger: Would you please try to mark your browsers for active mode at F5 -> Web and email -> Web access protection -> HTTP, HTTPS -> Active mode on ESS 6 to see if the problem comes back?
  17. Unfortunatelly this looks like an issue with the way lsass handles memory allocations/releases, which is beyond our control. We'll communicate the issue to Microsoft, but these things usually take time.
  18. Sorry for that, we're using ESS for a lot of Eset products for lack of a better word If you plan to use ZoneAlarm along with application protocol filtering, you should be aware that this combination may cause under certain (unpredictable) circumstances that some web pages will not load. I'm afraid that the only way to find out what's going on here is to debug the problematic machine, since we don't have any solid information about the internal workings of Windows. That means replicating the problem in our environment. I'll try to do that and see what I can see.
  19. Hello Arakasi, It looks like you're running the firewalling driver of ZoneAlarm called vsdatant.sys, which is known to have conflicts with application protocol filtering of Eset Smart Security due to a bug in ZoneAlarm. Would you please try to uninstall ZoneAlarm to see if it resolves the issue? Thank you.
×
×
  • Create New...