Rudder

If a directive is created in “audit” mode using the “SSH authorized keys” system technique with parameters as in attached screenshot, and after having been ran on the nodes, the directive is later on changed to “enforce” mode, then after being ran on the nodes again, their compliance displays a “bad policy mode” error as in attached screenshot.

Furthermore, if the directive is changed to “audit” mode again, it will display a spurious “The keys for user blah could not be flushed”, where the authorized_keys file do actually have the proper contents (thus should be considered compliant and shouldn't need to be flushed).