Skip to content

Fixes Bad fapolicyd Rule-Specifications for AWS CLI v2#639

Merged
ferricoxide merged 3 commits into
plus3it:masterfrom
ferricoxide:BUG/Issue638
Jun 15, 2026
Merged

Fixes Bad fapolicyd Rule-Specifications for AWS CLI v2#639
ferricoxide merged 3 commits into
plus3it:masterfrom
ferricoxide:BUG/Issue638

Conversation

@ferricoxide

Copy link
Copy Markdown
Member

Closes #638

As noted in the commit-message for 8272c1f:

This updated automation will, in the absence of any fapolicyd rules for the AWS CLI (v2) place a pristine rule-file at:

/etc/fapolicyd/rules.d/80-aws.rules

With the contents:

allow perm=any all : path=/usr/local/bin/aws
allow perm=any all : dir=/usr/local/aws-cli/v2/
allow perm=any comm=aws : dir=/var/tmp/'

If any fapolicyd rules for the AWS CLI (v2) already exist:

  • Their content will be aggregated with the "no already-defined" rules content
  • The aggregated rules will be deduplicated
  • The aggregated, deduplicated rules will be writtn to the .../80-aws.rules file

NOTE: if any existing rule-files exist (for AWS CLI v2) and have bad content, that content will be carried forward into the 80-aws.rules file. As such, any already-existing, fapolicyd-breaking rules for AWS CLI v2 will continue to exist after the formula runs and the fapolicyd configuration will continue to be broken

Similarly, if any other .rules file in the /etc/fapolicyd/rules.d directory are broken, when this formula causes the fapolicyd.service to be restarted, the service will go into an error-state.

This updated automation will, in the absence of any `fapolicyd` rules
for the AWS CLI (v2) place a pristine rule-file at:

  /etc/fapolicyd/rules.d/80-aws.rules

With the contents:

  allow perm=any all : path=/usr/local/bin/aws
  allow perm=any all : dir=/usr/local/aws-cli/v2/
  allow perm=any comm=aws : dir=/var/tmp/'

If any `fapolicyd` rules for the AWS CLI (v2) already exist:

* Their content will be aggregated with the "no already-defined" rules
  content
* The aggregated rules will be deduplicated
* The aggregated, deduplicated rules will be writtn to the
  .../80-aws.rules file

**NOTE**: if any existing rule-files exist and have bad content, that
content will be carried forward into the 80-aws.rules file. As such, any
already-existing, `fapolicyd`-breaking rules for AWS CLI v2 will
continue to exist after the formula runs and the `fapolicyd`
configuration will continue to be broken
@ferricoxide ferricoxide requested review from a team June 11, 2026 18:42
Comment thread ash-linux/el9/VendorSTIG/aws_cli_v2.sls
Comment thread ash-linux/el8/VendorSTIG/aws_cli_v2.sls
@ferricoxide ferricoxide requested review from a team and lorengordon June 12, 2026 12:01
@ferricoxide ferricoxide merged commit 1627a7f into plus3it:master Jun 15, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Bad fapolicyd rule-specifications for AWS CLI v2

2 participants