It just shouldn't bug me about it every damn time it happens. And I'll let Avast happily block that attempted access. What I do need, is to suppress the popups if and when an application tries to connect to that specific domain. I don't need access to this domain at this moment. If I don't have to, I'll take the extra layer of "protection". Regardless of whether the exclusion would actually expose me to more risk. So if I'm to try and keep 'safe', I'd rather not exclude the domain. At least not without the exclusion method thought so ill-advised. The wording suggests the broad approach by Avast, and it doesn't elaborate.Īll that said it still doesn't provide me with a means to suppress the popup for this domain. The domain or a specific url at that domain. Blacklist check with multiple sources including Google Safe Browsing and other Phishing Tools and Databases. Submitting a FP doesn't make sense if I can't tell from the popup exactly what was blocked. The details of the warning also do not provide additional information about why this domain is blocked and if the block pertains to the whole domain or just certain particular URLs on that domain. An entry on a blacklist isn't an infection, so that wording is simply wrong. Infected with URL: Blacklist doesn't mean a thing, and the message that "a connection on domain.suffix was aborted" suggests the whole domain is blocked, and doesn't tell me if it in fact is otherwise or more granular.Īt the very least the popup warning should be rewritten to make more sense. What isn't descriptive is the popup Avast shows.
I mention that it isn't a browser to make it clear this isn't a popup from surfing to a website. What new question have I asked? Now I'm quite curious! You certainly seem to think I have.
0 kommentar(er)
