This repository has been archived by the owner on Dec 26, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 200
UsePAM should probably default to yes on Red Hat Linux 7 #23
Comments
This was referenced Jul 26, 2015
The workaround mentioned by RedHat is: We could create that policy and add it to selinux, when use_pam is off and selinux is on. @chris-rock What do you think? |
As per dev-sec/chef-ssh-hardening#96:
|
chris-rock
added a commit
that referenced
this issue
Sep 22, 2015
Support for selinux and pam. fix #23
artem-sidorenko
added a commit
to artem-forks/ssh-baseline
that referenced
this issue
Dec 23, 2016
as PAM should be enabled per default on the most distros: - dev-sec/chef-ssh-hardening#96 - dev-sec/ansible-ssh-hardening#23 - dev-sec/puppet-ssh-hardening#53
artem-sidorenko
added a commit
to artem-forks/ssh-baseline
that referenced
this issue
Dec 23, 2016
as PAM should be enabled per default on the most distros: - dev-sec/chef-ssh-hardening#96 - dev-sec/ansible-ssh-hardening#23 - dev-sec/puppet-ssh-hardening#53
artem-sidorenko
added a commit
to artem-forks/ssh-baseline
that referenced
this issue
Dec 23, 2016
as PAM should be enabled per default on the most distros: - dev-sec/chef-ssh-hardening#96 - dev-sec/ansible-ssh-hardening#23 - dev-sec/puppet-ssh-hardening#53
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
From the
sshd_config
file on a CentOS 7 box:As such, it's probably a good idea to default
ssh_use_pam
totrue
on RedHat 7.This warning isn't in the CentOS 6
sshd_config
file, but there is an article in the Red Hat 6 knowledgebase about not being able to SSH into a system if UsePAM is off and SELinux is on. I don't have an account and can't see the solution, though, so there might be a way to deal with that.See also dev-sec/puppet-ssh-hardening#53 and dev-sec/chef-ssh-hardening#96.
The text was updated successfully, but these errors were encountered: