Jump to content

denixx

Members
 View Profile  See their activity

  • Posts

    26

  • Joined

  • Last visited

 Content Type 

Posts posted by denixx

    Installation of Eset Endpoint Antivirus on Ubuntu 22.04

    in ESET Endpoint Products

    Posted

    @eab Sorry, I have no answer for your question, as it might be hard to ask Google to search for something like "who and where decided to drop libssl 1.1 and what guided them," even if you are a google-fu champion.

    There are Release notes for 22.04 here: https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668

    I understood that ESET usually starts work under some issues after the OS release. I faced it while I was in a Fast Ring of Windows Insider program (for no reason, just pure curiosity) and tortured Marcos with mem dumps while Microsoft mangled with network stack, maybe. ESET's SSP firewall module produced BSODs (actually, they were green ).

    Technology is cursed. IS specialists reveal issues (bounty hunting), and technology giants prove some things like "SHA1 is really broken" (https://shattered.io/) maybe also for no reason, just pure curiosity.

    Someone had to make the hard decision somewhere, and it's good Canonical made this decision in 2022 (or maybe 2021).
    22.04 is an LTS release, and 20.04 LTS will have updates until early 2025: https://ubuntu.com/about/release-cycle. This is a long enough period for everyone to update their software.

    I am patiently using 21.10 with dropped support (in VM) because it is still better to have EEA over slightly old OS than to have fresh, shining LTS without EEA. Sept-Oct is acceptable for me as my VM is not facing the internet directly, and I use it for a few tasks. I also faced the issue with my home router OpenVPN configuration, thankfully to 22.04 (in a new VM). This way, I understood the migration to 22.04 would not be simple as it was for previous LTSes. I think I even will reinstall 22.04 from scratch into fresh VM when ESET releases EEA with support for 22.04, as I might break things in the previous copy in my trials.

    22.04 with dropped libssl 1.x will be a hard nut for many software companies. But in final, it will be beneficial.

    Installation of Eset Endpoint Antivirus on Ubuntu 22.04

    in ESET Endpoint Products

    Posted

    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".

    ESET SSP LiveGuard is messing with NVIDIA GeForce Experience which installs fresh NVIDIA drivers - installation fails.

    in ESET Internet Security & ESET Smart Security Premium

    Posted

    ESET SSP LiveGuard is messing with NVIDIA GeForce Experience which is installing fresh NVIDIA drivers.

    Hi!

    I am here to say that there is an issue with ESET LiveGuard is stopping installation of NVIDIA drivers which are run by NVIDIA's GeForce Experience application.

    Current driver branch for GeForce RTX 3070 is 511.79.

    GeForce Experience is a 3.25.0.84.

    Yesterday appeared new driver, and today I clicked to install it.

    Installation started, I choose Express installation, and it failed just because Live Guard started to check safety of it's components.

    Driver installer is extracting it's files into AppData/Temp, and, it looks like they are unpacking also some .so libs (don't ask me why they are packaged into windows installer :) Maybe it's something for CUDA development. )

    So these files is in "sent" in Logs viewer of SSP. (screenshot)

    Actually, I am here because of Live Guard is breaking installation process while fresh driver is trying to install.

    Yes, SSP after some time says all is good, but maybe there should be some action from ESET to be done for drivers. Or maybe for NVIDIA-only :) Some workaround.

     

    Знімок екрана 2022-02-15 16.58.59.png

    EWPE Smart

    in Malware Finding and Cleaning

    Posted

    11 hours ago, itman said:

    Note that other AV solutions on VT are also detecting something; notably WD and Fortinet.

    Opened link to virustotal again just now, and seeing only 6 of AVs for now.

    Looks like Fortinet is not in that list today. What is WD? Looks like it is not in list too.

    EWPE Smart

    in Malware Finding and Cleaning

    Posted

    Hi!

    I'm here to ask about detected application.

    It's "EWPE Smart", available in Play Store: https://play.google.com/store/apps/details?id=com.gree.ewpesmart

    This app is used to control the air conditioners (thru AC WiFi modules), at least my Cooper&Hunter AC may be controlled by this app.

    ESET Mobile Security detected Android/Packed.Jiagu.D in it (/data/app/com.gree.ewpesmart-blablabla/base.apk) and set it to "potentially unwanted app" category.

    Should I inform someone (from Cooper&Hunter, maybe) about this issue, or this could be normal for this app?

    I did some easy search, and found someone posted about another app with this issue: 

     

    (it's better to look the full thread)

    He says "it's just a packer".

    So, if this is kinda "manufacturer recommended app" - what I am supposed to do?

    Thank you!

    Chrome 79 always starts a core dump and crashes

    in ESET NOD32 Antivirus for Linux Desktop

    Posted

    4 hours ago, Kirill said:

    Hi,

    am I wrong here or did Eset just said that there will be no update for V4 but only for Endpoint V7? And if so, then what is with the https://www.eset.com/int/business/endpoint-antivirus-linux/download/ page only offering to download V4?

    Does it all mean that Eset had just basically dropped the support for Linux Desktop with a critical bug and multi-year paid licenses still active?

    That would be very nice of them indeed.

    https://www.eset.com/int/home/antivirus-linux/download/ :)

    Chrome 79 always starts a core dump and crashes

    in ESET NOD32 Antivirus for Linux Desktop

    Posted

    47 minutes ago, Steelskin said:

    Whoever said it's not an issue with Chromium is wrong. It is an identical issue with Chrome & Chromium from the tests I've done. Just depends on what versions you are using.

    My bad, I not checked that information.

    I could see this statement somewhere briefly, that "Chromium is not affected", and made additional conclusion from what Craig posted in Google Chrome Community because they say "we are testing new feature".

    Chrome 79 always starts a core dump and crashes

    in ESET NOD32 Antivirus for Linux Desktop

    Posted

    2 minutes ago, Rami said:

    You can find that here :

    Thank you!

    2 minutes ago, Rami said:

    I believe Google did some kind of change in Chrome that change is making problems with the legacy code of v4.

    Yep. They named it "Renderer Code Integrity".

    I found this via search: https://9to5google.com/2019/10/29/google-chrome-78-aw-snap-crash-windows/

    "With Chrome 78, Google introduced a Windows 10 specific feature called “renderer code integrity,” which is designed to prevent unsigned code from taking control of Chrome’s page rendering processes. Generally speaking, this was designed to stop most viruses from being able to change the way Chrome’s pages load."

    Does it mean that, libesets_pac.so is not signed? Does it mean that simple "signaturing" of this lib will fix a problem? Is that available under linuxes? Should Google turn this feature off for linuxes?

    I could see libesets_pac.so in stacktraces of chrome crashes in journalctl ( https://www.dropbox.com/s/j6rqlinuik612nq/google_chrome_unstable_flickering_and_crash.txt?dl=0 )

    Chrome 79 always starts a core dump and crashes

    in ESET NOD32 Antivirus for Linux Desktop

    Posted

    7 minutes ago, Rami said:

    Lately Chrome prevented AVs from being able to inject into the browser so few months ago Chrome was requesting the user to remove ESET on Windows , it could be the same thing in Firefox , ESET is trying to do something with Chrome and causing a crash.

    "Chrome was requesting the user to remove ESET on Windows"

    Huh, thank you, quite interesting info. Could you please guide me somewhere to read about it? I mean to some official places.

    As I am also using ESET Smart Security Premium on three of my Win10 machines, and wasn't affected, maybe.

    I want to observe the situation.

    Is this also posted somewhere in the Google Chrome Community forums?

     

    //Sorry for offtopic

    Chrome 79 always starts a core dump and crashes

    in ESET NOD32 Antivirus for Linux Desktop

    Posted

    Just now, Rami said:

    I'm not amazed , I am trying to know what the problem is and try to help with it , if you are being rude that doesn't fasten the process of fixing your problem , and no I don't need to take it from Google , I take Chromium from the Terminal which is enough and good for me

    And yes it's not NASA's plans to know that Chrome is not Chromium , you are not adding anything to me , with your reply also, and Chromium and Chrome is almost the same code..

    Sorry for pressure. My fault.

    But you are just looking at wrong browser, it would not be affected at all, as I understood.

    Also (not for being rude, but for numbers and talking about the same things) - the problem potentially affects more than a half of users of linux platform. The ones, who use ESET product for this platform, actually.

×
×
  • Create New...