From: Michal Marek <mmarek@suse.cz>
To: Yaroslav Halchenko <yoh@onerussian.com>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: doesn't fix for paranoid umask while 'make deb-pkg'
Date: Wed, 28 Oct 2015 11:07:49 +0100 [thread overview]
Message-ID: <56309E75.4070107@suse.cz> (raw)
In-Reply-To: <20151027165527.GO7844@onerussian.com>
Dne 27.10.2015 v 17:55 Yaroslav Halchenko napsal(a):
> $> ls -l /usr/include/linux/ | head
> total 3424
> -rw------- 1 root root 7319 Oct 27 11:20 a.out.h
> -rw------- 1 root root 3670 Oct 27 11:20 acct.h
> -rw------- 1 root root 1077 Oct 27 11:20 adb.h
> -rw------- 1 root root 873 Oct 27 11:20 adfs_fs.h
> -rw------- 1 root root 1481 Oct 27 11:20 affs_hardblocks.h
> -rw------- 1 root root 3920 Oct 27 11:20 agpgart.h
> ...
>
> So I guess there should be somewhere explicit chmod'ing. My umask is
> 077.
Well, you set umask 077, so nobody will be able to steal your precious
headers...
Michal
next prev parent reply other threads:[~2015-10-28 10:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 16:55 doesn't fix for paranoid umask while 'make deb-pkg' Yaroslav Halchenko
2015-10-28 10:07 ` Michal Marek [this message]
2015-10-28 12:35 ` Yaroslav Halchenko
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56309E75.4070107@suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kbuild@vger.kernel.org \
--cc=yoh@onerussian.com \
/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.
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 NNTP newsgroup(s).