brakkio86

Hello, I'm facing the same issue. I've a fresh installation of RH Satellite 6.14.0 (i.e. foreman-3.7.0.9-1.el8sat.noarch) and collection 3.10.0. There is any fix for this situation?

I've tried the fix suggested by @s-reimann and implemented a pull request #1686.

Hello, in RHEL the compiled-in default user is "chrony" user, on the other hand, CIS benchmark want to be sure that is also the effective configuration. Is it possible to...

> > Hello, in RHEL the compiled-in default user is "chrony" user, on the other hand, CIS benchmark want to be sure that is also the effective configuration. Is it...

> Well, as @mlichvar says, the default on RHEL is `-u chrony`. So for CIS compliance, do you just need a way to determine what that default value is? Unfotunally...

Hello, I've updated with the suggestion and using `timesync_chrony_service_settings`. What do you think now?

Hello, > The support for leapsectz directive was added long time ago. Is there other reason for having the >= 4.0 conditional? My fault, I didn't find when whas introduced...

> A warning about imcompatibility with leapsmearing servers would be nice. I've added the documenation and warning section.

> Do we need this PR at all? Can you use `timesync_chrony_custom_settings` https://github.com/linux-system-roles/timesync#role-variables: > > ```yaml > timesync_chrony_custom_settings: > - "leapsectz right/UTC" > ``` > > ? Yes, it could...

Hello, I've corrected my commit. The base idea of this pull request is to remove double bracket around logfile path because openscap scanner (CIS Benchmark for RHEL9 level 2 server)...