Which features is Windows 10 Defender Firewall blocking that Opera wants to do?
-
opedara last edited by
@leocg How do we identify it? If it's useful and not a real security risk, I'd be OK enabling it.
If there's any concern at all, like I've read with hacks and vulnerabilities opened up through unnecessary or improper port use (ahem, Dell Support Assist), then I'd like to leave it permanently blocked.
-
-
-
leocg Moderator Volunteer last edited by
@starlight It's because the path to opera.exe changes on every update.
-
-
leocg Moderator Volunteer last edited by
@starlight Because nobody asked. My answer is to your comment about it only happen after an Opera update.
What triggers that dialog at first place, I don't know. -
-
-
amunoto last edited by
@opedara Hello leocg. Thank you for giving the explanation, why the defender warning pops up again and again! It's great to have people assist us users here.
Maybe you could even help clarify the mystery entirely for us; Which Opera- feature is demanding the connection that windows defender ist blocking at all / in general / in the first place?
I would like to disable this feature, I think.
It is not the basic internet browsing, as this keeps on working after declining.You wrote: "What triggers that dialog at first place, I don't know."
Who does know this? Can you point him at this discussion here, perhaps? -
A Former User last edited by leocg
@amunoto Another annoyance of the opera updates identiying slightly different is that if you set cookie preferences, after each 'update' you have to reaffirm your choices for each site.
-
amunoto last edited by
@amunoto said in Which features is Windows 10 Defender Firewall blocking that Opera wants to do?:
@opedara Hello leocg. ...
@leocg
I think I have @mentioned the wrong user in my previous post
Sorry!
Leocg - any hints for us (see post)?
Kind regards, Hauke -
-
amunoto last edited by
@leocg Thx, Leo, for your answer.
I would have thought that Opera tries to do something that triggers the firewall, and that is not the simple IP http thing I want it to do.
But I understand from you, that there is stuff that Opera is not doing, but that is coming from "the outside" and that triggers the windows firewall, leading to the message that has been shown in this thread's firts post.
It is weird and not satisfying to me, but well.
Thx again for your help. -
leocg Moderator Volunteer last edited by
@amunoto Unless you have changed something, the Windows Firewall will only alert you about incoming connections. So all those alerts are of sites trying to stablish a connection to your computer.
Usually it's not a problem, since it's how the web works. You will see it if you use other browsers too.You can try removing the rules from the firewall and the check which site triggers it for the first time.
One other thing that may trigger the alert are notifications.
-
-
opedara last edited by
@leocg So, saying it's not a problem and how the web works is brushing away the point of the post... it's a problem if it keeps popping up and we can't tell what exactly it's asking us to stop blocking. Chrome updates just fine without triggering a firewall prompt; same with Firefox and Edge. What Opera's doing is not normal, and is concerning, as is anything that triggers the pop-up (I mean, we all fully understand the point of a firewall right, and why it pops up confirm/deny prompts), especially when we can't tell what exactly it's trying to do.
So, since apparently Opera's dev team hasn't shown up to tell us what's going on, how do we find out?
So far I just cancel the pop-up, because I don't have enough information to know whether to stop blocking something my operating system's firewall is automatically blocking, but it's annoying having to deal with it. The security risk is at this point not worth the convenience, until I get more information.
-
-
leocg Moderator Volunteer last edited by
@opedara Now, what triggers the firewall alert in the first time I don't know since it can be a different reason for each one.
Probably it's the same reason that triggers the firewall for the other browsers. Maybe if you enable the firewall log you can see what is triggering it. -
A Former User last edited by leocg
@leocg As I've said before, it's the crazy way Operas installs the update in a new folder each time, so we get 12345/launcher.exe, then a few days later 12356/launcher.exe, and that's what triggers the firewall (and cookie) rules to run again
The obvious answer is to always have the current working folder for opera as Opera, upon the start of the upgrade, the existing opera folder is renamed Opera.old, then the update is applied to and overwrites the already existing Opera folder.
Then the firewall still assumes it's the same program, as does the Cookie rule models, so the prompt no longer appears.
Although the multiple version folders is, in theory, a good idea the reality is that it's problematic in a browser securing system required these days -
careware last edited by
I don't know about you guys, but for mine it doesnt happen in other browsers...it's an Opera thing...
I don't have the answer... its annoying, I just accept it... it doesn't endear me to Opera tho...only stay cause its a 15 or more year habit
