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
{{ message }}
This repository has been archived by the owner on Dec 26, 2020. It is now read-only.
If I comment in this module in the above playbook, I get this error in /var/log/auth.log:
May 23 18:05:21 ubuntu-xenial sshd[26236]: Connection from 10.0.2.2 port 59156 on 10.0.2.15 port 22
May 23 18:05:21 ubuntu-xenial sshd[26236]: User myuser not allowed because account is locked
May 23 18:05:21 ubuntu-xenial sshd[26236]: input_userauth_request: invalid user myuser [preauth]
May 23 18:05:21 ubuntu-xenial sshd[26236]: error: maximum authentication attempts exceeded for invalid user myuser from 10.0.2.2 port 59156 ssh2 [preauth]
May 23 18:05:21 ubuntu-xenial sshd[26236]: Disconnecting: Too many authentication failures [preauth]
May 23 18:05:31 ubuntu-xenial su[22231]: pam_unix(su:session): session closed for user myuser
It's running on xenial64, the 16.04 LTS of Ubuntu.
Provisioning the node without this module makes it possible access both SSH and SFTP with the newly created user.
The text was updated successfully, but these errors were encountered:
I'm failing in reproducing your example code because the users_and_groups module failed for me at two different spots.
The hardening module sets the following:
# Specifies the maximum number of authentication attempts permitted per connection. Once the number of failures reaches half this value, additional failures are logged.
ssh_max_auth_retries: 2
Can you set that to 10 and see if it fixes your problem? This seems to be a problem with the authentication.
Hello, I believe I tried that, but I can't be sure I set -o IdentityFile=myuser, but I'm sorry to say that I rewrote this module myself from scratch while waiting for a reply and then it works. I also tried rebooting the machine with a different setting on ssh_max_auth_retries, so I believe that I'm correct in filing this bug report.
I'll leave up to you to choose what to do with this issue, to close or to keep. I'm fine with both, but I won't participate with this module any more. I still use your os hardening though.
Problem: this module stops one new user from logging in, but not the default
ubuntu
vagrant user.I've set up the user/playbook like so:
If I comment in this module in the above playbook, I get this error in
/var/log/auth.log
:It's running on xenial64, the 16.04 LTS of Ubuntu.
Provisioning the node without this module makes it possible access both SSH and SFTP with the newly created user.
The text was updated successfully, but these errors were encountered: