Skip to content
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

[enhancement]: limit webadmin access by IP range & add robots.txt #542

Open
1 task done
alexmbird opened this issue Jun 18, 2024 · 3 comments
Open
1 task done

[enhancement]: limit webadmin access by IP range & add robots.txt #542

alexmbird opened this issue Jun 18, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@alexmbird
Copy link

Which feature or improvement would you like to request?

I'd like to see this feature:

At present, when using Stalwart's (brilliant) feature to get LetsEncrypt certificates its HTTP (+HTTPS?) interfaces must be exposed to the whole world. From a security perspective this is undesirable - Stalwart installations will get indexed by Google et al, so if ever there's a vulnerability they'll be easy to find and exploit.

That's not just a theoretical concern - two people's Stalwart installations already show up on Google:

Screenshot 2024-06-18 at 07 05 21

To prevent this it'd be nice to have:

  • A /robots.txt discouraging search engines from indexing Stalwart installations
  • A setting to restrict IP ranges that can connect to the web interface

Hits to /.well-known will need to bypass the restriction as LetsEncrypt don't publish the IP ranges their challenges come from.

Is your feature request related to a problem?

I'm having a problem with...

Code of Conduct

  • I agree to follow this project's Code of Conduct
@alexmbird alexmbird added the enhancement New feature or request label Jun 18, 2024
@nomadturk
Copy link

Obscurity ain't so bad!
I wouldn't want to worry about one more attack vector either. Ideally, I wouldn't even want to host the webadmin on the same server.

But there is already a change that is cooking for this exact purpose AFAIK.

;)

mdecimus added a commit that referenced this issue Jun 18, 2024
@williamdes
Copy link

Thank you for adding the robots tkt
Ideally and code binding http or https should have it

What about implementing the security.txt spec?
Maybe it is already done

@alexmbird
Copy link
Author

@mdecimus that was quick, thanks :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants