Round up the version of RHEL-6's RPM to 0.1-15
so the initial EPEL-6 update wouldn't have 'rc'
in the RPM name.
Pushed to master, uploaded new tarball to source
location, made the Koji build && also scheduled
EPEL-6 Bodhi update:
After passing the testing (having enough karma) this
update will be pushed to EPEL-6 stable channel =>
feel free to test and leave feedback.
Thank you && Regards, Jan.
Jan iankko Lieskovsky / Red Hat Security Technologies Team
I was reading through the Network portion of the SCAP guide and noticed
that there are no CCEs associated with network_ipv6_limit_requests.
Is this an oversight, or are there really none available at this time?
Vice President, Onyx Point, Inc
-- This account not approved for unencrypted proprietary information --
we are proud to announce that the first version of the scap-security-guide
RPM package for Fedora operating system has now reached the -stable repositories
of Fedora 18, 19 (and in case you are running the upcoming preview of Fedora 20
version already, there too).
You can install normally via:
# yum -y install scap-security-guide
Also, the scap-workbench-0.8.2 version:
is already loading the provided SCAP content on Fedora system by default
(refer to scap-security-guide(8) manual page for further information regarding
how to use the content).
Yet, to let Neil Armstrong to clarify our further objective, let's return to his
words for a bit:
"I think we're going to the moon because it's in the nature of the human being to
face challenges. It's by the nature of his deep inner soul... we're required to do
these things just as salmon swim upstream."
The above projected into Fedora SCAP content context means, we are happy to accept
content contributions from the wide community [*]. Therefore feel free to adopt
(test and submit patches) existing RHEL6 SCAP content rules to Fedora, project
Fedora Security Guide's rules:
into OVAL / XCCDF content, or propose completely new rules touching the most hot
areas of Fedora functionality you daily use.
Jan iankko Lieskovsky (on kind behalf of SCAP security guide team)
[*] Feel free to submit questions / patch proposals to scap-security-guide