GNU bug report logs -
#22650
umask is 0000 when logging in over SSH (with lshd running)
Previous Next
Reported by: myglc2 <myglc2 <at> gmail.com>
Date: Sat, 13 Feb 2016 14:37:01 UTC
Severity: normal
Done: ludo <at> gnu.org (Ludovic Courtès)
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
于 2016年3月7日 GMT+08:00下午8:18:44, ludo <at> gnu.org 写到:
>ludo <at> gnu.org (Ludovic Courtès) skribis:
>
>> myglc2 <myglc2 <at> gmail.com> skribis:
>>
>>> glc <at> g1 ~$ ssh glc4 <at> g1
>>> glc4 <at> g1's password:
>>> glc4 <at> g1 ~$ umask
>>> 0000
>>
>> Oh indeed, I can reproduce it.
>>
>> The problem is that lshd resets the umask when it starts (in
>> src/daemon.c:daemon_init) but never changes it again.
>>
>> Perhaps we should be using pam_umask and login.defs (although I’m
>unsure
>> if lshd would honor it), or alternately add explicitly set the umask
>in
>> /etc/profile.
>>
>> Thoughts?
>
>宋文武 & Alex: WDYT? (Asking you since I know you’re already familiar
>with these things. :-))
>
>Ludo’.
I never pay attention to umask, but set it in /etc/profile seem the right thing to me. IIRC, debian and exherbo set it in there too.
[Message part 2 (text/html, inline)]
This bug report was last modified 9 years and 82 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.