On 07/17/2012 06:25 PM, Jeffrey Blank wrote:
This is a reasonable start on where we'd like to go (having a
discussion
about authentication/security options), but let's try to flesh this out
a bit more.
Our goal is not to repeat the documentation here:
http://support.ntp.org/bin/view/Support/ConfiguringAutokey
or here:
http://support.ntp.org/bin/view/Support/AccessRestrictions#Section_6.5.3.1.
...but to provide a few XCCDF Rules and OVAL checks that would:
1) provide (basic) info to admins on what they'd need to configure to
get some security benefit (while referencing the authoritative docs)
2) allow for an enterprise admin to run checks to determine if system
are configured a certain way.
For ntp, it's looking complicated.
I also updated the wiki to try to show how we've been using
git-send-email (in an attempt to lure other developers):
https://fedorahosted.org/scap-security-guide/wiki/becomeadeveloper
On 07/16/2012 03:30 PM, ctrueman(a)redhat.com wrote:
> Not sure doing an actual push, so I figured I'd throw this out there on
> the list first.
>
>
>
> _______________________________________________
> scap-security-guide mailing list
> scap-security-guide(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/scap-security-guide
_______________________________________________
scap-security-guide mailing list
scap-security-guide(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/scap-security-guide Well I'm going to
do a bit more research on what a really secure NTP
server looks, because if it's more than just looking at the checksum,
you're right - it's going to be complicated.
--
Clifford Trueman
Red Hat Consulting
757 570 0253