User story #4226
closed
User story #3889: Configure node-server communication security options from administration web interface
Add the CFEngine logic to use DENYBADCLOCKS and SKIPIDENTIFY
Added by François ARMAND almost 11 years ago.
Updated over 9 years ago.
Category:
System techniques
Description
When Rudder will have the "deny bad clocks" system variable available, it need to be used in CFEngine to actually do what it should on CFEngine server.
- Subject changed from Add the CFEngine logic to use DENYBADCLOCKS to Add the CFEngine logic to use DENYBADCLOCKS and SKIPVERIFY
- Status changed from 8 to In progress
- Assignee set to Jonathan CLARKE
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to François ARMAND
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/246
- Subject changed from Add the CFEngine logic to use DENYBADCLOCKS and SKIPVERIFY to Add the CFEngine logic to use DENYBADCLOCKS
- Status changed from Pending technical review to In progress
- Assignee changed from François ARMAND to Jonathan CLARKE
Jon,
you need to add the variable in the metadata.xml as well
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Nicolas CHARLES
Nicolas CHARLES wrote:
Jon,
you need to add the variable in the metadata.xml as well
Done, thanks. Can you re-TR?
- Status changed from Pending technical review to 12
Looks good to me !
You need to rebase though, as it is not mergeable as it is
- Subject changed from Add the CFEngine logic to use DENYBADCLOCKS to Add the CFEngine logic to use DENYBADCLOCKS and SKIPIDENTIFY
- Status changed from 12 to Discussion
- Assignee changed from Nicolas CHARLES to Jonathan CLARKE
Some more integration have to be done as "SKIPVERIFY" was added along with "DENYBADCLOCKS".
- Status changed from Discussion to In progress
- Status changed from In progress to 12
- Assignee changed from Jonathan CLARKE to Vincent MEMBRÉ
Looks good. Not to be merged yet.
- Status changed from 12 to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:d50a188df7d8b8cf98fa2f68b9aec7be4b31a3eb.
Applied in changeset policy-templates:commit:056eff64ae653a80d5a8c964b3c17ff070e5fc51.
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.9.0~rc1, which was released on Friday 13/12/2013.
Check out:
- Tracker changed from Enhancement to User story
Also available in: Atom
PDF