All of lore.kernel.org
 help / color / mirror / Atom feed
From: sven.vermeulen@siphos.be (Sven Vermeulen)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH]: clarify the file_contexts.subs_dist configuration file usage
Date: Wed, 15 Aug 2012 10:20:39 +0200	[thread overview]
Message-ID: <20120815082038.GA1471@siphos.be> (raw)
In-Reply-To: <502B5A26.5070309@trentalancia.com>

On Wed, Aug 15, 2012 at 10:13:26AM +0200, Guido Trentalancia wrote:
> > This seems to break policycoreutils:
> >
> > # semanage fcontext -l
> > /usr/sbin/semanage: too many values to unpack (expected 2)
> >
> > Undoing the comment change fixes things again.
> 
> Is semanage using the standard library functions to read the file ? 
> Because I had a very quick look through the library and the #-comment 
> skipping code seemed to be there...

                        fd = open(selinux.selinux_file_context_subs_dist_path(), "r")
                        for i in fd.readlines():
                                target, substitute = i.split()
                                self.equiv_dist[target] = substitute
                        fd.close()

Just opens the file, reads lines and assumes there are always two
values (target & substitute) on each line. This is from seobject.py.

Wkr,
	Sven Vermeulen

PS Sorry for mailing you directly the first time, forgot to update the "To" header...

  reply	other threads:[~2012-08-15  8:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-10 13:13 [refpolicy] [PATCH]: clarify the file_contexts.subs_dist configuration file usage Guido Trentalancia
2012-08-14 12:03 ` Christopher J. PeBenito
2012-08-15  8:02   ` Sven Vermeulen
2012-08-15  8:13     ` Guido Trentalancia
2012-08-15  8:20       ` Sven Vermeulen [this message]
2012-08-15  8:38         ` Guido Trentalancia
2012-08-15  8:45           ` Sven Vermeulen
2012-08-15  9:48             ` Guido Trentalancia
  -- strict thread matches above, loose matches on Subject: below --
2012-08-18 12:30 Guido Trentalancia

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=20120815082038.GA1471@siphos.be \
    --to=sven.vermeulen@siphos.be \
    --cc=refpolicy@oss.tresys.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.