Jump to content

effprompts

Members
  • Posts

    4
  • Joined

  • Last visited

About effprompts

  • Rank
    Newbie
    Newbie

Profile Information

  • Location
    U.K.
  1. They're not. That's why I said that very specific example of an event that has occurred to me.
  2. Thinking about it though, even that might be an issue. Could you perhaps put up a default Windows toast stating that an application has attempted to make a connection, some basic info, and then have a list of pending connections in the Eset window itself? Maybe under a new header, between "Computer scan" and "Update" or something? This would also help with gaming, since Eset doesn't throw up prompts whilst gaming mode is active, so sometimes network based games get patched and can't connect, with no notification as to the issue from Eset.
  3. So, I use Eset, and have for a couple of years now. It's by far the best solution I've seen, baring one issue that almost every AV/Firewall seems to have: Any prompt is keyboard interactable, the window is default focused, and to top it off, "Allow" is the default selected option. This is incredibly frustrating when your profession requires a lot of keyboard usage. Is there a way to change any of these behaviours? Or set a short period that I can't accidentally press space to confirm that I really did want to allow supertrojan.exe to have full connectivity, instead of entering a simple space in VS? I'm honestly surprised this behaviour has persisted in so many AVs (and Windows itself) for so many years.
×
×
  • Create New...