Timeline for User can't touch -t
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2011 at 12:30 | comment | added | Caleb | I think the next thing to look into is setting up ACLs (Access Control Lists), but I have little experience in this area so maybe some guru can add an answer and explain if and how this can be done. | |
| Jun 15, 2011 at 12:13 | comment | added | Tom Auger | Thanks - this is interesting, although the developer is on a Windows box, so I'm not sure rsync is the best way to go. Again, as I mentioned in the edit to my post, I want this solution to work for any average user, not some priviledged users, beyond someone belonging to the group that owns that particular directory. | |
| Jun 15, 2011 at 9:29 | comment | added | Caleb |
You are right, allowing sudo rsync is very difficult to restrict. I only suggested it because the OP said the user already had sudo access.
|
|
| Jun 15, 2011 at 8:44 | comment | added | Gilles 'SO- stop being evil' | What would the sudo rule be? Simply allowing rsync would allow the user to overwrite arbitrary files. It's pretty hard to get argument limitations right, and anyway here I think you'd need to put restrictions on rsync's input, which is technically possible with a wrapper script but not easy. | |
| Jun 14, 2011 at 21:13 | history | answered | Caleb | CC BY-SA 3.0 |