Alex Kost skribis:
> 宋文武 (2016-03-07 18:18 +0300) wrote:
>
>> 于 2016年3月7日 GMT+08:00下午8:18:44, l...@gnu.org 写到:
>>
>> l...@gnu.org (Ludovic Courtès) skribis:
>>
>> myglc2 skribis:
>>
>> glc@g1 ~$ ssh glc4@g1
>> glc4@g1's password:
>> glc4@g1 ~$
宋文武 (2016-03-07 18:18 +0300) wrote:
> 于 2016年3月7日 GMT+08:00下午8:18:44, l...@gnu.org 写到:
>
> l...@gnu.org (Ludovic Courtès) skribis:
>
> myglc2 skribis:
>
> glc@g1 ~$ ssh glc4@g1
> glc4@g1's password:
> glc4@g1 ~$ umask
>
>
>
于 2016年3月7日 GMT+08:00下午8:18:44, l...@gnu.org 写到:
>l...@gnu.org (Ludovic Courtès) skribis:
>
>> myglc2 skribis:
>>
>>> glc@g1 ~$ ssh glc4@g1
>>> glc4@g1's password:
>>> glc4@g1 ~$ umask
>>>
>>
>> Oh indeed, I can reproduce it.
>>
>> The problem is that lshd resets the umask when it starts (in
l...@gnu.org (Ludovic Courtès) skribis:
> myglc2 skribis:
>
>> glc@g1 ~$ ssh glc4@g1
>> glc4@g1's password:
>> glc4@g1 ~$ umask
>>
>
> 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.
>
>
l...@gnu.org (Ludovic Courtès) writes:
> myglc2 skribis:
>
>> glc@g1 ~$ ssh glc4@g1
>> glc4@g1's password:
>> glc4@g1 ~$ umask
>>
>
> 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.
>
> P
myglc2 skribis:
> glc@g1 ~$ ssh glc4@g1
> glc4@g1's password:
> glc4@g1 ~$ umask
>
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 (althou
l...@gnu.org (Ludovic Courtès) writes:
> I can’t reproduce this. For instance, in the system created with:
>
> guix system vm gnu/system/examples/bare-bones.tmpl
>
> ‘umask’ returns 0022.
>
> Could it be that your user accounts have shell startup files like
> ~/.bashrc that specify a different
I can’t reproduce this. For instance, in the system created with:
guix system vm gnu/system/examples/bare-bones.tmpl
‘umask’ returns 0022.
Could it be that your user accounts have shell startup files like
~/.bashrc that specify a different umask?
Thanks,
Ludo’.
out of the box, umask should default to something more typical.