You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setting up a port forward in the GUI on mac, while in the "Simulated Vlan" mode, exposes the host port publicly by default, even though the UI might lead you to believe it wouldn't.
The UI config for a port-forward (image edit → network → port → add/edit) has a field to specify the host address (third field, tooltip "Host Address") that contains a greyed out 127.0.0.1 if unspecified, but actually seems to default to 0.0.0.0 if you leave it empty, thus exposing the host port outside of the host machine.
Replacing the greyed out 127.0.0.1 with an explicit 127.0.0.1 makes it actually bind the host port to 127.0.0.1:the_port and then doesn't expose it.
Either making the default actually be 127.0.0.1 or changing the greyed out text to 0.0.0.0 to reflect the actual default might be an improvement
(mac os 15, UTM Version 4.6.5 (108), mac chip M3)
Thank you for maintaining this very nice tool btw!
The text was updated successfully, but these errors were encountered:
Setting up a port forward in the GUI on mac, while in the "Simulated Vlan" mode, exposes the host port publicly by default, even though the UI might lead you to believe it wouldn't.
The UI config for a port-forward (image edit → network → port → add/edit) has a field to specify the host address (third field, tooltip "Host Address") that contains a greyed out 127.0.0.1 if unspecified, but actually seems to default to 0.0.0.0 if you leave it empty, thus exposing the host port outside of the host machine.
Replacing the greyed out 127.0.0.1 with an explicit 127.0.0.1 makes it actually bind the host port to 127.0.0.1:the_port and then doesn't expose it.
Either making the default actually be 127.0.0.1 or changing the greyed out text to 0.0.0.0 to reflect the actual default might be an improvement
(mac os 15, UTM Version 4.6.5 (108), mac chip M3)
Thank you for maintaining this very nice tool btw!
The text was updated successfully, but these errors were encountered: