Jump to content

maverickws

Members
  • Posts

    26
  • Joined

  • Last visited

Everything posted by maverickws

  1. Someone please advise Marcos that we're not ESET software testers, we're final costumers that paid for a ready product. I tried to tell him but I felt he didn't listen.
  2. Dear Alana, this is happening due to the unfortunate and mediocre implementation of filters that lock all internet access, making all apps crash. Upon reboot as some apps are then offline, you're able to boot until internet access is restored. This is a brutally awful work by these supposed developers of ESET. Myself as many others have simply uninstalled it to prevent this from happening.
  3. I confirm that the Mac crashes on a fresh boot shortly after login. I received an update from our local distributor saying there was an updated version of ESET, so I proceeded to install: First error says its not meant for my OS version, as the new installer is for 10.12 to 11.0 but we're already on macOS 11.1 since December. Second issue when enabling the extensions ESET Cyber Security appears duplicated. Third issue after reboot the mac freezes until you have to force reboot. I assume this happens because of the -implementation of the network filter, that locks all internet access until it starts, making apps crash. Forth Issue the problem with the emails keeps happening. This version has absolutely no difference from the last, all the issues continue exactly the same. I downloaded the installer from the link provided by our distributor, but also tried a second time going to the international ESET site, exactly the same issues. The mediocrity around here stinks.
  4. As you have provided a number of incorrect and inaccurate answers to a number of topics around here I’ve seen, let us know when the message is coming directly from the developers and engineers. Thank you.
  5. Not a discussion I'm looking to nurture. Please don't use other companies as example for what you have wrong. Since when is this even accepted as a plausible excuse? This is mind boggling. Look up to the examples of who got it right instead of telling us the others who got it wrong.
  6. We don't use Avast. We don't care about "others", we care about presenting the best possible solution to our customers (we're on the IT business btw). There are many mediocre players on the market but that's not who we have as reference, and mediocrity is making way in an augmenting rate by the day. We work very hard to stay away from those people. Sometimes software comes to a stall and no new ideas come to the table, that's why some products die and others gain success, bc they reinvent themselves. Because software is evaluated every moment of every day, constantly. If we're taking time to come here and reporting this and giving pointers is because we want you guys to do it right, which will be good for your company too.
  7. Obviously. I'm not sure if you're deflecting or just playing dumb, but I obviously meant the implementation in regard to how it's active on the system, now if it was filtering L3 or L4. .......... This is irrelevant to the way of how the connection is implemented to be ACTIVE.
  8. Hi Martin before I uninstalled ESET today I noticed there was an update this morning. All our email clients started going off, connectivity to network devices was affected, and other sparse issues here and there. ESET had over a year (since the release of macOS Catalina) when it was widely announced that kernel extensions were being discontinued. If you go to Google and type "ESET legacy extension" you'll get thousands of images like this: However, they waited until Big Sur came out to state that "due to the recent changes on macOS extensions" while being caught unprepared and impacting macOS customers, not giving a damn about it. I've been reporting these issues since November, so far I've had ZERO acceptable answers, the software keeps decreasing in quality to each update, and instead of implementing the network filter properly are just wasting time crippling us users.
  9. Hi Marcos, I think you have mistaken me for an ESET Beta Tester or something alike. We have our own obligations and work to do, we won't be wasting precious hours to debug a crappy software that is the image of the people working behind it. We have completely removed ESET from our machines and we won't be installing it until we have a warranty that the problems are over. We have contacted out local ESET distributor to put a hold on our licenses until then. Moreover, I am again very sorry that you're still not getting the point about the filters. I have posted screenshots of how a proper implementation works, yet you're still here insisting on a completely abhorrent approach to this filter. Again, an approach at the image of the people behind it. Here's a proper Network Filter implementation: Here is the piece of ... implementation by ESET: Print this ticket and pin it to the walls of the dev's labs. Until it looks like the former, you're doing it wrong. The mediocrity is over the roof, for gods sake.
  10. Today we started noticing yet more email problems, random connectivity issues, and unable to SCAN from our network devices, although we could print to the same devices. After troubleshooting, removing and re-adding devices, installing new drivers, checking network and devices config, plus the whole nine yards on the network part, we decided to simply uninstall ESET as it has been the recent cause of all connectivity issues on macOS. As soon as we uninstalled ESET Cyber Security, we can scan again, no more problems with connections etc. So, I would like to ask how much more time will ESET require to fix this issues, properly implement the network filter without having it as a local VPN connection to localhost, and stop f*cking around. I definitely think you guys should fire a couple of devs and poach someone from Obdev for example, they for sure know what they're doing when it comes to network components on Apple devices.
  11. Hi Marcus, do you have an update on this? Also, sometimes after boot the VPN connection doesn't start which hangs my Mac while all apps and iCloud are trying to get internet connectivity. As our licenses are close to expire, we would like to know how much longer after Big Sur coming out will you take until delivering a properly working product.
  12. Thank you Marcos, IIRC these ports have been listed there for a while. I assume what is encrypted is the connection between two endpoints, that doesn't prevent ESET from analysing the emails after they've come out of the encrypted link.
  13. Hi Marcos, I haven't added any ports to no where. However, I did update macOS to 11.1 (from 11.0.z) before stop getting them mails. The ports configured on the app are the standard ports for IMAP (as for POP), so I imagine that is how it is supposed to be, it wouldn't be an effective email protection if it was listening to HTTP ports.
  14. Unable to connect to iCloud IMAP using Apple Mail while Email Protection is activated on ESET Cyber Security. Error message in Apple Mail: Could not connect to this IMAP server. Check your network connection and that you entered the correct information in the Account preferences. Also verify that the server supports SSL. If it does not, deselect the Use TLS/SSL tick box in the Server Settings tab of Account preferences. I performed the following actions to diagnose the issue: Cleared HSTS cache; Cleared NVRAM; Cleared SMC; These actions had no effect. Going to ESET and disabling Email Protection: email started working immediately.
  15. In fact, and adding to what was mentioned here, we can read the following on this ESET official link: https://support.eset.com/en/news7604-eset-support-of-macos-11-big-sur This sentence again implies like if it was Apple's fault - "Apple's mandatory change" & "(...)we were not able to deliver a fully compatible product on the day of the macOS Big Sur release": No, you were not able to deliver a full compatible product because the genius over there were ONE YEAR AND HALF LATE to figure that kernel extensions were to die. Apple correctly informed about this on the FIRST HALF of 2019. ESET, on its mediocrity, not only ignored the information provided, also ignored the warnings issued by Catalina saying Kernel extensions were legacy. It was one whole year with that warning. ONE WHOLE F. YEAR WITH THIS.
  16. Glad you amended the statement, yet I did not read something along the lines of "I am sorry for my incorrect statement, indeed Security Extensions have been available since Catalina, available for development for over one and half years". I guess it was a silent update. I'm REALLY looking forward for January (when my license renews, as well as a hundred other company licenses). I hope you guys use your time well, bc we're starting to do AV testing with other products.
  17. As I called before, "Marcos" is, in my opinion, the perfect image of how bad things are going at ESET: First he insists on affirming that "Security Extensions were introduced in Big Sur" as I'm still waiting for a retraction about that, which is completely incorrect, not to say something else. Also, as he said "When we have a new version with firewall compatible with Big Sur ready, it will appear exactly as Little Snitch in the Network connection list." AGAIN IS NOT TRUE: This is the new version: Which also is INTRUSIVE as unlike the other network filters properly implemented, this one forces to have an active VPN connection. This is Little Snitch (just ONE example): At least something is consistent. Marcos and ESET's developers. Both are horrible and can't get one thing right.
  18. I already created a topic there, inclusive you were there posting that Security Extensions were introduced in Big Sur which is a big lie (and your further "technical" explanations of the same caliber), asked you to retract yourself and you didn't. Anyway will stop the technical discussion here as its an introduction forum. WILL BE LOOKING FORWARD FOR THAT NETWORK FILTER PROPERLY IMPLEMENTED AS YOU DESCRIBE. As well as for your retraction on the aforementioned comment.
  19. @peteytthank you for your reply. The changes were not introduced in this update. Were introduced in Catalina. The narrative that they were introduced in this update is poor and merely indicative of poor technical knowledge on the subject. The change from Kernel Extensions to System Extensions was pushed on Catalina. That means that devs have had since June 2019 or so to start working on these. While the former worked on Catalina, you'd get a warning saying "Legacy Kernel Extensions" something. With Big Sur, it was enforced. That is the difference. I can only tell you that from all the apps I use, and they're plenty, ESET was the only (that I use/own) that wasn't Big Sur ready. Can't vouch for others I don't know about, or other AV's, I didn't chose those, I chose ESET. This is what "ESET's" implementation looks like: And this is how a properly implemented filter looks like: Spot the differences? (I can shoot a difference right way: the poor developer quality). Thousands of companies got this right, these guys at ESET are trying to find a way to have a VPN connection connected all the time: A permanent solution I'd propose would be "get better developers".
  20. Hi all, I'm Ricardo from Portugal, Systems Administrator and Business owner. I've been using ESET Cyber Security for a few years. We only have interest in anti-virus as we have multi-layer firewalls and other security solutions for this. Back in the day we tested a bunch of AV software and we were quite happy with ESET's low footprint and high detection rate. Now-a-days I must say we are very unpleased with the direction of ESET's macOS software development. I have repeatedly received the indication (not only from Marcos here on the forums but also on the phone support) that "Security Extensions" have been introduced with Big Sur. THEY HAVE NOT. They have been introduced with macOS Catalina, on Oct. 2019. Even before the official Catalina launch, devs have had months on end before that launch to develop Security Extensions. Today, in 2020, I have been told ESET is aiming to have a working product .... IN DECEMBER. (its the 24th of November....!), and from what I get still looking at the security extensions the wrong way. For us this is something very troublesome. It tells us ESET is completely alienated from macOS's reality and not even making an effort to cover it. Based on the what the development of ESET Cyber Security will be in the short future, we may give up on ESET, as we are not comfortable with working with suppliers that behave this way or sound this kind of bells.
  21. Alright. Thank you for the feedback. However either the survey has ended or I can't reply to it so... maybe next time. cheers.
  22. Hopefully then it will be a proper implementation of network filter, not that "VPN Proxy whatitsname". It shouldn't even have a "connect" button, shouldn't have any fields editable under Network Preferences. ESET has had MONTHS to install Beta versions of macOS Big Sur and solve this. BTW I kindly request you to retract your comment about System Extensions. System extensions were introduced in CATALINA, your remark just shows how little your knowledge about the subject is, and that's YEARS to work on System Extensions. https://developer.apple.com/system-extensions/
  23. We are ESET Cyber Security users. Which of the options on #2 are Cyber Security users supposed to select? What ESET security products do you use? ESET NOD32 Antivirus ESET Internet Security ESET Smart Security Premium ESET Endpoint Antivirus, ESET Endpoint Security or server security products Is this simply a reflection of why macOS products have had such a poor development lately? Is this the consideration we're due?
×
×
  • Create New...