-
Notifications
You must be signed in to change notification settings - Fork 139
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
There's no way to limit acces to administrative commands #37
Comments
Regarding the topic I concerned without success in the group |
Totally legitimate problem. Also I think shutdown removal is something I could get behind if enough people agree to it, but I'd like to leave this as a more general issue. |
To be clear... send me a patch, and ping the mailing list, and let's get shutdown removed in the next release. I think it's a stupid command to have in the admin protocol with or even without ACL. |
+1 I agree that a client should not be allowed to shutdown the server. If you are looking for a way to mitigate the concern right now, I recommend using supervisord to start gearmand. It can auto-restart gearmand if it ever exits. P.S. "access" is misspelled in the issue title. |
Here is a PL related to the issue. |
Is there a way to limit the access to the text admin protocol ? It looks strange to me that a client can shutdown server for example.
Why not to use a different port for the admin protocol ?
Thanks!
The text was updated successfully, but these errors were encountered: