Conversation
|
9b1ac1d to
babcc49
Compare
|
|
CDS Report build-stretch-amd64#581.0 ✔
|
|
CDS Report build-bullseye-amd64#580.0 ✔
|
|
CDS Report build-buster-amd64#581.0 ✔
|
|
CDS Report build-stretch-amd64#580.0 ✔
|
|
CDS Report build-buster-amd64#580.0 ✔
|
|
CDS Report build-bullseye-amd64#581.0 ✔
|
|
CDS Report build-bookworm-amd64#580.0 ✔
|
|
CDS Report build-bookworm-amd64#581.0 ✔
|
This feature will allow to chose a specific cis version to run, like debian 11 or debian 12
And use it as default version. To this end, the scripts in bin/hardening have been made generic by removing the associated recommendation number. Only impact is if you are used to execute scripts directly from bin/hardening. In this case, please use the "bin/hardening.sh" wrapper as intended. I had to rename 2.3.1_disable_nis.sh to uninstall_nis.sh, as it was conflicting with 2.3.1_disable_nis.sh Also, there was a doublon between 1.1.1.8_disable_cramfs.sh and 99.1.1.1_disable_cramfs.sh ; the former was kept
find_ungrouped_files.sh and find_unowned_files.sh tests can not be executed multiple times: - test repository is not cleaned - configuration is updated multiple times Those tests are also failing, because: - the sed to change the status in the configuration was also changing the test folder path. - missing /proc in EXCLUDED paths - the EXCLUDED configuration doesn't have the correct format for egrep
babcc49 to
ecd32e8
Compare
|
CDS Report build-stretch-amd64#583.0 ✔
|
|
CDS Report build-bullseye-amd64#583.0 ✔
|
|
CDS Report build-buster-amd64#582.0 ✔
|
|
CDS Report build-bullseye-amd64#582.0 ✔
|
|
CDS Report build-stretch-amd64#582.0 ✔
|
|
CDS Report build-buster-amd64#583.0 ✔
|
|
CDS Report build-bookworm-amd64#583.0 ✔
|
|
CDS Report build-bookworm-amd64#582.0 ✔
|
| This option allows to run the scripts as defined for a specific CIS debian version. | ||
| Supported version are the folders listed in the "versions" folder. | ||
| examples: | ||
| --set-version debian_11 |
There was a problem hiding this comment.
debian word is redundant here, on next step we should decide between 11, bullseye, or bullseye_11
There was a problem hiding this comment.
We can also include the pdf file version, like "12_1.0.1", "11_1.0.0" etc.
There was a problem hiding this comment.
pdf version may be not convenient for automation usage though
There was a problem hiding this comment.
We'll settle that in the next PR
No description provided.