All of lore.kernel.org
 help / color / mirror / Atom feed
From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] Help with policy definition.
Date: Tue, 7 Jun 2011 08:03:50 -0400	[thread overview]
Message-ID: <4DEE13A6.2070704@tresys.com> (raw)
In-Reply-To: <BANLkTi=2=mMMTE9raGH+HM8sa7SK3VX=fA@mail.gmail.com>

On 06/06/11 19:26, Sam Gandhi wrote:
> I am writing a policy for embedded device that I am working with. When
> I am in permissive mode I can login to my console located on
> /dev/ttymxc1.
> 
> which generate AVC message
> 
> user.notice kernel: type=1400 audit(165.890:8): avc:  denied  {
> relabelto } for  pid=605 comm="login" name="ttymxc1" dev=tmpfs
> ino=1475 scontext=system_u:system_r:kernel_t
> tcontext=user_u:object_r:tty_device_t tclass=chr_file

Looks like your login program is running in the wrong context.  It
should be local_login_t, not kernel_t.  Check the label on your init
program (eg /sbin/init) which should be init_exec_t.


> which audit2allow says should translate to :
> 
>      allow kernel_t tty_device_t:chr_file relabelto;
> 
> Even if with above allow rule when in enforcing mode I am not able to
> login to my serial console and I get message on the console.
> 
> login: chsid(/dev/ttymxc1, user_u:object_r:tty_device_t) failed:
> 
> /dev/ttymxc1 in my case has label of  user_u:object_r:tty_device_t
> 
> What am I missing in my configuration or any hints on how I should go
> about debugging this issue/


-- 
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com

  parent reply	other threads:[~2011-06-07 12:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-06 23:26 [refpolicy] Help with policy definition Sam Gandhi
2011-06-07  3:52 ` Guido Trentalancia
2011-06-07 15:30   ` Sam Gandhi
2011-06-07 19:42     ` Guido Trentalancia
2011-06-07 12:03 ` Christopher J. PeBenito [this message]
2011-06-07 19:11   ` Guido Trentalancia
2011-06-07 19:28     ` Christopher J. PeBenito

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=4DEE13A6.2070704@tresys.com \
    --to=cpebenito@tresys.com \
    --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.