plus3it / plus3it/ash-linux-formula

[Feature Request] Make `grub2_info.jinja` content a "common" resource

Open
#507 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
SaltStack
Stars
19
Forks
17
PR merge metrics
No merged PRs in 30d

Description

Is your feature request related to a problem? Please describe.

With the Red Hat Enterprise Linux 9 hardening-automation, the bootloader user/password content is (currently) broken up into two findings: one at a priority of "high" (password-protecting GRUB2 menu) and one at "medium" (superuser name). To avoid pointless duplication of configuration content, copied the …/el8 hierarchy's grub2_info.jinja into the …/el9 hierarchy that will be introduced once #506 is merged. Probably want to extend that paradigm to cover EL8, as well.

Describe the solution you'd like

Consolidate the grub2_info.jinja in the already-implemented …/el8/STIGbyID/cat1/grub2_info.jinja file and the soon-to-be-implemented …/el9/RuleById/common/grub2_info.jinja content into a single file that's referenced by both the …/el8/… and …/el9/… content. This should be done by moving the grub2_info.jinja content above (or parallel to) the …/el8/… and …/el9/… content-hierarchies and then use a fetch-method similar to what's implmented in the (pending) …/el9/RuleById/high/content_rule_grub2_uefi_password.sls and …/el9/RuleById/medium/content_rule_grub2_uefi_admin_username.sls states.

Describe alternatives you've considered

Additional context

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Compare the existing el8/STIGbyID/cat1/grub2_info.jinja with the proposed el9/RuleById/common/grub2_info.jinja and inspect the referenced el9 password and admin-username states. Consolidate the shared content so both EL8 and EL9 hierarchies reference it without duplication, then verify the pending EL9 structure from #506 is compatible.

Written by the indexing model from the issue text.

Assessment

Domain
devops, security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.