to provide status update on this issue.
----- Original Message -----
From: "Jan Lieskovsky" <jlieskov(a)redhat.com>
To: "Dan Warburton" <dan.warburton(a)jvncomm.com>
Cc: "SCAP Security Guide" <scap-security-guide(a)lists.fedorahosted.org>
Sent: Tuesday, June 30, 2015 6:57:59 PM
Subject: Re: [New Release] SCAP Security Guide 0.1.23 is now live
thank you for checking.
----- Original Message -----
> From: "Dan Warburton" <dan.warburton(a)jvncomm.com>
> To: "SCAP Security Guide"
> Sent: Monday, June 29, 2015 4:19:20 PM
> Subject: Re: [New Release] SCAP Security Guide 0.1.23 is now live
> Did you generate the per-builts? I do not see them.
No sorry, I didn't create them yet. Originally planned to make them
manually, then starting from the future versions to add new Makefile
target that would build them automatically.
But later I changed my mind - it's better to start creating them
automatically right from the scratch (read as add new SSG GitHub
repo Makefile target, that would create them upon request).
While exploring the ways how to start providing the pre-built SCAP
Security Guide XML files in a zip archive automatically, we encountered
the following issue:
This needs to be fixed first. Only then we can start shipping pre-built
XML files zip archive. We are looking into fixing this issue and
should be able to provide that promised pre-built zip archive very
For now please use the process described in:
to build an scap-security-guide RPM.
Apologize for the inconvenience / delay.
This way we can find an agreement wrt e.g. to paths, where the content
should be installed etc. (wanted to do this earlier, but in the meantime
got distracted by other issues).
I will do make that pull request tomorrow (so tomorrow in the evening
they could be available already).
Sorry for the delay (and thanks for the remainder!)
Jan iankko Lieskovsky / Red Hat Security Technologies Team
> On June 23, 2015 at 11:53 AM Jan Lieskovsky <jlieskov(a)redhat.com> wrote:
> Hello folks,
> we are thrilled to announce the GA for the SCAP Security Guide of version
> -- the highlights for this release include:
> * Start porting of PCI-DSS profile from RHEL-6 to RHEL-7
> * Add OVAL-5.11 language support for RHEL-7 product if underlying system's
> oscap version supports OVAL-5.11 already
> * Start generating benchmarks for derivative OSes (CentOS, Scientific
> * Get rid of using symbolic links mechanism for OVAL checks shared across
> multiple products (RHEL/6, RHEL/7, and Fedora)
> * Enhance XML files validation performed via make validate target for all
> (optimize speed, validate all XML files against schematron where possible
> For a more detailed Changelog / Release Notes for this release kindly have
> look at:
>  https://github.com/OpenSCAP/scap-security-guide/releases
> For the instructions how to try the new upstream version from source
> kindly have a look at:
> For the prebuilt XML files -- I will try to generate them within tomorrow
> update the v0.1.23
> tag page appropriately when done.
> Please report any issues encountered with the newly added (but also
> existing) SSG content
> via GH tickets interface:
>  https://github.com/OpenSCAP/scap-security-guide/issues/new
> Happy hardening!
> Regards, Jan
> Jan iankko Lieskovsky (on behalf of the SCAP Security Guide upstream team)
> SCAP Security Guide mailing list
> Dan Warburton / JVN Communications w: 609-485-4480 m: 609-457-0154
SCAP Security Guide mailing list