-
-
Notifications
You must be signed in to change notification settings - Fork 314
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
Consul user is created with login shell #293
Comments
Whoa. Yes please. |
Thank you for addressing this. |
Thanks :) |
It turns out this might be problematic :( hashicorp/consul#1358 (comment) We're now seeing health checks fail .. might be better to revert this change until the issue with consul using a login shell is fixed ... sorry for the hassle, turns out this wasn't a wise change |
Crap. Reverted :( |
Sorry about that! a bit annoying that consul's using a login shell instead On Tue, Nov 15, 2016 at 5:30 PM, Kyle Anderson notifications@github.com
|
Hi,
We're implementing CIS compliance based on the CIS benchmark, and when we're running our InSpec profiles on servers that have consul installed via this module, the system user created for consul has a login shell set (
/bin/bash
in this case) .. would you be open to explicitly setting the shell to/sbin/nologin
?I'll send a PR if this is something that you're likely to accept a change for.
The text was updated successfully, but these errors were encountered: