From: Daniel J Walsh <dwalsh@redhat.com>
To: Dan Pou <danielp@sgi.com>
Cc: SELinux-NSA <SELinux@tycho.nsa.gov>
Subject: Re: Programmatic domain change to unprivileged role
Date: Fri, 09 Aug 2013 05:59:54 -0400 [thread overview]
Message-ID: <5204BD9A.5090108@redhat.com> (raw)
In-Reply-To: <20130808195857.GB23152@localhost>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 08/08/2013 03:58 PM, Dan Pou wrote:
> Thanks for the suggestion about strace, that is pointing to the problem. I
> need to check the policy rules I have been adding to see how I got here:
>
> write(3, "user_u:sysadm_r:sysadm_t:s0\0", 28) = -1 EINVAL (Invalid
> argument)
>
Most likely user_u does not allowed sysadm_r
semanage user -l | grep user_u
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlIEvZoACgkQrlYvE4MpobOx3wCg0XS4z3Gw5U0lcYRiN/bE6X9y
KWYAn2QbXMP580qcCmftJBBOdQzJhivh
=6NHy
-----END PGP SIGNATURE-----
--
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.
next prev parent reply other threads:[~2013-08-09 9:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-05 19:07 Programmatic domain change to unprivileged role Dan Pou
2013-08-06 20:15 ` Stephen Smalley
2013-08-06 20:37 ` Dan Pou
2013-08-07 12:28 ` Stephen Smalley
2013-08-07 12:41 ` Stephen Smalley
2013-08-08 19:58 ` Dan Pou
2013-08-09 9:59 ` Daniel J Walsh [this message]
2013-08-09 12:51 ` Stephen Smalley
2013-08-20 20:05 ` Dan Pou
2013-08-21 7:54 ` Dominick Grift
2013-08-21 14:05 ` Dan Pou
2013-08-21 15:58 ` Dominick Grift
2013-08-21 14:22 ` Stephen Smalley
2013-08-21 14:27 ` Stephen Smalley
2013-08-22 22:50 ` Dan Pou
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=5204BD9A.5090108@redhat.com \
--to=dwalsh@redhat.com \
--cc=SELinux@tycho.nsa.gov \
--cc=danielp@sgi.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.