Cool -- thanks for the patch.
You may want to do a few things (and possibly reset away this commit,
and try again):
1) Fill in SUBJECT HERE and BLURB HERE :)
2) Inspect (using git diff) your changes prior to commit, to make sure
you've got exactly what you want.
3) Tell git your username, so you'll get proper credit for your changes
in the commit log. This should do it:
https://help.github.com/articles/setting-your-username-in-git
Thanks again for the patch -- let us know if you want this one, or if
you want to "git reset" and send again!
On 02/07/2013 04:25 PM, Brian Millett wrote:
*** BLURB HERE ***
root (2):
Some minor cosmetic changes, but a major change to the REGEX to
correctly match sha512 no matter where it is on the line see:
"^[\s]*password[\s]+sufficient[\s]+(?:[\w_\.\-=\s]+[\s])sha512" vs
"^\s*password\s+sufficient\s+pam_unix.so\s+sha512.*$"
added extra values for the dcredit, ucredit, etc. then removed the
comments so the oval check will be created.
.../checks/accounts_password_hashing_algorithm.xml | 20 +++++++++++------
RHEL6/input/system/accounts/pam.xml | 22 ++++++++++----------
2 files changed, 24 insertions(+), 18 deletions(-)
_______________________________________________
scap-security-guide mailing list
scap-security-guide(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/scap-security-guide