All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Justin P. Mattock" <justinmattock@gmail.com>
To: AlannY <m@alanny.ru>
Cc: SELinux@tycho.nsa.gov
Subject: Re: Policy is not managed or store cannot be accessed
Date: Wed, 20 Jan 2010 12:45:48 -0800	[thread overview]
Message-ID: <4B576B7C.8020606@gmail.com> (raw)
In-Reply-To: <20100120202135.GA6124@alanny-pc.lcl.starlink.ru>

On 01/20/10 12:21, AlannY wrote:
> Hi there. I'm new in SELinux world. I'm trying to setup SELinux in Archlinux. Everything seems ok.
> Everything successfully built and even runs.
>
> But when I'm trying to do something with SELinux (semanage, semodule), I'm getting to following error:
>
>      %# semanage login -l
>      /usr/sbin/semanage: SELinux policy is not managed or store cannot be accessed.
>
> I don't know what I can do in this situation. I've already asked on Archlinux forum about this problem,
> but there are no experts in SELinux, so no one answered.
>
> Sestatus tells me, that SELinux is working:
>
>      %# sestatus
>      SELinux status:                 enabled
>      SELinuxfs mount:                /selinux
>      Current mode:                   permissive
>      Mode from config file:          permissive
>      Policy version:                 24
>      Policy from config file:        refpolicy
>
> When I'm trying to go to enforcement, the system is hang off. I think, it's normal, because of AVC deniels in log.
> I can solve it by creating new module, but I cannot load it, because of 1st error (not managed/not accessed).
>
> I'm
>      %# id -Z
>      root:staff_r:insmod_t
>
> What can I do?
>
> I think, that my problem is with version mismatch of selinux tools (checkpolicy,semanage) and refpolicy.
> Where can I check it? Currently I have:
>
>      kernel26-selinux-2.6.31
>      selinux-coreutils-7.6
>      selinux-pam-1.1.0
>      refpolicy-2.20091117
>      selinux-sysvinit-2.86
>      checkpolicy-2.0.20
>      libselinux-2.0.89
>      libsemanage-2.0.42
>      libsepol-2.0.41
>      selinux-usr-policycoreutils-2.0.77
>      sepolgen-1.0.18
>
> That everything I have.
>
> Thanks for patience.


I was getting the same thing until
I did sudo /usr/sbin/semanage *


Justin P. mattock

--
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:[~2010-01-20 20:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-20 20:21 Policy is not managed or store cannot be accessed AlannY
2010-01-20 20:45 ` Justin P. Mattock [this message]
2010-01-21 12:27   ` AlannY
2010-01-21 19:01     ` Justin P. Mattock
2010-01-20 20:46 ` Stephen Smalley
2010-01-21 12:28   ` AlannY
2010-01-21 13:29     ` Stephen Smalley
2010-01-21 14:17       ` AlannY
2010-01-21 14:37         ` Stephen Smalley
2010-01-21 14:57         ` Stephen Smalley
2010-01-21 12:44   ` AlannY

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=4B576B7C.8020606@gmail.com \
    --to=justinmattock@gmail.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=m@alanny.ru \
    /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.