On Sun, Nov 16, 2008 at 8:35 PM, Mario Goebbels <me at tomservo.cc> wrote:
> > The one thing I see offhand is that using the -p > > option with scp should cause the > > original permissions to be preserved; otherwise, scp > > uses whatever umask > > it inherits (from the calling program on the local > > side probably, or from sshd on > > the remote side?); Sun's sshd I think uses UMASK= > > from /etc/default/login, > > or defaults to 022 if that isn't set. > > > > That's all from a _very_ quick look at the code...I > > don't claim I got it right, > > and I didn't look at sftp. > > Well, I have the same issue right now on my dedicated webserver. I've set > PermitUserEnvironment and set UMASK=0002 in ~/.ssh/environment, it does > nothing. I'm searching on Google since a while, I just find more frustrated > users. > > As I said before, try putting the umask in the scp user's .profile file. That is, the user which is logged into, eg on the SCP/SSH server. -- Any sufficiently advanced technology is indistinguishable from magic. Arthur C. Clarke My blog: http://initialprogramload.blogspot.com -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/opensolaris-help/attachments/20081117/f9a0d939/attachment.html>
