pam.py leaves 6 trailing spaces in system-auth and password-auth
bbaassssiiee opened this issue · 6 comments
oscap test U_RedHat_6_V1R8_STIG_SCAP_1-1_Benchmark fails because of that.
I'll get to this today
Now I only see trailing spaces on this line:
account required pam_faillock.so
Is that using a 'fresh' pam file? Or was it ran against the same as prior?
On Wed, Jun 15, 2016 at 1:51 PM, Bas Meijer notifications@github.com
wrote:
Now I only see trailing spaces on this line:
account required pam_faillock.so—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/MindPointGroup/RHEL6-STIG/issues/60#issuecomment-226316075,
or mute the thread
https://github.com/notifications/unsubscribe/AEcrYn4WoiZKWcf16bYtbqYsWnIVE5Ybks5qMGXPgaJpZM4IeniB
.
That is against a vagrantbox that you can use too:
vagrant init dockpack/centos6
vagrant up
Op 15 jun. 2016 om 23:09 heeft Jonathan Davila notifications@github.com het volgende geschreven:
Is that using a 'fresh' pam file? Or was it ran against the same as prior?
[image: photo] http://linkedin.com/in/davilaio
http://twitter.com/defionscode http://github.com/defionscode Jonathan
I. Davila
Principal Architect, Automation Practice, Red Hat, Inc
202.415.1878 // redhat.com // jdavila@redhat.com // Washington, D.COn Wed, Jun 15, 2016 at 1:51 PM, Bas Meijer notifications@github.com
wrote:Now I only see trailing spaces on this line:
account required pam_faillock.so—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/MindPointGroup/RHEL6-STIG/issues/60#issuecomment-226316075,
or mute the thread
https://github.com/notifications/unsubscribe/AEcrYn4WoiZKWcf16bYtbqYsWnIVE5Ybks5qMGXPgaJpZM4IeniB
.—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Thumbs up! The oscap audit passes, YEAH!
Cannot reproduce the spaces anymore