From: Joe Perches <joe@perches.com>
To: "Serge E. Hallyn" <serge@hallyn.com>
Cc: John Johansen <john.johansen@canonical.com>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
Paul Moore <paul@paul-moore.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
Casey Schaufler <casey@schaufler-ca.com>,
Kentaro Takeda <takedakn@nttdata.co.jp>,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
James Morris <jmorris@namei.org>,
linux-security-module@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org,
selinux@tycho.nsa.gov
Subject: Re: [-next PATCH] security: use octal not symbolic permissions
Date: Wed, 13 Jun 2018 16:49:47 -0700 [thread overview]
Message-ID: <85d6e86b7829b42e69feab8e8dbe93a30b5fa4f1.camel@perches.com> (raw)
In-Reply-To: <20180613151921.GA27375@mail.hallyn.com>
On Wed, 2018-06-13 at 10:19 -0500, Serge E. Hallyn wrote:
> Using octal and not symbolic permissions is preferred by many as more
> > readable.
> >
> > see: https://lkml.org/lkml/2016/8/2/1945
>
> Heh, well see also https://lkml.org/lkml/2016/8/2/2062 .
We all love Al.
I did reply then too.
cheers, Joe
prev parent reply other threads:[~2018-06-13 23:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-11 19:01 Joe Perches
2018-06-11 20:07 ` Casey Schaufler
2018-06-12 20:32 ` James Morris
2018-06-12 21:12 ` Paul Moore
2018-06-12 21:29 ` John Johansen
2018-06-12 21:36 ` Mimi Zohar
2018-06-13 0:29 ` Joe Perches
2018-06-13 15:49 ` Paul Moore
2018-06-13 16:04 ` Joe Perches
2018-06-13 16:19 ` Paul Moore
2018-06-13 19:30 ` Joe Perches
2018-06-13 19:57 ` Paul Moore
2018-06-13 21:14 ` Casey Schaufler
2018-06-13 21:22 ` Paul Moore
2018-06-13 15:19 ` Serge E. Hallyn
2018-06-13 23:49 ` Joe Perches [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=85d6e86b7829b42e69feab8e8dbe93a30b5fa4f1.camel@perches.com \
--to=joe@perches.com \
--cc=casey@schaufler-ca.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=serge@hallyn.com \
--cc=takedakn@nttdata.co.jp \
--cc=zohar@linux.vnet.ibm.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
all inboxes | Powered by JetHome®