David du Colombier

> I would rather suggest that Mirco (@hipponix) add your commit: [2a5ffe7](https://github.com/ComplianceAsCode/content/commit/2a5ffe75a310a26b3a128652b050f2cd9649e2c0) to this PR, keeping your contribution that way and as the author of the change Yes, we may...

@hipponix I think you could include this commit as is: https://github.com/0intro/content/commit/975b25cf6d0ec162d7b05e4407ab5ff527602c24

The `controls/cis_al2023.yml` file currently available as part of this PR is nearly identical to `control/cis_rhel9.yml`, with the removal of `l1_workstation` and `l2_workstation`. Just by looking at the beginning of `controls/cis_al2023.yml`...

> Here you can find a commit on my branch, two weeks ago approx .. with a proper file reflecting CIS controls: `https://github.com/hipponix/content/blob/e745325648f56fa2b74c04352549790d4deb38a9/controls/cis_al2023.yml` OK, I've started to look at it,...

Thanks, but your [last commit](https://github.com/ComplianceAsCode/content/pull/12006/commits/895c53755f9fe7960b30f1d599b989f79e493e13) doesn't contain the right `cis_al2023.yaml` file.

> just noticed al2023 does not need the NetworkManager support and it implies a different detection/remediation. What rules are relying on NetworkManager? By the way, there are also some incorrect...

> * NetworkManager -> the remediation ansible playbook generated by the **oscap xccdf generate fix** command, introduces a change for the NetworkManager which is not the default network component on...

> @0intro do we have any additional testing tool to validate the syntax/lint/cis-control you've just pointed out to me or is it just by you looking at the CIS control...

Unfortunately, it's not possible to build Plan 9 on Linux yet. In the past, I've experimented to change the mkfiles to be able to build on Linux with the port...

Thanks. I've added this change to 9legacy. http://9legacy.org/9legacy/patch/9k-jmk-devcons-uartnuart.diff