Jump to content

TomasP

ESET Moderators
  • Posts

    917
  • Joined

  • Last visited

  • Days Won

    45

Posts posted by TomasP

  1. Hello Howard,

    We are indeed in the process of switching from 32-bit modules to 64-bit modules.

    The 64-bit module are being tested and will be released via an update soon, so currently the app runs 32-bit modules, but there is full compatibility and full protection even on 64-bit systems and thus nothing to worry about.

    Now why you saw "64-bit" in the about screen earlier - this was simply a bug, which instead of the modules showed the bit-ness of the system. We fixed the bug in the latest release and now it correctly shows the bit-ness of the modules.

    Regards,
    Tomas

  2. 15 minutes ago, itman said:

    BTW - I am not an Eset insider unless someone enrolled me as such w/o my consent.

    That is not possible - being an Insider means downloading and installing a specific build of the product, it is not a switch on our side that we could switch on your behalf.

    Maybe there is some glitch that causes to show some limited parts of the new design in the previous version of the module as well, we will need to look into it.

    Can you please send me an output of ESET Log Collector via a private message?

    Thanks

  3. On April 11, 2019 May 29, 2019, Google is replacing the Google Cloud Messaging (GCM) service with the Firebase Cloud Messaging (FCM) service. (Google has deprecated GCM since April 2018).

    GCM communication protocol is currently used by ESET Remote Administrator / ESET Security Management Center Mobile Device Connector component for management of Android devices.

    The GCM successor – FCM – is supported only by Mobile Device Management v7.0+ and ESET Endpoint for Android 2.2.x+.

    What does this mean? Communication between MDM v6.x and managed Android devices will not stop after April 11, 2019 May 29, 2019, but will no longer be guaranteed on the same level as it was up to this date.

    For users of either MDM version lower than v7.0 or ESET Endpoint for Android lower than 2.2.x, the following article explains all the ways to upgrade and to resolve any issue during upgrading: https://support.eset.com/kb7092/.

    ---

    Google moved the deadline to May 29, 2019. The post has been edited accordingly.

  4. On April 11, 2019 May 29, 2019, Google is replacing the Google Cloud Messaging (GCM) service with the Firebase Cloud Messaging (FCM) service. (Google has deprecated GCM since April 2018).

    GCM communication protocol is currently used by ESET Remote Administrator / ESET Security Management Center Mobile Device Connector component for management of Android devices.

    The GCM successor – FCM – is supported only by Mobile Device Management v7.0+ and ESET Endpoint for Android 2.2.x+.

    What does this mean? Communication between MDM v6.x and managed Android devices will not stop after April 11, 2019 May 29, 2019, but will no longer be guaranteed on the same level as it was up to this date.

    For users of either MDM version lower than v7.0 or ESET Endpoint for Android lower than 2.2.x, the following article explains all the ways to upgrade and to resolve any issue during upgrading: https://support.eset.com/kb7092/.

    ---

    Google moved the deadline to May 29, 2019. The post has been edited accordingly.

  5. I see where you're coming from. Most of the claims you listed can subjectively be understood in several ways, but in general, they are not false, nor misleading - e.g. the product is indeed built on NOD32 technology, as it uses the same malware detection engine, the same database, etc.

    I also checked the product's online help pages and they only mention HTTP, POP3 and IMAP protocols, but nevertheless, I will ask our documentation team to include an explicit mention of no support for encrypted protocols at this time, to make it even clearer and more transparent - thank you for the feedback.

  6. Thank you for your comment. To be honest, I don't recall a situation when a customer contacted us believing the SSL scanning feature was present when it actually wasn't - seldom customers asked whether it is included or not, but I don't think I remember someone actually being misled.

    Can you please point me to the marketing material that made you believe SSL scanning was a part of the product? If there is a misinformation somewhere, we can certainly have it fixed!

    Thank you.

  7. Hello bld,

    The ports used for SSL communication were added both to HTTP and POP3/IMAP scanners in order to facilitate blocking feature - without seeing the encrypted content, we can still perform basic decisions based on the available information about the connection (mainly applicable in the HTTP scanner).

    Rest assured we did not forget the request for SSL scanning - however, we analyze and prioritize new features based on many criteria, both from the users and the market in general and we strive to create a product with features that the majority of our user base will find useful in their everyday online activities.

    With that being said, full HTTPS and POP3S/IMAPS scanning has now been confirmed, is already in the works and will be coming, as Marcos said above.

    Regards,
    Tomas

  8. 2 hours ago, bbahes said:

    Hi @TomasP !

    Can you confirm beta status for 7.1 is still active?

    Does ESET have any release date in mind for 7.1? We use 5.x and will jump to 7 in near future, but would rather wait for this major release than to go through upgrade process which from my perspective is still unpolished and prone to errors.

    Hi, public release for Endpoint products 7.1 is planned for Q2 of this year.

  9. Hello Forum users,

    As most of you probably know, Google is shutting down Google+ later this year - and as one of the shutdown steps, the Google+ login will stop working too. Since Google+ is one of the login options on our Forum as well, we have prepared this post with information about the process.

    While the shutdown will happen on March 7, 2019, some login attempts may intermittently fail starting today (January 28, 2019), as Google is shutting the service down gradually. In case your login attempt via Google+ fails, please try again.

    We anticipate an update to the forum soon. This will replace the Google+ login option with a Google account login option, which will continue to work after the social network ceases its operation. The switch should be seamless and you should be able to continue using your accounts just as before.

    In case you have a dedicated Forum username and password, you can also use these to log in, regardless of the current status of the Google login plugin.

    Users logging in via different social channels or with Forum credentials are not affected by this change.

    Regards,
    Tomas

×
×
  • Create New...