Jump to content

Protopia

Members
  • Posts

    8
  • Joined

  • Last visited

About Protopia

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    U.K.

Recent Profile Visitors

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

  1. I took a look at the extension's "web permissions" and tried allowing anything that was blocked-by-default, but nothing seemed to help. Also the error message we get on Brave "Connection lost" does suggest that it is something that Brave is blocking rather than something that ESET has disabled.
  2. There is a BIG difference between this extension not being supported and it not working. Brave is mostly the same code as Chrome, and almost ALL extension in the Chrome Extension store work on Brave. So why does the ESET one NOT work? Did ESET deliberately disable this functionality because they didn't want to support it, thus depriving paying customers of a tool which could have been left working but unsupported? Or is there something extra in Brave preventing it from working and if so, are there any Brave settings we can use to allow it to start working?
  3. Using the ESET Outlook Email integration add-in, Classifying an email as Spam in the Outlook Inbox works fine (so the add-in appears to be properly registered with Outlook), however doing the same thing in an open message no longer works (hasn't worked for as long as I can remember). Does anyone have a solution for this?
  4. AFAIK, the eset files are not corrupted - I believe that the issue here is that ESET has updated them but not updated the security hashes.
  5. @Marcos Thank you for reassuring me. However, this has been an issue since Windows 8.1 was introduced with new-style apps, so it has been an issue for many years - so when you say "There is a plan to come with up a solution to this in long term" just how many more years does "long term" mean?
  6. As a tweak to the proposed algorithm, I would suggest that instead of searching within the directory tree 3 leaves below drive root, that instead ESET maintains a list of path prefixes within which the above algorithm would search e.g.: C:\Program Files (x86)\Java\ C:\Program Files\Hyper-V\ C:\Program Files\Java\ C:\Program Files\WindowsApps\ C:\ProgramData\Microsoft\Windows Defender\Platform\ C:\Users\All Users\Microsoft\Windows Defender\Platform\ C:\Users\*\Appdata\Local
  7. Marcos - I did a search for "Keep Rules" before I posted this and didn't find anything else. But a better search has come up with a couple: However, both of these only considered wildcard paths as a solution - which I can understand might create a risk of permissive rule hijacking - and neither of these proposed a workable solution. But they do illustrate that other users find this as annoying as I do. What makes this post different is that it actually proposes an algorithm to allow Keep Rules for new-style Windows apps that is sufficiently secure as to prevent permissive rule hijacking - and I would hope that ESET will give this proper consideration.
  8. Eset internet security does a pretty good job when you install an update to a traditional Windows Desktop App i.e. in the same directory - it offers you a choice of keeping existing rules or not. However it does a very bad job for more modern apps which reside in a different directory. In essence it doesn't recognise that this is an update for an existing app, and you have to set new rules every time. This is by far the biggest annoyance with Eset at the moment. I would like to suggest - AS A MATTER OF HIGH PRIORITY - that Eset adds new functionality for this. So for example, if an App is stored in a directory e.g. "C:\Program Files\WindowsApps\Microsoft.YourPhone_1.20062.97.0_x64__8wekyb3d8bbwe\YourPhone.exe" and it is replaced with a more up to date version in e.g. "C:\Program Files\WindowsApps\Microsoft.YourPhone_1.20101.99.0_x64__8wekyb3d8bbwe\YourPhone.exe" then when Eset finds the new app wants to access the internet it uses the following algorithm to determine whether it is an upgrade or not, and if it is then it offers the Keep Rules dialog as before: Look in the directory hierarchy starting at the second level i.e. subdirectories of "C:\Program Files\WindowsApps" and search for matching executables as follows: 1) Directories match except for exactly one directory level; 2) Application names are the same e.g. YourPhone.exe; 3) Executable signature certificates are identical (and valid). Many thanks.
×
×
  • Create New...