Kodiak Firesmith kfiresmith
| This is the list of exit codes for wget: | |
| 0 No problems occurred | |
| 1 Generic error code | |
| 2 Parse error — for instance, when parsing command-line options, the .wgetrc or .netrc… | |
| 3 File I/O error | |
| 4 Network failure | |
| 5 SSL verification failure | |
| 6 Username/password authentication failure | |
| 7 Protocol errors |
| #System language | |
| lang en_AU | |
| #Language modules to install | |
| langsupport en_AU | |
| #System keyboard | |
| keyboard us | |
| #System mouse |
This note explains the common issue of "notapplicable" results when running openSCAP and SCAP-Security-Guide on CentOS.
SCAP seems like it should be easy because it is "just XML". Then you dig into looking for a test and it gets confusing fast. So it is good to have some background.
SCAP (Security Content Automation Protocol) is actually a set of multiple standards and specifications that are used together to enable automatically testing hundreds of nerd settings. Let me emphasize that: SCAP is not a single XML specification -- SCAP is multiple standards and specs. Whenever you give "SCAP Content" to a scanner to check a system configurations you are giving the scanner multiple XML files representing multiple standards.
References:
From man page: man apt_preferences
| #!/bin/bash | |
| # Does the equivalent of sysprep for linux boxes to prepare them for cloning. | |
| # SPDX-License-Identifier: GPL-3.0-or-later | |
| # For issues or updated versions of this script, browse to the following URL: | |
| # https://gist.github.com/AfroThundr3007730/ff5229c5b1f9a018091b14ceac95aa55 | |
| set -euo pipefail | |
| shopt -s extdebug nullglob |