All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ed Street" <blacknet@simplyaquatics.com>
To: "'Stephen Smalley'" <sds@tislabs.com>
Cc: <selinux@tycho.nsa.gov>
Subject: RE: lsm3 notes
Date: Tue, 9 Jul 2002 09:33:24 -0400	[thread overview]
Message-ID: <005401c2274d$33387be0$0a01a8c0@ed> (raw)
In-Reply-To: <Pine.GSO.4.33.0207090836321.27193-100000@raven>

Hello,

=> > I keep seeing /dev/xconsole avc's.
=> > This is from startup
=> > allow initrc_t device_t:fifo_file { setattr };
=> >         #EXE=/bin/chmod  PATH=/dev/xconsole   :  setattr
=> 
=> /dev/xconsole doesn't exist on my systems.  Feel free to define an
=> appropriate type and submit a patch to types/device.te and
=> file_contexts/type.fc, along with a patch to whatever domains require
=> access.  What creates this FIFO?

I'm not 100% sure why it's doing the file_fifo or the xconsole.  It does
warrant further investigation.

=> 
=> > startup as well
=> > allow initrc_t resolv_conf_t:file { setattr };
=> >         #EXE=/bin/chmod  PATH=/etc/resolv.conf   :  setattr
=> 
=> Why are your rc scripts changing the mode on /etc/resolv.conf?
=> In any event, this is probably harmless.

I think at load of services it's looking at /etc/resolv.conf for dns
issues but it eludes me as to why setattr is being issued.  Another good
reason for Selinux, is to see what linux is REALLY doing behind our
backs with out our knowing.

=> 
=> > when I ssh into the box
=> > allow sshd_t sysadm_home_t:dir { search };
=> >         #EXE=/usr/sbin/sshd  PATH=/root   :  search
=> 
=> Do you really need to login directly as root?

No I normally ssh in as a user and su to root.  I also noted that the
path is not being set correctly either.

=> 
=> > when I tried to tail syslog as user_r
=> > allow user_t var_log_t:file { getattr read };
=> >         #EXE=/bin/bash  PATH=/var/log/syslog   :  getattr
=> >         #EXE=/usr/bin/tail  PATH=/var/log/syslog   :  read
=> 
=> Do you really want to permit ordinary users to read your logs?

No, this can be ignored and I should have left it out.  Figured I would
see what it gave in this case.

=> 
=> > Most notably problems with sysklogd, and it's not writing events to
=> > /var/log/syslog
=> 
=> Are klogd and syslogd running in the right domains?

Yes klogd and syslogd is running correctly.  Seems that Selinux is
denying access to both on a restart.  I am in agreement they may not
have the correct label (same issue as raid devices )

IN any case this is definitely turning out to be a very fun project to
be working on.  It's proving some rather insightful views into linux.

Ed


--
You have received this message because you are subscribed to the selinux 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:[~2002-07-09 13:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-09  1:16 Is make relabel suposed to be run from policy or or setfiles? JW
2002-07-09  5:33 ` lsm3 notes Ed Street
2002-07-09 12:43   ` Stephen Smalley
2002-07-09 13:33     ` Ed Street [this message]
2002-07-09 14:03       ` Stephen Smalley
2002-07-09 11:49 ` Is make relabel suposed to be run from policy or or setfiles? Stephen Smalley
2002-07-09 16:41   ` JW

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='005401c2274d$33387be0$0a01a8c0@ed' \
    --to=blacknet@simplyaquatics.com \
    --cc=sds@tislabs.com \
    --cc=selinux@tycho.nsa.gov \
    /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.