Skip to content

Commit

Permalink
Typo Fixes -1
Browse files Browse the repository at this point in the history
Signed-off-by: Frederick Witty <[email protected]>
  • Loading branch information
frederickw082922 committed Aug 22, 2023
1 parent cdd9fa4 commit c52bee4
Show file tree
Hide file tree
Showing 7 changed files with 17 additions and 17 deletions.
12 changes: 6 additions & 6 deletions CONTRIBUTING.rst
Original file line number Diff line number Diff line change
Expand Up @@ -6,13 +6,13 @@ Rules
1) All commits must be GPG signed (details in Signing section)
2) All commits must have Signed-off-by (Signed-off-by: Joan Doe <[email protected]>) in the commit message (details in Signing section)
3) All work is done in your own branch
4) All pull requests go into the devel branch. There are automated checks for signed commits, signoff in commit message, and functional testing)
4) All pull requests go to the devel branch. There are automated checks for signed commits, signoff in commit message, and functional testing)
5) Be open and nice to each other

Workflow
--------
- Your work is done in your own individual branch. Make sure to to Signed-off and GPG sign all commits you intend to merge
- All community Pull Requests are into the devel branch. There are automated checks for GPG signed, Signed-off in commits, and functional tests before being approved. If your pull request comes in from outside of our repo, the pull request will go into a staging branch. There is info needed from our repo for our CI/CD testing.
- Your work is done in your own individual branch. Make sure to Signed-off and GPG sign all commits you intend to merge
- All community Pull Requests are to the devel branch. There are automated checks for GPG signed, Signed-off in the commits, and functional tests before being approved. If your pull request comes in from outside of our repo, the pull request will go into a staging branch. There is info needed from our repo for our CI/CD testing.
- Once your changes are merged and a more detailed review is complete, an authorized member will merge your changes into the main branch for a new release

Signing your contribution
Expand All @@ -30,19 +30,19 @@ The process is to certify the below DCO 1.1 text
By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
have the right to submit it under the open-source license
indicated in the file; or

