All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SELinux <SELinux@tycho.nsa.gov>
Subject: Re: Patch to policycoreutils
Date: Mon, 31 Jan 2005 10:27:16 -0500	[thread overview]
Message-ID: <1107185236.24654.97.camel@moss-spartans.epoch.ncsc.mil> (raw)
In-Reply-To: <41FE4B16.1050206@redhat.com>

On Mon, 2005-01-31 at 10:13, Daniel J Walsh wrote:
> >1) The first sed substitution changes:
> >/var/tmp/vi\.recover  -d      system_u:object_r:tmp_t
> >to:
> >/var/tmp/vi*
> >
> >  
> >
> This looks good.

i.e. We can drop the first substitution entirely, right?  Shell will
correctly handle \. as is.

> >2) The second sed substitution changes:
> >/usr/lib(64)?/[^/]*thunderbird[^/]*/thunderbird --      system_u:object_r:bin_t
> >to:
> >/usr/lib*
> >
> >This is due to sed itself performing regex matching for the .* sequence,
> >i.e. it consumes anything after an open parens.  Possibly you could
> >escape it if that is what you intended, e.g. \.\*.
> >
> >  
> >
> Huh?   you need to match both /usr/lib/ and /usr/lib64/  So I don't see 
> anyway of doing this withoug /usr/lib*

Possibly /usr/lib{64,}/*thunderbird*/thunderbird.  The point being that
we don't need to relabel all of /usr/lib here.

> >Similar issues with the other substitutions that are using .*, I think,
> >e.g. changing:
> >/usr/bin/[xgkw]dm     --      system_u:object_r:xdm_exec_t
> >to:
> >/usr/bin/*
> >
> >But the shell would have correctly handled /usr/bin/[xgkw]dm without any
> >change at all.
> >
> >  
> >
> But there are lots of other stuff that could be in between the [] correct?

Yes, we would have to distinguish the cases that can be handled by the
shell vs. the use of other regex metacharacters within the brackets.

> Yes, good catch.  First off we should remove /u?dev and switch to /dev 
> in policy since this was
> only a pre-fc3 problem.  But as in other message any sed experts who can 
> change
> 
> /u*dev --> /{u,}dev

More generally, we would want to replace x? or (x)? with {x,}.  Might be
easier to do in perl or other languages than just sed.

-- 
Stephen Smalley <sds@tycho.nsa.gov>
National Security Agency


--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2005-01-31 15:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1106927779.32737.59.camel@moss-spartans.epoch.ncsc.mil>
2005-01-28 16:29 ` Patch to policycoreutils Daniel J Walsh
2005-01-28 19:51   ` Stephen Smalley
2005-01-28 20:25     ` Daniel J Walsh
2005-01-28 20:30       ` Stephen Smalley
2005-01-31 14:14       ` Stephen Smalley
2005-01-31 15:13         ` Daniel J Walsh
2005-01-31 15:27           ` Stephen Smalley [this message]
2005-01-31 18:49             ` Daniel J Walsh
2005-02-01 14:22               ` Stephen Smalley
2009-04-01 14:10 patch " Daniel J Walsh
2009-04-22 22:03 ` Chad Sellers
2009-04-23  1:50   ` Daniel J Walsh
2009-04-23 20:01     ` Chad Sellers
2009-05-18 15:29       ` Joshua Brindle

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=1107185236.24654.97.camel@moss-spartans.epoch.ncsc.mil \
    --to=sds@tycho.nsa.gov \
    --cc=SELinux@tycho.nsa.gov \
    --cc=dwalsh@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.