Peter Randziak

Hello @FranceBB, well yes, as the v9 didn't have the Web Access Protection feature at all. I recommend to follow it up via a ticket so it can be checked and resolved / work-around-ed. The WAP brings an important additional level of protection... The support schedule is available at https://support-eol.eset.com/en/policy_business/product_tables.html Peter

Hello @j-gray, Ouch, sad to hear that 😞, can you please provide us with the ticket ID so I can have it checked? Peter

Hello @daspolfo, thank you for using our products for such long time. I provided an update on the Pro version, based on the actual info we obtained in this topic Peter

Hello @xiaowu, I still can’t activate it. I recommend to enable the activation logging (ECP logging) and open a case with your distributor to have it checked. The Apple chips are being supported, natively by the v7 so that is not an issue for sure... Peter

Hello @xiaowu, please try to activate it without the VPN, some licenses might be restricted to be activated only in allowed countries... Are you able to access https://edf.eset.com/edf ? Peter

Hello @j-gray, thank you for the feedback provided and the summary. I hope you have cases with the Support team opened to tackle them together. When it comes to the #1 it is a think of ESET PROTECT management platform as well as the #3. When it comes to the issues with the EI activation, the support team would need 1. enable the ECP logging 2. send the activation task and wait until it finishes; mark the UUID of the activation task 3. collect the logs from a client, where the activation task was sent, but was not activated 4. Update / open a new ticket with the Support team to have it checked. Peter

Hello @xiaowu the error should be only temporary, see https://support.eset.com/en/kb7297-resolve-act-or-ecp-errors-during-activation-home-users 0x00030000 (macOS) 0x1003000d (macOS) We could not reach the activation server This error commonly occurs when your computer is not properly connected to your network and your internet connection is not active. Verify you have an active internet connection Your ESET product is having trouble connecting to the ESET servers. Verify that your computer has an active internet connection by going to https://www.eset.com.

Hello @Tp6ojNfYgWweHa, I recommend to submit it as a bug report via a ticket so it will be properly tracked to be checked and fixed... Peter

You are welcome, yes it was fixed by a colleague... Peter

Hello @Nightowl O.K., in that case I'm assume we will have to wait for the analysis by the HQ Support / Dev teams to see what is wrong there and how to fix it... Please keep us posted, Peter

Hello @FranceBB, I understand your frustration, but from our past experience it was really needed to list systems, on which our products bas been tested and are supposed to work as expected. With the vast amount of Linux distros it's not feasible to support all of them, as it is a wild place Don't tell anyone 😉, but I recommend to set it up on a supported distribution to check if the issue is the same and if yes, report a ticket from it. I guess that the solution / work-around will be than same for the Linux distribution of your choice 😉 Peter

Hello @th3mach, thank you for the full URL provided. I'm receiving the same detection on the file and I'm checking it with the lab. Peter

Hello @SALC, VPN is a great tool, but from my PoV to use it just to secure the EP server <-> agent communication would be cracking a nut with a sledgehammer I'm afraid that the checking of the agent's certificate on the proxy level is not possible, at least not easy to achieve, see the links on the end of my post I recommend to check it with the support. Sure the cloud license brings some additional costs, but many benefits as well - like to do not need to host the EP infrastructure and do not need to keep it updated / maintained. I meant of the proxies in this case 🙂 Additional details on the EP server <-> agent communication can be found in the posts by MartinK https://forum.eset.com/topic/27187-securing-port-2222-on-sonicwall-firewall-to-allow-remote-connections-to-esmc-server-on-premise/ https://forum.eset.com/topic/29496-public-facing-esmc-port-2222/ https://forum.eset.com/topic/24859-management-protocol-reverse-proxy/ Peter

Hello @SALC, I recommend to open a support ticket to have it checked, provide the with the configuration of the proxy, policy of the agent and the log from the proxy to have it checked. Peter

How have you excluded it? (by IP or by the certificate's details ?) Peter

Hello @Mohsen Ghaffari, we have a detections in place for payloads used in exploitation of this vulnerability. Peter

Hello @SALC, well yes the VPN would be a very good solution, but deploying it for this purpose only probably does not make a sense. As far as I know it is not possible to verify the agent certificate on the proxy, but you can set up the proxy with an authentication, set it up in the agent's policy so the agents will connect to the on-prem server via it. Or you can migrate to the cloud version, where are teams are taking care of it 😉 Peter

Hello @Nightowl, Have you tried to exclude it by IP or the certificate? It might be worth trying, until a solution is provided by the tech support team... Peter

Hello guys, there probably will be some changes to the product line of products for macOS users, but as of now without further details. As of now it seems that a version with a Firewall feature will be available during the next year... The decision on conducting a BETA program for the Firewall feature for the ECS hasn't been done, yet. Peter

Hello guys, as the ESET Endpoint Antivirus for Linux 10 bas been released as a GA, let me thank you for your participation in this BETA program and the feedback provided. Peter on behalf of the teams involved

Hello @j-gray the recently released ESET Inspect version 1.11 contains fixes for the licensing on macOS / Linux, among many others. Can you please try it with that and provide us with feedback? Thank you in advance, Peter note for us: P_EEI-12927

Hello @j-gray, the EI connector v 1.11 bas been released a later took down, as it was causing some issues for the customers, who's EI instances weren't upgraded yet. As of now the EI connector v 1.11 is available in the Repository. We apologize for the inconvenience caused, Peter

Hello @cyb, I found a similar case from the past This behavior might be a security feature of the underlying authentication protocol (see https://docs.microsoft.com/en-us/dotnet/framework/wcf/feature-details/extended-protection-for-authentication-overview). We recommend to create an exception on the affected endpoints (this is the preferred solution): Open the following configuration path: Web and email -> SSL/TLS -> List of known certificates Click Add, URL, enter extwadfs2v.seas.sk (alternatively you can import the certificate manually by clicking File) Change Scan action to Ignore Peter note for us: P_EESW-2983

Hello @TomTomTom, the ESET Bridge can be used as standard caching / forwarding proxy so the http traffic can be cached, the https will be forwarded. Not sure what is your primary motivation to use it, but it should work fine with the products without full support for it. Peter

Hello @lllusion as of now the product is generally available, it can be downloaded from https://www.eset.com/int/home/cyber-security/download/