From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: 宋文武 <iyzsong@openmailbox.org>,
iyzsong@member.fsf.org, 22650-done@debbugs.gnu.org
Subject: bug#22650: guixSD default umask is 0000
Date: Tue, 08 Mar 2016 23:33:49 +0100 [thread overview]
Message-ID: <87twkgfvle.fsf@gnu.org> (raw)
In-Reply-To: <87k2lekjrc.fsf@gmail.com> (Alex Kost's message of "Tue, 08 Mar 2016 01:25:59 +0300")
Alex Kost <alezost@gmail.com> skribis:
> 宋文武 (2016-03-07 18:18 +0300) wrote:
>
>> 于 2016年3月7日 GMT+08:00下午8:18:44, ludo@gnu.org 写到:
>>
>> ludo@gnu.org (Ludovic Courtès) skribis:
>>
>> myglc2 <myglc2@gmail.com> skribis:
>>
>> glc@g1 ~$ ssh glc4@g1
>> glc4@g1's password:
>> glc4@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.
>
> I agree ("ArchLinux" also has "umask 022" in /etc/profile).
Done in 112024826d3283284654475a50ccef81c697e2c9.
Thanks for your feedback,
Ludo’.
prev parent reply other threads:[~2016-03-08 22:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 14:36 bug#22650: guixSD default umask is 0000 myglc2
2016-02-21 23:17 ` Ludovic Courtès
2016-02-22 16:24 ` myglc2
2016-02-24 15:41 ` Ludovic Courtès
2016-03-01 2:25 ` myglc2
2016-03-07 12:18 ` Ludovic Courtès
2016-03-07 15:18 ` 宋文武
2016-03-07 22:25 ` Alex Kost
2016-03-08 22:33 ` Ludovic Courtès [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87twkgfvle.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=22650-done@debbugs.gnu.org \
--cc=alezost@gmail.com \
--cc=iyzsong@member.fsf.org \
--cc=iyzsong@openmailbox.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).