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
At present, if you navigate to my home IP address with the right port and protocol but without knowing my Sandstorm hostname, the error message Sandstorm offers for unrecognized hostnames appears, and helpfully tells you the Sandstorm server's actual URL.
This is useful for troubleshooting DNS issues. However, it also lets someone port scanning know not just that I run Sandstorm but what URL it is at, which may lead to more personal or identifying information.
The only legitimate users of my Sandstorm server would approach it by hostname, so there's really no good reason, troubleshooting aside, to offer that error page to someone navigating by IP. It's really just helping port scanners at some point.
I'm wondering if it would be possible to have a configuration option to drop traffic not using a valid hostname instead of displaying the error message.
The text was updated successfully, but these errors were encountered:
At present, if you navigate to my home IP address with the right port and protocol but without knowing my Sandstorm hostname, the error message Sandstorm offers for unrecognized hostnames appears, and helpfully tells you the Sandstorm server's actual URL.
This is useful for troubleshooting DNS issues. However, it also lets someone port scanning know not just that I run Sandstorm but what URL it is at, which may lead to more personal or identifying information.
The only legitimate users of my Sandstorm server would approach it by hostname, so there's really no good reason, troubleshooting aside, to offer that error page to someone navigating by IP. It's really just helping port scanners at some point.
I'm wondering if it would be possible to have a configuration option to drop traffic not using a valid hostname instead of displaying the error message.
The text was updated successfully, but these errors were encountered: