Jump to content

chrcoluk

Members
  • Content Count

    39
  • Joined

  • Last visited

Profile Information

  • Location
    U.K.

Recent Profile Visitors

526 profile views
  1. Is there a changelog? even tho I had prelease selected i wasnt expecting an automated update to v12 without consent been asked.
  2. I think it has actually activated, as I have a 30 day license, I had to click on the X to close the activation window after acknowledging the error.
  3. An internal error occurred during the activation process. Latest version downloaded directly from ESET.
  4. This seller is still around, and still selling these licenses. I am talking about eset enabling this practice to happen, really they should either be honouring the licenses so innocent people dont lose out or taking action to prevent this from occurring.
  5. I brought a 10 year license from ebay, it seems the practice is to wait for ebay feedback period to expire and also wait for paypal period to expire (6 months) and then cancel the license. Isnt eset giving too much power to resellers as its enabling some nasty fraud to take place. This here also where marcos response was not very forgiving https://forum.eset.com/topic/16019-eset-cancelled-license/
  6. the pause protection is useful for me, please re add it. I have a password enabled so to pause that password has to be entered. Perhaps make it so it still shows if a password is set?
  7. I am not talking about the process although I didnt specifically check the process usage but I think its tied to the OS buffers or something, as I remember checking task manager and no process had large amounts of usage. It was basically memory unaccounted for. Task manager reported the memory as commited but in the process list nothing had it used. The problem goes away when I disable the ransomware protection and does not exist in nod32 v8 (but of course v8 doesnt have the ransomware protection). If I ignore it then windows will eventually start closing down processes when memory runs ou
  8. I prefer the new warning icon, orange was too in your face for informational minor stuff.
  9. I have been running v10 for a while on both my laptop and desktop, overall I am happier with it than v8. However on my laptop there has been a niggling memory leak, its slow but steady, it seems to leak about 100-200mB a day in resource usage, the leak cannot be recovered by closing programs, I have always had to reboot to recover the memory. I started playing with the settings and found by disabling the new ransomware protection in HIPS settings has solved it. I have an idea of why its happening, my laptop runs automated tools every minute which connect to my modem to collect s
  10. So I have been using nod32 with outlook for a number of years, I am scanning emails using the outlook plugin. I however want to migrate to thunderbird, the first problem I noticed was that there is no plugin. I googled and nod32 decided to drop support way back in v5 for vague reasons, which seemed to be summed up as they couldnt be bothered to maintain the plugin anymore. Even when pointed out there is a long term support version of thunderbird which lasts a year with no feature changes eset seeminly refuse to support it. Yet of course they advertise on their commercial product they
  11. I too would like more information on this, the description from eset on AMS is extremely vague and whilst marcos has offered a bit more insight he still hasnt clarified how nod32 determines a process to be suspicious. The post above mine is proof customers of eset are looking at the competition the fact they researched what emsisoft are doing, and I too can confirm I was doing the same, yesterday I spent about 3-4 hours mulling whether to buy nod32 licenses or emsisoft licenses for my laptop and w10 testing machine. I came very close to emsisoft due to the behaviour blocker (of which th
  12. adding this here, as is more relevant then where I posted it I guess. https://forum.eset.com/topic/8418-wishlist/ Will install the new v10 beta on my win10 machine and a VM to test.
  13. it fails because ESET doesnt check for revoked cert's, is recommended if you value proper TLS security to not use https scanning. hxxp://users.encs.concordia.ca/~mmannan/publications/ssl-interception-ndss2016.pdf
  14. The ESET root certificate is not pre-generated. Keeping SSL filtering enabled is strongly recommended and safer than having it disabled as the number of malware that utilizes encrypted communication is rising. With SSL scanning disabled, your system might be vulnerable to such malware. The document is very valid marcos, its sad that eset keep telling people to ignore this stuff instead of redesigning the way they scan https traffic to be TLS RFC compliant.
×
×
  • Create New...