eab

@Marcos @TomasP @JamesR @Peter Randziak
So, should I say, here is an example where we asked for an update and didn't get it? 
Do we really have to find out by ourselves it is out? (Seen it half an hour ago on the Console by accidentally checking it) 
This is really REALLY bad reputation for ESET. Is there anyone we can escalate this to? 
 
Also, @eab - I suggest doing small batch tests first, I get skeptical with every new version lately.

By the way everyone ... it's been released!!
https://www.eset.com/int/business/download/endpoint-antivirus-linux/

😂😂 Do you work for ESET? LOL!

I agree with avielc and eab's well presented rational comments.
Eset has no idea how businesses function and they fail to comprehend our needs.
 

I think you are missing the point here mate. 
No one from ESET made any attempt to mention any release of a new version or that there has been any changes that might affect the current version. 
Instead all of us here, had to dig through the net to try and debug the ESET R&D Team error messages and figure out what's wrong with installations on 22.04. 
This is a really bad (not the worst, unfortunately I've seen worse) customer service of how to share information and help your customers prepare ahead of time. 

On that note, the error messages can be so unclear and the lack of information on errors that could occur to anyone on the range of ESET business products. really must have me, a client have to dig through a forum where the answers are given on separate threads that would require extensive digging and waste of time on my end. 
Not to mention some errors are just generic errors I actually find answer to on the web instead of ESET. 
Only shows how the support segment of ESET is disorganized, and is left for the community to help one another.  
I will add the staff can be helpful sometimes. However, I expect some better ways to make the common errors or at the very least, a list of these error codes to be published somewhere. 
After all these were made by R&D for them to make it clear to understand what the error is, so make a list of what it means and attach it to some ESET KB. <- you can have this idea for free, this time.

Thanks. Better late than never I suppose. 😒
Both of you have completely missed the point. 🤦‍♂️
Let me try to explain this to you once more as clearly as I possibly can.
Businesses are looking for products and services, which are as reliable as possible, to use in their business environment.
Being reliable not only means, in the case of software, that it runs stably and functions correctly, and that it is well documented, but also that the company developing the software is proactive with informing the customers about such things as critical updates and bug-fixes, as well as when to expect the next releases (release schedule) - especially when concerning major releases. Why is this latter information important?
Because businesses with 100s or 1000s of licences will need to plan ahead for roll-outs, and when Apple, Microsoft, Canonical, etc ... announce months in advance that they have a new OS being released, a businesses IT team will begin to discuss the strategy for migrating to the new OS, and then the question will immediately arise "What is our Endpoint provider doing about the new OS?". 
In the case of ESET and Ubuntu 22.04 the proactive communication to your business customers was, as far as I know, totally non-existent. In plain words, you guys are just sitting on your proverbial communicative hands with the attitude of "Well, if any of our customers are interested enough, they can spend their time searching online until they either eventually stumble across a forum thread that deals with this matter or have to create a new forum thread themselves. We just cannot be bothered to spend a mere 5 minutes of our time writing an official communication regarding the matter." It comes across as incredibly unprofessional.

Thanks. Better late than never I suppose. 😒
Both of you have completely missed the point. 🤦‍♂️
Let me try to explain this to you once more as clearly as I possibly can.
Businesses are looking for products and services, which are as reliable as possible, to use in their business environment.
Being reliable not only means, in the case of software, that it runs stably and functions correctly, and that it is well documented, but also that the company developing the software is proactive with informing the customers about such things as critical updates and bug-fixes, as well as when to expect the next releases (release schedule) - especially when concerning major releases. Why is this latter information important?
Because businesses with 100s or 1000s of licences will need to plan ahead for roll-outs, and when Apple, Microsoft, Canonical, etc ... announce months in advance that they have a new OS being released, a businesses IT team will begin to discuss the strategy for migrating to the new OS, and then the question will immediately arise "What is our Endpoint provider doing about the new OS?". 
In the case of ESET and Ubuntu 22.04 the proactive communication to your business customers was, as far as I know, totally non-existent. In plain words, you guys are just sitting on your proverbial communicative hands with the attitude of "Well, if any of our customers are interested enough, they can spend their time searching online until they either eventually stumble across a forum thread that deals with this matter or have to create a new forum thread themselves. We just cannot be bothered to spend a mere 5 minutes of our time writing an official communication regarding the matter." It comes across as incredibly unprofessional.

Thanks. Better late than never I suppose. 😒
Both of you have completely missed the point. 🤦‍♂️
Let me try to explain this to you once more as clearly as I possibly can.
Businesses are looking for products and services, which are as reliable as possible, to use in their business environment.
Being reliable not only means, in the case of software, that it runs stably and functions correctly, and that it is well documented, but also that the company developing the software is proactive with informing the customers about such things as critical updates and bug-fixes, as well as when to expect the next releases (release schedule) - especially when concerning major releases. Why is this latter information important?
Because businesses with 100s or 1000s of licences will need to plan ahead for roll-outs, and when Apple, Microsoft, Canonical, etc ... announce months in advance that they have a new OS being released, a businesses IT team will begin to discuss the strategy for migrating to the new OS, and then the question will immediately arise "What is our Endpoint provider doing about the new OS?". 
In the case of ESET and Ubuntu 22.04 the proactive communication to your business customers was, as far as I know, totally non-existent. In plain words, you guys are just sitting on your proverbial communicative hands with the attitude of "Well, if any of our customers are interested enough, they can spend their time searching online until they either eventually stumble across a forum thread that deals with this matter or have to create a new forum thread themselves. We just cannot be bothered to spend a mere 5 minutes of our time writing an official communication regarding the matter." It comes across as incredibly unprofessional.

Can you direct me to the actual new version announcement you just mentioned about Linux new version?

Is there some place where this information is made public? 
Thanks for Sharing Marcos, but you do understand that by revealing it after someone mentions their dissatisfaction from the product to the point of not renewing their license, presents itself as an enforced answer, which just makes ESET looks bad. 
Why WHY Can't this be told publicly, shared more transparently??
This isn't criticism. This is merely a poiint for improvement, where delivering more frequent news to those working with ESET products can benefit and schedule their timeline accordingly. 

So, a time has come to ask for support for 22.10 X-D

@Nightowl I hear you, and I agree with your points being:
There doesn't seem to be any AV security product out there which officially supports Ubuntu 22.04/openssl3 (I searched 👀) ESET prefers to release security products which are as secure and well-developed as possible Linux OS on the PC is 2%- 3% of the market share ESET will be releasing a compatible version this month However, all of that being the case, it would have been a welcome, if not also expected, act of professionalism for ESET to communicate these sorts of things to it's paying customers, instead of leaving them high and dry to the point that said customers have to go looking through forum threads to get some indication of what's going on. ESET can send out promotional E-mails to all it's customers, so they obviously have the technical and staffing resources to make this kind of communication happen.
I only mention this because it's something I think ESET can (easily) improve - and I want them to improve because I like their products.

Why do I have the feeling like the devs are going to wait until October 31st 11:59:59 to release the Ubuntu 22.04 version .... 😒

@Nightowl I hear you, and I agree with your points being:
There doesn't seem to be any AV security product out there which officially supports Ubuntu 22.04/openssl3 (I searched 👀) ESET prefers to release security products which are as secure and well-developed as possible Linux OS on the PC is 2%- 3% of the market share ESET will be releasing a compatible version this month However, all of that being the case, it would have been a welcome, if not also expected, act of professionalism for ESET to communicate these sorts of things to it's paying customers, instead of leaving them high and dry to the point that said customers have to go looking through forum threads to get some indication of what's going on. ESET can send out promotional E-mails to all it's customers, so they obviously have the technical and staffing resources to make this kind of communication happen.
I only mention this because it's something I think ESET can (easily) improve - and I want them to improve because I like their products.

Sure, but then again, I'm not aware of 'We' (ESET?) having technically 'promised' anything. In fact, I'm not aware of any official communication on the topic whatsoever.
Now this could be because ...
I'm ignorant, and there exists such official communication, but I'm just not aware of it's existence. The question then could be asked why you never mentioned said information here in this thread ...  Or it could be because the proportion of ESET Ubuntu users is so small that it's not worth ESET's time to formulate such a communication. Or it could be that ESET got caught with their proverbial pants down on this one, and any communication would likely just provoke more questions. The question to be posed here is why they were they caught so off-guard when since at least October 2021 it seemed more than likely that Ubuntu 22.04 would ship with openssl3 ... !? An additional question would be why ESET didn't ship an intermediate release with libssl1 bundled in the software, so that it's Ubuntu customers wouldn't be left in the lurch while they take 6 months to release something more final. I assume it's because of option #2.
In any case, there seems to be an informational blackout surrounding this incident - something I, and others, will not quickly forget. ESET could have handled this much better, especially with regards to ESET's business customers who are each paying for dozens, if not hundreds, of licences per year!

So basically Marcos you gave a timeline but it's not definitive. 
I can understand that, these things takes time and a lot of testings to avoid needing a hotfixes to be pushed due to a complete break. 
Marcos would you mind updating this thread once the service is out? (I don't mind you dropping a link to the release notes without adding another word, this would really be helpful to know what's has changed)
Also if there is any place with a more technical details on such major changes (e.g. libssl issues) where there could be an explanation on what is working and what isn't (to avoid installing something broken per our usecase. that would be really REALLY helpful and a great addition to service to ESET customers. 
Thanks mate!
Appreciate your answers and help in the forum.

Hello!
The IT department where I work, has relied on ESET solutions to protect more than 200 systems on our network, including servers and workstations, very happy with their performance to date.
That said, the license we purchased includes the ability to install this software on our compatible Linux systems and it seems to me a nonsense to have to downgrade a security critical component such as OpenSSL, to continue using other security software such as Endpoint Antivirus.
In our specific case, we have been able to solve the incompatibility problem (temporary I hope) with Ubuntu 22.04.01 in the following way:
# download binary openssl packages from Impish builds wget hxxp://security.ubuntu.com/ubuntu/pool/main/o/openssl/openssl_1.1.1f-1ubuntu2.16_amd64.deb wget hxxp://security.ubuntu.com/ubuntu/pool/main/o/openssl/libssl-dev_1.1.1f-1ubuntu2.16_amd64.deb # install downloaded binary packages sudo dpkg -i libssl-dev_1.1.1f-1ubuntu2.16_amd64.deb sudo dpkg -i openssl_1.1.1f-1ubuntu2.16_amd64.deb Once this is done, the EEA service can be restarted succesfully and the GUI in GNOME Desktop can be launched again. It also re-synchronizes with our local ERA installation.

I hope these indications will be useful for the rest of the forum users who encounter this problem, and will be a wake-up call for ESET to hurry to release the promised update for September-October, in order to upgrade OpenSSL to v3.0 again.
Sorry for my English.
Best regards.

@eab Check this thread https://lists.ubuntu.com/archives/ubuntu-devel/2021-October/041639.html

Guys, I feel you are messing with libssl, but it is not good to mess with it and give others ghostly hopes to work around the installation.
@Marcos is not so happy to announce a specific release day because Ubuntu moved to libssl 3 and dropped old libssl 1.x.x entirely.
There is a need for an ESET devs team to produce a compatible variant for a new OS version because libssl 3 has some breaking changes (a major version digit is changing precisely in such cases).
My experience using Ubuntu(s)/Arch says you must not manually mess with libssl in production systems. Except if you want to break the security layer of your OS to the state when you couldn't use apt/pacman to download packages thru https, inability to run crypto operations like signature verification, etc.
Old EEA is linked to old libssl 1.1.x, you could check it running
$ /opt/eset/eea/sbin/lic
/opt/eset/eea/sbin/lic: error while loading shared libraries: libssl.so.1.1: cannot open shared object file: No such file or directory
As a developer myself, I feel all the pain and questions like "Why the hell they broke it here?!" of ESET devs. 
Antiviruses for Linux are an enterprise thingy. Enterprises are usually not happy to throw more bucks for a blind move to a new release of Linux just because it was released. ESET in this case is just "doing their best for a hard decision made in Canonical". Businesses are asking for support, so 22.04.1 is a good version to have "stabilized LTS"&&"businesses are thinking to start using it".