On Thu, 2004-02-05 at 07:58, Chris Gehlker wrote: > On Feb 5, 2004, at 7:50 AM, Chris Gehlker wrote:
>
> >
> > Sounds like a simple WinSCP bug. Their site isn't responding right now
> > so I can't tell if it's a known bug. Actually, I guess "bug" is too
> > strong since I've never seen a claim that WinSCP pays any attention to
> > umask in the documentation. Call it a misfeature.
>
> Responding to my own post.
>
> I found a site which claims that WinSCP has it's own mechanism for
> changing file properties on the target machine. I'm going to guess that
> it's doing a chmod on the files after creating them. I'd investigate
> the WinSCP docs. ---
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. Yes, they can be
set on each user machine but that was beside the point of my question. I
have the same issue regardless of the local application used by Mac or
Windows clients (Mac/SFTP) or niftyTelnet or ???
According to man sshd_config - sftp is the subsystem that is used when
using ssh2 protocol so I'm not sure that scp and sftp are entirely
different things - I can't really tell. What I can tell is that even
with logging turned on to VERBOSE, I still don't get enough information
to tell where the umask variables come from and how to change them -
that's why I asked the list.
(text/plain)