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".
Max Lavache gave kudos to denixx in Installation of Eset Endpoint Antivirus on Ubuntu 22.04
