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
Describe the bug
As a first time user of this ansible role, I had a couple of issues that I was able to work through, but would have been easier if covered in the readme documentation. Can I suggest some updates to the readme for these points?
I had a similar issue to this one. [BUG] User locked out if not in *sudo* group #326
I was unable to connect over ssh - this message in sshd log: .. because none of user's groups are listed in AllowGroups
My ansible user had sudo permissions, was in AllowUsers, was in /etc/sudoers, but not in the sudo group, so I was initially locked out of the server.
It is not clear what the purpose of the sugroup group is - should an ansible or admin user be in that group also?
When setting up a new server, when is the best stage to run the hardening role?
Should I setup the server applications before hardening? I found at minor issue when installing an application, and was unclear if this was due to the hardening.
A brief summary of the purpose of the changes in defaults/main/packagemgmt.yml would have been helpful.
Expected behavior
Just an easier experience for those new to hardening via Ansible.
System (lsb_release -a or similar):
Distributor ID: Ubuntu
Description: Ubuntu 24.04.1 LTS
Release: 24.04
Codename: noble
Additional context
Thanks for this invaluable and well-maintained role, and I have run it many times without any errors.
I am happy to draft some text for the readme to assist with this.
The text was updated successfully, but these errors were encountered:
Since this role is pretty massive (and that doesn't have to be a good thing), my steps are:
Install distribution -> Run hardening role -> Install application using a role that applies all necessary changes for the application to work.
Updating the readme with the the purpose of the changes in defaults/main/packagemgmt.yml would indeed be a good thing.
Thanks for the kind words and if you want to submit a PR with any updates, please do so.
Describe the bug
As a first time user of this ansible role, I had a couple of issues that I was able to work through, but would have been easier if covered in the readme documentation. Can I suggest some updates to the readme for these points?
I had a similar issue to this one.
[BUG] User locked out if not in *sudo* group #326
I was unable to connect over ssh - this message in sshd log:
.. because none of user's groups are listed in AllowGroups
My ansible user had sudo permissions, was in AllowUsers, was in
/etc/sudoers
, but not in thesudo
group, so I was initially locked out of the server.It is not clear what the purpose of the
sugroup
group is - should an ansible or admin user be in that group also?When setting up a new server, when is the best stage to run the hardening role?
Should I setup the server applications before hardening? I found at minor issue when installing an application, and was unclear if this was due to the hardening.
A brief summary of the purpose of the changes in
defaults/main/packagemgmt.yml
would have been helpful.Expected behavior
Just an easier experience for those new to hardening via Ansible.
System (lsb_release -a or similar):
Distributor ID: Ubuntu
Description: Ubuntu 24.04.1 LTS
Release: 24.04
Codename: noble
Additional context
Thanks for this invaluable and well-maintained role, and I have run it many times without any errors.
I am happy to draft some text for the readme to assist with this.
The text was updated successfully, but these errors were encountered: