User story #3115
closed
Technique "Download From A Shared Folder": Add possibility to set SUID and SGID to files copied
Added by Nicolas CHARLES almost 12 years ago.
Updated over 9 years ago.
Description
Some users needs to define (or undefine) setuid and setgid on files they copy from a remote location.
The technique doesn't allow that for the moment, and it really should
There are two different option for this :
- Change the "mode" field (array of checkbox) to have as well the setuid and setgid (resulting in 4 rows rather than 3), but I guess it might be a bit too much, as it is not that common and might cause unsuspecting user to wrongly set it (especially if they are not familiar with this behaviour)
- add three new fields in the technique : Define the ID upon execution : Yes/Don't Change ; Set user ID upon execution : true/false; Set group ID upon execution : true/false
- Target version changed from 2.5.0~beta1 to 2.5.0~rc1
Found it! I knew it was there somewhere: this is related to #2914.
- Status changed from New to 8
- Assignee set to Matthieu CERDA
Matthieu has agreed to work on this.
- Target version changed from 2.5.0~rc1 to 2.3.10
- Status changed from 8 to 13
Development is over, functionnal review pending.
- Status changed from 13 to Pending release
- Project changed from Rudder to 24
- Category deleted (
Techniques)
- Status changed from Pending release to Released
- Status changed from Released to New
- Target version changed from 2.3.10 to 84
- % Done changed from 100 to 0
This ticket has NOT been released. This is a mistake in the subtask (#3141) which was misunderstood.
- Target version changed from 84 to 2.4.7
- Target version changed from 2.4.7 to 2.4.8
- Subject changed from The technique Copy from Shared Folder should allow to define setuid and setgid to Technique "Download From A Shared Folder": Add possibility to set SUID and SGID to files copied
- Status changed from New to 13
- Assignee changed from Matthieu CERDA to Nicolas PERRON
During the functional review of the implementation, we have decided to consider that this functionnality should be added into the Rudder code in order to have only one variable. Neverthless it means to add this modification on Rudder 2.8 and this functionnality is needed before Rudder 2.8.
So, the comprise is to implement the functionnality into the Techniques until Rudder 2.8.
Nicolas PERRON wrote:
During the functional review of the implementation, we have decided to consider that this functionnality should be added into the Rudder code in order to have only one variable. Neverthless it means to add this modification on Rudder 2.8 and this functionnality is needed before Rudder 2.8.
So, the comprise is to implement the functionnality into the Techniques until Rudder 2.8.
A new ticket has been made for that: #3875
- Status changed from 13 to Pending release
- Status changed from Pending release to Released
This bug has been fixed in Rudder 2.4.8, which was released today.
Check out:
- Project changed from 24 to Rudder
- Category set to Techniques
Also available in: Atom
PDF