All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: Sven Vermeulen <sven.vermeulen@siphos.be>,
	SELinux <selinux@tycho.nsa.gov>
Subject: Re: SELinux Userspace Release: 20140826-rc1
Date: Fri, 29 Aug 2014 08:11:00 -0400	[thread overview]
Message-ID: <54006DD4.6040706@tycho.nsa.gov> (raw)
In-Reply-To: <CAPzO=Nwwbn8ihZmuj-JGKPUonZwjS69Zjg=1ix1EDbR=QQ56oQ@mail.gmail.com>

On 08/28/2014 04:52 PM, Sven Vermeulen wrote:
> On Thu, Aug 28, 2014 at 10:15 PM, Stephen Smalley <sds@tycho.nsa.gov> wrote:
>>> When running the semanage_migrate_script I get the following problem:
>>>
>>> Migrating from /etc/selinux/mcs/modules/active to /var/lib/selinux/mcs/active
>>> Attempting to rebuild policy from /var/lib/selinux
>>> sysnetwork: Warning: 'else' blocks in optional statements are
>>> unsupported in CIL. Dropping from output.
>>> Segmentation fault
> [...]
>> Can you provide a copy of your original policy prior to conversion?
> 
> If you mean the policy.29 file, certainly. You can wget it from
> http://dev.gentoo.org/~swift/tmp/20140828-policy.29

No, the contents of /etc/selinux/mcs.  The migration script converts the
old policy module store, not the final kernel policy file.

  reply	other threads:[~2014-08-29 12:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26 15:31 SELinux Userspace Release: 20140826-rc1 Steve Lawrence
2014-08-27 15:06 ` Sven Vermeulen
2014-08-27 16:10   ` Steve Lawrence
2014-08-28 19:58     ` Sven Vermeulen
2014-08-28 20:15       ` Stephen Smalley
2014-08-28 20:52         ` Sven Vermeulen
2014-08-29 12:11           ` Stephen Smalley [this message]
2014-08-29 12:56             ` Steve Lawrence
2014-08-29 14:00               ` Sven Vermeulen
2014-08-29 14:14                 ` Stephen Smalley
2014-08-29 14:18                   ` Stephen Smalley
2014-08-29 14:22                   ` Steve Lawrence
2014-09-14  9:31                     ` Sven Vermeulen
2014-09-15 12:12                       ` Steve Lawrence

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=54006DD4.6040706@tycho.nsa.gov \
    --to=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    --cc=sven.vermeulen@siphos.be \
    /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.