-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After every update the Windows Firewall promts on first call #14788
Comments
Related upstream issue: electron/electron#23756 I tested this on windows and I believe its the same thing - Windows Firewall logs relate to UDP packets sent to port 5353 with destination IP 224.0.0.251 as per https://en.wikipedia.org/wiki/Multicast_DNS. It is probably not due to the actual connection needed for the call! Note that for me, the calls succeed (because mDNS isn't required for them to succeed), consistent with the upstream report. The popup doesn't come back once I clicked cancel, but it probably would if I took an update and moved the exe to a different path, as the rule the firewall creates points at the version-specific path. Interesting point from https://groups.google.com/g/discuss-webrtc/c/6stQXi72BEU/m/7qVwleLiBwAJ is that
Most recent Chromium issue: https://bugs.chromium.org/p/chromium/issues/detail?id=1000955
|
Note that this bug refers to the firewall triggering on calls whereas #15973 seems to be about the firewall triggering in general. |
Our plan is to try building with |
Close in favour of element-hq/element-desktop#666 |
Description
After every update of Element / Riot, when I'm receiving or starting the first voice call after the update, the Windows Firewall promts that a new application requested to open a port.
This probably happens because the path of the executable changes with every update (version number in its name).
Steps to reproduce
Describe how what happens differs from what you expected.
I would expect that calls still work after a update and you don't have to have your system administrator around when you want to answer a call after an update.
Logs being sent: no
Version information
For the desktop app:
The text was updated successfully, but these errors were encountered: