mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: serue@us.ibm.com
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] TOMOYO: Add recursive directory matching operatorsupport.
Date: Wed, 25 Nov 2009 23:59:21 +0900	[thread overview]
Message-ID: <200911252359.DFI56759.FMOSVOFQFJLHOt@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <20091125140009.GA602@us.ibm.com>

Hello.

Serge E. Hallyn wrote:
> Are you sure you want to use this syntax for 'in_repeating'?

Yes.

I don't have a plan to implement conventional regular expressions.
There are many variants for regular expressions (e.g. shell, perl, sed) and
users likely use characters with special meaning without knowing.
TOMOYO treats a character as literal unless prefixed by '\' character so that
users who didn't know the meaning of a character don't get unwanted results.

> As a unix admin, I expect something like
> 
> 	/{bin,sbin}/init
> (or more likely /{s,}bin/init )
> 
> to mean match both /bin/init and /sbin/init.

You will be able to use

  path_group ALL_INIT /bin/init
  path_group ALL_INIT /sbin/init

    +

  allow_execute @ALL_INIT

in the future (hopefully in Linux 2.6.34).

  reply	other threads:[~2009-11-25 14:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-24 13:00 [PATCH] TOMOYO: Add recursive directory matching operator support Tetsuo Handa
2009-11-24 23:37 ` John Johansen
2009-11-25  7:52 ` James Morris
2009-11-25 14:00 ` Serge E. Hallyn
2009-11-25 14:59   ` Tetsuo Handa [this message]
2009-11-25 15:27     ` [PATCH] TOMOYO: Add recursive directory matching operatorsupport Serge E. Hallyn

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=200911252359.DFI56759.FMOSVOFQFJLHOt@I-love.SAKURA.ne.jp \
    --to=penguin-kernel@i-love.sakura.ne.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=serue@us.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®