You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The tag-ids mentioned against the Task listed in the Table of Roles are not in sync with actual task-ids used in the yaml declarations of the task.
This leads to incorrect hardening roles getting applied on the machine.
For example the tag-id 2.2.4 from README.md says it is for Ensure CUPS is not installed (Automated).
But if you check the code base then this tag-id is assigned for ./tasks/section_2_Services.yaml:449:- name: 2.2.4 Ensure telnet client is not installed
To Reproduce
Steps to reproduce the behavior:
grep the the tag-id 2.2.4 in the code repository itself.
Expected behavior
The tag-ids should be uniquely assigned to each role task and has to be aligned while mentioning in the README.md and index.html.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Not Applicable
Additional context
None
The text was updated successfully, but these errors were encountered:
Describe the bug
The tag-ids mentioned against the Task listed in the Table of Roles are not in sync with actual task-ids used in the yaml declarations of the task.
This leads to incorrect hardening roles getting applied on the machine.
For example the tag-id
2.2.4
from README.md says it is forEnsure CUPS is not installed (Automated)
.But if you check the code base then this tag-id is assigned for
./tasks/section_2_Services.yaml:449:- name: 2.2.4 Ensure telnet client is not installed
To Reproduce
Steps to reproduce the behavior:
grep the the tag-id
2.2.4
in the code repository itself.Expected behavior
The tag-ids should be uniquely assigned to each role task and has to be aligned while mentioning in the
README.md
andindex.html
.Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Not Applicable
Additional context
None
The text was updated successfully, but these errors were encountered: