Bug #4368
closed
Technique "Download a file from the shared folder": permissions defaulted to none (mode 0000)
Added by Jonathan CLARKE almost 11 years ago.
Updated almost 11 years ago.
Description
This technique has a permissions editor to set permissions on the file, which is used by default (there is no option not to set perms). However, there is no default value, so by default no permissions are applied!
This means the Technique copies files that are not at all usable by default.
- Status changed from In progress to Pending technical review
- Assignee changed from Jonathan CLARKE to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder-techniques/pull/270
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset policy-templates:commit:e9ba29ca4164d0c0cad6e5d73255c4caa7095e5b.
Applied in changeset policy-templates:commit:408b2f5784a75085d4441067229df9df244e4b14.
- Status changed from Pending release to Rejected
Yvan, another issue was openend and fix about that : #4368.
I reject this issue as it duplicates #4368 and this one contains the fix!
The fix will be available in next releases (2.6.10, 2.7.7, 2.8.2, 2.9.2) or nightlies
Really thank you!
- Status changed from Rejected to Pending release
Why on earth this issue was modified? It happened when i modified the other issue #4352
I put back in pending release.
- Subject changed from Technique "Download a file from the shared folder": no default value for perms to Can't keep current perms on copied files when using Technique "Download a file from the shared folder"
- Subject changed from Can't keep current perms on copied files when using Technique "Download a file from the shared folder" to Technique "Download a file from the shared folder": permissions defaulted to none (mode 0000)
Vincent, this subject change is not correct - this ticket doesn't allow the current perms to be kept, it just sets a default for new Directives to use (it used to default to 0, so no perms). Reverting.
Thank you Jonathan, I thought this was already the behavior and I clearly misunderstood this issue.
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.6.10 which was released today.
Check out:
Also available in: Atom
PDF
Updated by Jonathan CLARKE 
Updated by 
Updated by