On Thu, 2004-02-05 at 09:10, Chris Gehlker wrote:
> On Feb 5, 2004, at 8:44 AM, Craig White wrote:
> 
> > actually WinSCP3 has preferences that allow you to set default umask 
> > (as
> > much as may be permitted by the umasking features of the host system)
> > and I have left these preferences unset deliberately
> 
> I don't think you *can* leave them unset. You just get the defaults.
---
ok - if you look back at my original message...

when I obtain a shell as user exchange
mkdir testdir
touch testfile2
ls -l
drwxrwsr-x    2 exchange dom_users     4096 Feb  5 10:14 testdir
-rw-rw-r--    1 exchange dom_users        0 Feb  5 10:14 testfile2

files/directories created are group writable

now I delete both the directory and testfile

and back at root prompt (in another directory)
# touch testfile2
# mkdir testdir
# chmod 777 testdir
# chmod 777 testfile2
# scp testfile2 exchange@localhost:
exchange@localhost's password:
testfile2            100%
|***********************************************************************************************|   347       00:00
# scp -r testdir exchange@localhost:
exchange@localhost's password:
#
and then finally...
back in the original directory...
ls -l
drwxrwxrwx    2 exchange dom_users     4096 Feb  5 10:20 testdir
-rwxr-xr-x    1 exchange dom_users      347 Feb  5 10:20 testfile2

the directory is group writable, the file is not. This means that only
the user exchange can delete these files. This is not acceptable. This
has nothing to do with WinSCP

Craig