Replies: 1 comment
-
Thanks for your comment. We are fairly up to new products in upstream. I would also note that maybe this might be case for XCCDF and tailoring. Something else to think about. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Dear complianceAsCode Maintainers,
I hope this message finds you well. I am writing to discuss some modifications I have made to the original complianceAsCode project rules in order to be able to use these rules with my product. I would like to inquire if these changes can be upstreamed or if there is a better way to implement them to ensure compatibility and usability for my product while also contributing back to the main project.
As an example I have included the original code and my modification for one rule but we have several rules with the same behavior.
Original Code:
In the enable_ldap_client/oval/shared.yml file,
/etc/sysconfig/authconfig
andUSELDAPAUTH=yes
were hardcoded :Modified Code:
I modified the original code in order to be able to use the same rule in case a product has a path other than
etc/sysconfig/authconfig
also I replaced the hardcoded regexUSELDAPAUTH=yes
with a configurable oneThese changes allow the rule to support my product, which uses a different configuration file path. I am looking forward to your guidance on whether these modifications are suitable for upstreaming or if there are alternative approaches that you recommend.
Thank you for your time and assistance. I look forward to your response.
Beta Was this translation helpful? Give feedback.
All reactions