Jump to content

derek328

Members
  • Posts

    5
  • Joined

  • Last visited

Posts posted by derek328

  1. 1 minute ago, itman said:

    Appears Eset needs to add an option in User Interface -> Application Statuses -> Webcam Protection not to display the access alert for allowed processes. This appears to be the simplest way to do this since there presently is no editing capability for Web Cam rules.


    Fully agreed. Any chance we can get this implemented by the product UI team, @Marcos?

    It would certainly be worthwhile, especially since the currently non-discriminant notification design could foreseeably prompt most users (like us here) to simply disable ESET notifications altogether (amounting to an actual security risk).

  2. 23 hours ago, Skier said:

    The notification appears at boot and anytime the webcam is accessed by any program i.e. the Logitech software and Skype in my case.  To my mind if the webcam is accessed by a program that has been granted permission and a rule created reflecting this, then the notification shouldn't be shown.  It's not a big deal but is annoying.

    Exactly my sentiment as well.

    If I've already created a rule allowing Skype for calls, or Windows 10 biometrics (Windows Hello) to use my webcam for login verification, I don't need ESET to notify me every time they access my webcam anymore.

    Seeing ESET's popup about authorized webcam access at every login (telling me it has authorized Windows Hello to use my webcam) is insanely annoying.

  3. 4 minutes ago, itman said:

    His quoted posting is he granted access. No where does he state he created an allow rule for it.

    I don't have a web cam attached, so I can't test. I assumed this feature is no different than any other Eset protection feature in that clicking on the "allow" button within the alert amounts to a one time allow action. Normally, the alert has to manually expanded to create a permanent rule for the action selected.

     

    Unfortunately, even if a rule is created (as is my case), ESET will still give repeated "webcam access granted" prompts which is just bad design. Wishing there's a bit more we can do about the specific prompts we receive / block out.

  4. 17 minutes ago, itman said:

    Here's a write up on how to create web cam access rules: https://help.eset.com/eis/11.2/en-US/idh_config_webcam_rule_dlg.html

    When you received the Eset alert about web cam access, did the "allow" option also give an option to create a permanent rule for the action? If so, that is your solution. After the rule is created, examine it to determine what process it is allowing access for. The process might not be one you want to give global allow access for.

    I think you misunderstood the post.

    Skier didn't have any problems creating webcam access rules, but was rather frustrated by the fact that ESET doesn't provide more granular ways to control notifications. At the current moment, whenever we use Windows Hello biometric webcam login, ESET would feel the need to bombard us with a message (upon every login, and re-login) about the authorized webcam access.

    That's not just incredibly frustrating, unnecessary, but also can foreseeable prompt some users to simply disable ESET notifications altogether (amounting to an actual security risk).

     

     

×
×
  • Create New...