LizardByte
Firewall Rules and Web UI Defaults #1013
-
Select Topic AreaQuestion BodyThe default Windows firewall rules allow any ports on any network profile and 'Origin Web UI Allowed' is set to LAN by default. I understand this was likely a decision between convivence and security but I don't think these should be the defaults. Either the firewall rules should be updated to exclude the Public profile and limited to the ports used by sunshine or the Web UI should be set to local only by default. The Web UI doesn't really have minimum requirements, I can set the password to 'admin' if i wanted and if someone is using public Wi-Fi with Public Network profile this could potentially be an entry point. I think the bare minimum should be that the Web UI is set to local only by default, users are free to change it later. Thoughts? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
No, I don't think that should be the default. The defaults should work for the majority of users, not the minority. Certainly only a minority of users would use Sunshine on a public wifi... and you really shouldn't even use public wifi for anything, let alone Sunshine. If you have to use public wifi, you should be using a VPN. |
Beta Was this translation helpful? Give feedback.
-
|
I don't think anyone is using sunshine on public wifi, but having the UI just available is the issue. While i agree you should use a VPN on public wifi, there are many scenarios such as school wifi where a VPN may not be a good solution. Why does one need the Web UI available on the LAN by default anyways? |
Beta Was this translation helpful? Give feedback.
No, I don't think that should be the default. The defaults should work for the majority of users, not the minority. Certainly only a minority of users would use Sunshine on a public wifi... and you really shouldn't even use public wifi for anything, let alone Sunshine. If you have to use public wifi, you should be using a VPN.