Bug #11422
closed
Incomplete description of the behaviour of technique copyGitFile, that may result in broken permissions of whole folder
Added by Nicolas CHARLES about 6 years ago.
Updated about 6 years ago.
Severity:
Major - prevents use of part of Rudder | no simple workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Very Small
Description
The Technique copyGitFile allow to copy a file from the shared folder.
However, if in "full path" we put a folder, rather of a specific file name, the permission part apply to the WHOLE folder, resulting usually in painful result
We should clearly state that permission apply to the defined "full path", and can so apply to a complete folder, and break everything is not used correctly.
- Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
- Effort required set to Very Small
- Priority changed from 50 to 86
I'm setting it to major, because the consequences of that problem are EXTREMELLY hard to heal (imagine changing all your perms on /etc/...)
- Assignee set to Alexis Mousset
- Status changed from New to In progress
- Status changed from In progress to Pending technical review
- Assignee changed from Alexis Mousset to Benoît PECCATTE
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/1204
- Status changed from Pending technical review to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 3.1.24, 4.1.8 and 4.2.1 which were released today.
Also available in: Atom
PDF