Skip to content

grenn169/scap-workbench

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

scap-workbench – Fedora 42 Compatibility Fork

This is a community-maintained fork of scap-workbench modified to compile and run successfully on Fedora 42 with:

  • Qt 6
  • OpenSCAP 1.4+
  • GCC with -Werror enabled

✅ What’s fixed

  • Deprecated QString::SkipEmptyPartsQt::SkipEmptyParts
  • Deprecated QSet::toList() and QSet::fromList() → replaced with values() / range constructors
  • Range-for loops over QString → now use reference (const QString&)
  • Updated xccdf_policy_generate_fix() signature to match OpenSCAP 1.4+

🛠 How to build

git clone https://github.com/grenn169/scap-workbench.git
cd scap-workbench
mkdir build && cd build
cmake ..
make -j$(nproc)

sudo make install

🧩 Optional: Patch script

If you want to apply all compatibility changes to a clean upstream source:

./patch-for-fedora42.sh

SCAP Workbench

A GUI tool that provides scanning, tailoring and validation functionality for SCAP content

About

SCAP Workbench is a GUI tool that provides scanning, tailoring and validation functionality for SCAP content. It uses openscap library to access SCAP functionalities.

Homepage of the project is https://www.open-scap.org/tools/scap-workbench/

How to run it out of the box

  1. Make sure you have installed all prerequisites

required dependencies:

# yum install cmake gcc-c++ openssh-clients util-linux openscap-devel qt5-qtbase-devel qt5-qtxmlpatterns-devel openssh-askpass

required dependencies (only for the git repo, not required for released tarballs):

# yum install asciidoc

optional dependencies:

# yum install polkit

On Ubuntu this is roughly equivalent to:

# apt install build-essential openssh-client libopenscap-dev libqt5xmlpatterns5-dev ssh-askpass
# apt install asciidoc
# apt install libpolkit-agent-1-0
  1. Build SCAP Workbench:
$ mkdir build; cd build
$ cmake ../
$ make

To build against locally built OpenSCAP library export following variables:

$ export PKG_CONFIG_PATH="$PKG_CONFIG_PATH:/PATH/TO/DIR/WITH/.pcFILE/"
$ export LIBRARY_PATH=/PATH/TO/DIR/WITH/openscap.soFILE/

Additionally it is possible to use custom CMake definitions instead of exporting environment variables:

$ cmake -DOPENSCAP_LIBRARIES:PATH=/local/openscap.so/filepath/ \
    -DOPENSCAP_INCLUDE_DIRS:PATH=/local/openscap/include/path \
    -DOPENSCAP_VERSION:STRING="X.Y.Z" \
    ../
$ make
  1. Install SCAP Workbench: (optional)

(inside the build folder):

$ # may require superuser privileges if you didn't set different installation
$ # prefix (CMAKE_INSTALL_PREFIX)
$ make install

4a) Run SCAP Workbench: (if it was installed)

spawning open file dialog:

$ scap-workbench

with an XCCDF file to load:

$ scap-workbench /path/to/xccdf-file.xml

with a source datastream (SDS) to load:

$ scap-workbench /path/to/sds-file

4b) Run SCAP Workbench: (straight from build dir, without installation)

Note: If you have built SCAP-Workbench against locally built OpenSCAP library, then run one of the following commands:

$ ldconfig /PATH/TO/DIR/WITH/openscap.soFILE/

or

$ export LD_LIBRARY_PATH=/PATH/TO/DIR/WITH/openscap.soFILE/

and then:

$ cd build/
$ bash runwrapper.sh ./scap-workbench

What now?

You should have a built SCAP Workbench executable by now. Please refer to the user manual for documentation on how to use it.

There are 3 ways to get the user manual:

  • Click Help -> User Manual in the application
  • Open /usr/share/doc/scap-workbench/user_manual.html (installed system-wide) or doc/user_manual.html (from the tarball) in your browser
  • Open or download user manual from the website

How to make a tarball

$ mkdir build; cd build
$ cmake ../
$ make package_source

About

SCAP Scanner And Tailoring Graphical User Interface

Resources

License

Stars

Watchers

Forks

Languages

  • C++ 90.4%
  • CMake 5.2%
  • Shell 3.1%
  • C 1.3%