Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Monday 23 May 2005 9:44 am, Ben Williams wrote: > Thanks, this gets me really close to what I wanted. Forcing my users' > umask is actually no problem but it doesn't do anything because sftp/scp > ignores the umask and maintains the permissions on the source file. Now I > just need to find a way to force the permissions that sftp/scp uses. scp uses the umask you set up. Remember that umask is a shell builtin and only applies to the current process and any subprocess that is started from that process. so: umask 0xxx scp remote:<path> . The file that you receive will have premissions based on your umask. But is you send the files from a remote system, it will use the umask that is inherited by the ssh daemon. -- Jerry Feldman <gaf at blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |