Actions
User story #7690
closedForce classic protocol on CFEngine 3.7
Status:
Released
Priority:
N/A
Assignee:
Category:
System techniques
Target version:
Effort required:
Name check:
Fix check:
Regression:
Description
The TLS protocol is used by default in CFEngine 3.7, but we will keep classic for now (especially because it breaks skipidentify).
Updated by Alexis Mousset almost 9 years ago
- Status changed from New to In progress
Updated by Alexis Mousset almost 9 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/830
Updated by Alexis Mousset almost 9 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-techniques|26ae24002e30b8836b5abe8fa80a332dd91d8240.
Updated by Benoît PECCATTE almost 9 years ago
Applied in changeset rudder-techniques|935b6b3aa591884c68d6ae31d6d9f63ddfdcc285.
Updated by Benoît PECCATTE almost 9 years ago
- Subject changed from Use classic protocol in Rudder 3.2 to Force classic protocol on CFEngine 3.7
Updated by Benoît PECCATTE almost 9 years ago
- Status changed from Pending release to Released
Updated by Benoît PECCATTE almost 9 years ago
This bug has been fixed in Rudder 3.2.0~rc2 which was released today.
Updated by Alexis Mousset almost 9 years ago
- Related to User story #7835: Enable TLS for file copy between server and agent added
Updated by Nicolas CHARLES over 8 years ago
Ha, actually, this should go also in 3.1
Updated by Nicolas CHARLES over 8 years ago
- Related to Bug #8458: If using Rudder Server 3.1 and a node with agent 3.2, protocol used is TLS added
Actions