Jump to content

Matus

ESET Staff
  • Content Count

    54
  • Joined

  • Last visited

Profile Information

  • Gender
    Not Telling
  • Location
    Slovakia

Recent Profile Visitors

2,593 profile views
  1. Hi Guys, we're working on adding support for RHEL 8 and Suse Linux Enterprise Desktop (SLED) 15. What is means is, that we're actively testing our product on those distributions and we're fixing bugs occured on those systems. It might happen that on other distribution the product will work, but it'll not be officially tested and in case of bugs specific for that system, fix is not guaranteed. There are just too many distributions and we're not capable of supporting everything. Thank you for understanding
  2. Hello, Listed below are package dependencies. However, each of those dependencies can have its own dependencies on particular distro. Unfortunately, we don't have such a list of really master dependencies (dependencies of our dependencies). I'm sorry. Also, list of officially supported distributions is not that big. Therefore if you have really diverse environment outside of supported list, you may experience issues which we may not fix. RPM: /bin/sh /etc/cron.d /usr/bin/crontab gcc kernel-devel make perl rpmlib(CompressedFileName
  3. Hello KPS, hashes of malicious files are shared via LiveGrid Reputation System or other mechanism mentioned above as Marcos wrote. Please don't forget, that if you're the first with a new malware and you would not upload anything to ESET and non of detection layers on the endpoint itself would detect it, you get infected. That's why EDTD works only with when files are sent. Otherwise it's almost the same as LiveGris... Also, EDTD analysis can result in file being suspicious or highly suspicious... for Endpoint, it looks clean so far. For LiveGrid it looks clean as well. However, with
  4. Hi guys, to question no.1, which is probably solved anyway, here is a guidance: https://help.eset.com/efs/7/en-US/realtime-protection-cannot-start.html?zoom_highlightsub=headers To question about CLI: To receive module updates, product have to be activated (CLI, ESMC, WebGUI). When you initiate an update, you get a message that product is not activated (if it's not activated), other server:~$ sudo /opt/eset/efs/bin/upd -u Product is not activated. Otherwise you get following: server:~$ sudo /opt/eset/efs/bin/upd -u Update is not ne
  5. OK, please share it:) Also, please write us an ideal flow, how would you like that activation in terminal with offline file would be implemented.
  6. Hi Sangator, please can you tell me, how do you plan to solve updating of Detection engine and other modules? Unfortunately, right now it's not possible to activate using offline file via console. If you'd have some proxy, which would be connected to internet then it would work.
  7. I'm sorry, I haven't provided you all the information. do this: yum remove efs userdel eset-efs-icap groupdel eset-efs-daemons then install again. It's underlaying behavior of this bug which will be fixed in release version.
  8. Hi, It's a bug which happens in case of update from Beta 3 to RC build. If you'd install that as clean install (uninstall and then re-install) it should work fine. Please note, that Release version will be different than RC with some bugs fixed. Sorry for inconveniences
  9. Hi Paul, Have you tried also with the latest version - 6.7.876.0 ? There have been a couple of changes regarding MacOS compatibility. Thanks
  10. Hi Guys, this thing was identified as malicious, however, it's False Positive. We've added that to whitelist not to trigger, however, we're investigating what has happened, which system and why it was identified that as malicious. The issue will be fixed properly after that investigation. Anyway, for imagination if that would not be FP, then to your questions: Was it really a threat file that got deleted thanks to EDTD? - YES Would the ESET EndPoint Antivirus (without EDTD) still catch it? - No, it would not. Into EDTD are sent only files which Endpoint identified as clean, but
  11. Hi Hawkunsh, it's quite hard to say it just like that via forum, as we don't have any logs or other info, but in case you've a EDTD license and ESMC proxy, then: a, due to different replication times of servers to proxy and it seems that in exact time proxy wasn't available b, because there are healing methods during module updates period ------- A & B will be improved in the next module update. If you however don't have EDTD license, such things should not happen and in such case I'd ask to contact support via official channel so they can troubleshoot that properl
  12. Hi guys. We're very sorry for the inconvenience. We'll surely adjust a tooltip. To your question, why suddenly it starts to appear is that we've added a new message in case license is not available and it was implemented in current AV module 1548. In next version 1549 we'll also provide a more specific description of the error in computer details > alerts. Also, we've adjusted behavior in an environment with ESET proxy, so in case you have licensed EDTD and you experienced some issues, it should much better. Thank you for understanding and we're really sorry for inconveniences.
  13. Hi Guys, if there is a portion of endpoints which reports some error message please check, if a particular endpoint has EDTD license. Go into ESMC Computers > Show details If you don't have it, for such endpoints you'll need to do a new activation task. We've started to show proper information via module update, that why it's sudden. We're also working on a way how to add such endpoints into Dynamic Group in ESMC so some "join dynamic group trigger" or recurrent activation task can be planned.
  14. Hi Brandobot, you can find logs from installation in /var/log/install.log, however, please know that there is more information than just log from ESET products. I'd strongly recommend contacting support directly - https://www.eset.com/us/support/contact/?intcmp=btn-support-request#/business-support/install-activate-endpoint-product/install-endpoint Thank you
×
×
  • Create New...