On Mon, Nov 17, 2008 at 10:07 AM, Mario Goebbels <me at tomservo.cc> wrote:
> > 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. > > Doesn't work either. scp causes the shell to be spawned as > non-interactive and thus that file and others aren't read. At least > that's supposedly the explanation about why it doesn't. > > As a workarround you can set UMASK in the "start)" section in this file: /lib/svc/method/sshd But that will affect ssh and scp, for all users. I believe Secure Shell sessions will restore themselves when the user logs in and reads /etc/default/login. -- 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/1ab14dcb/attachment.html>
