Jump to content

denixx

Members
  • Posts

    26
  • Joined

  • Last visited

About denixx

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    Ukraine

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @eab Check this thread https://lists.ubuntu.com/archives/ubuntu-devel/2021-October/041639.html
  2. @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.
  3. 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".
  4. Done, thank you. I've added logs in previous post. "Yes, SSP after some time says all is good" - I mean that after this message I was able to install driver successfully.
  5. 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.
  6. Hi, @Marcos. There is also something like Spindump. Would it be more effective to make this one? This evening I also found esets_proxy hanging on with 200% CPU usage. Usually this MacBook goes crazy if this happens so I could take a closer look at it if this would happen again. Thank you.
  7. Hi, Marcos! Looks like it is working now, thanks! I would test for couple of days, but even now it looks good with Chrome Unstable 83.0.4103.7 dev (64-bit). No flickering, no crashes. Thank you!
  8. 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.
  9. https://www.virustotal.com/gui/file/8609b4f0effc79fa667cad6ae7b822329abcbce4850bb580ce8d8a8f38736477/detection
  10. But if I launch the scan, mobile ESET says this extracted apk is unwanted.
  11. Also, if I extract the apk to sdcard, and send it to my PC, ESET Smart Security Premium is not seeing apk-file as something bad, it says file is OK.
  12. 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!
×
×
  • Create New...