(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
by me, under the same open-source license (unless I am
permitted to submit under a different license), as indicated
in the file; or

(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
person who certified (a), (b), or (c) and I have not modified
it.

(d) I understand and agree that this project and the contribution
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -114,7 +114,7 @@ Package 'python-xmltodict' is required if you enable the OpenSCAP tool installat

## Role Variables

This role is designed so that the end user should not have to edit the tasks themselves. All customizing should be done via the defaults/main.yml file or with extra vars within the project, job, workflow, etc. Non-disruptive CAT I, CAT II, and CAT III findings will be corrected by default. Disruptive finding remediation can be enabled by setting `win22stig_disruption_high` to `yes`.
This role is designed so that the end user should not have to edit the tasks themselves. All customizing should be done via the defaults/main.yml file or with extra vars within the project, job, workflow, etc. Non-disruptive CAT I, CAT II, and CAT III findings will be corrected by default. Disruptive finding remediation can be enabled by setting `win22stig_disruption_high` to `true`.

## Tags

Expand Down
8 changes: 4 additions & 4 deletions tasks/cat2.yml
Original file line number Diff line number Diff line change
Expand Up @@ -2877,7 +2877,7 @@
- name: "MEDIUM | WN22-CC-000270 | PATCH | Windows Server 2022 Application event log size must be configured to 32768 KB or greater. | Warning Message."
ansible.builtin.debug:
msg:
- "Warning!! You have a invalid file size set for wn22stig_application_event_log_max_size please read"
- "Warning!! You have an invalid file size set for wn22stig_application_event_log_max_size please read"
- "the notes for the variable and make the necessary change to the variable to be in compliance."
when: wn22stig_application_event_log_max_size < 32768

Expand Down Expand Up @@ -2910,7 +2910,7 @@
- name: "MEDIUM | WN22-CC-000280 | AUDIT | Windows Server 2022 Security event log size must be configured to 196608 KB or greater. | Warning Message."
ansible.builtin.debug:
msg:
- "Warning!! You have a invalid file size set for wn22stig_security_event_log_max_size please read"
- "Warning!! You have an invalid file size set for wn22stig_security_event_log_max_size please read"
- "the notes for the variable and make the necessary change to the variable to be in compliance."
when: wn22stig_security_event_log_max_size < 196608

Expand Down Expand Up @@ -2943,7 +2943,7 @@
- name: "MEDIUM | WN22-CC-000290 | AUDIT | Windows Server 2022 System event log size must be configured to 32768 KB or greater. | Warning Message."
ansible.builtin.debug:
msg:
- "Warning!! You have a invalid file size set for wn22stig_system_event_log_max_size please read"
- "Warning!! You have an invalid file size set for wn22stig_system_event_log_max_size please read"
- "the notes for the variable and make the necessary change to the variable to be in compliance."
when: wn22stig_system_event_log_max_size < 32768

Expand Down Expand Up @@ -4042,7 +4042,7 @@
- name: "MEDIUM | WN22-DC-000430 | AUDIT | The password for the krbtgt account on a domain must be reset at least every 180 days. | Warning Message Variable."
ansible.builtin.debug:
msg:
- "Warning!! You have a invalid number of days set for wn22stig_krbtgt_account_pass_age please read"
- "Warning!! You have an invalid number of days set for wn22stig_krbtgt_account_pass_age please read"
- "the notes for the variable and make the necessary change to the variable to be in compliance."
when: wn22stig_krbtgt_account_pass_age > 180

Expand Down
6 changes: 3 additions & 3 deletions tasks/cat2_cloud_lockout_order.yml
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@
- name: "MEDIUM | WN22-AC-000020 | AUDIT | Windows Server 2022 must have the number of allowed bad logon attempts configured to three or less. | Warning For Bad Variable."
ansible.builtin.debug:
msg:
- "Warning!! You have a invalid number of days set for wn22stig_lockoutbadcount please read"
- "Warning!! You have an invalid number of days set for wn22stig_lockoutbadcount please read"
- "the notes for the variable and make the necessary change to the variable to be in compliance."
when:
- wn22stig_lockoutbadcount == 0 or
Expand Down Expand Up @@ -45,7 +45,7 @@
- name: "MEDIUM | WN22-AC-000010 | AUDIT | Windows Server 2022 account lockout duration must be configured to 15 minutes or greater. | Warning For Bad Variable."
ansible.builtin.debug:
msg:
- "Warning!! You have a invalid number of minutes set for wn22stig_lockoutduration please read"
- "Warning!! You have an invalid number of minutes set for wn22stig_lockoutduration please read"
- "the notes for the variable and make the necessary change to the variable to be in compliance."
when:
- wn22stig_lockoutduration < 15
Expand Down Expand Up @@ -84,7 +84,7 @@
- name: MEDIUM | WN22-AC-000030 | AUDIT | Windows Server 2022 must have the period of time before the bad logon counter is reset configured to 15 minutes or greater."
ansible.builtin.debug:
msg:
- "Warning!! You have a invalid number of days set for wn22stig_resetlockoutcount please read"
- "Warning!! You have an invalid number of days set for wn22stig_resetlockoutcount please read"
- "the notes for the variable and make the necessary change to the variable to be in compliance."
when:
- wn22stig_resetlockoutcount > wn22stig_lockoutduration or
Expand Down
2 changes: 1 addition & 1 deletion tasks/cat3.yml
Original file line number Diff line number Diff line change
Expand Up @@ -51,7 +51,7 @@
- SV-205800r859311_rule
- V-205800

- name: "LOW | WN22-CC-000030 | PATCH | Windows Server 2022 internet Protocol version 6 (IPv6) source routing must be configured to the highest protection level to prevent IP source routing."
- name: "LOW | WN22-CC-000030 | PATCH | Windows Server 2022 Internet Protocol version 6 (IPv6) source routing must be configured to the highest protection level to prevent IP source routing."
ansible.windows.win_regedit:
path: HKLM:\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters
value: DisableIPSourceRouting
Expand Down
2 changes: 1 addition & 1 deletion tasks/prelim.yml
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@

# HVM is Amazon AMI's, Hyper-V is Azure's, KVM is used for ('QEMU', 'Amazon EC2', 'DigitalOcean', 'Google', 'Scaleway', 'Nutanix', 'KVM', 'KVM Server', 'Bochs', 'AHV')
# Current list is elastic and will be updated as we test more cloud based services.
# Current testing is working in Azure using Hyper-V. We are curently using this for reference:
# Current testing is working in Azure using Hyper-V. We are currently using this for reference:
# https://github.com/ansible/ansible/blob/905131fc76a07cf89dbc8d33e7a4910da3f10a16/lib/ansible/module_utils/facts/virtual/linux.py#L205
- name: Set Fact If Cloud Based System.
ansible.builtin.set_fact:
Expand Down
2 changes: 1 addition & 1 deletion tasks/warning_facts.yml
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@
#
# warn_control_list is the main variable to be used and is a list made up of the warn_control_id's
#
# warn_count the main variable for the number of warnings and each time a warn_control_id is added
# warn_count is the main variable for the number of warnings and each time a warn_control_id is added
# the count increases by a value of 1

- name: "NO CONTROL ID | AUDIT | Set Fact for Manual Task Warning"
Expand Down

0 comments on commit c52bee4

Please sign in to comment.