All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: Bryan Harris <bryanlharris@me.com>,
	"selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: new to selinux
Date: Fri, 10 Jan 2014 09:44:24 -0500	[thread overview]
Message-ID: <52D00748.9070205@tycho.nsa.gov> (raw)
In-Reply-To: <441837E5-55B1-463C-A8E2-7F48F2C847E0@me.com>

On 01/10/2014 04:16 AM, Bryan Harris wrote:
> Hello,
> 
> I'm wondering if it is possible to use selinux network & process labeling, iptables, and something like /usr/bin/script to create an environment where we can enforce session recording for ssh sessions.
> 
> We will soon have a requirement to record our actions on customer environments, but at the same time we also need to block users who have not activated the recording.  Is selinux policy an appropriate way to accomplish these requirements?  I'd like to search for the details and learn more, but if I'm taking the wrong approach I'd like to know that before starting out.
> 
> Any guidance is greatly appreciated.  Thanks in advance.

I think linux-audit is where you want to be,
https://www.redhat.com/mailman/listinfo/linux-audit

  parent reply	other threads:[~2014-01-10 14:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-10  9:16 new to selinux Bryan Harris
2014-01-10  9:33 ` Ilya Frolov
2014-01-10 13:47   ` Daniel J Walsh
2014-01-10 14:44 ` Stephen Smalley [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-08-10 15:48 nitin kanaskar
2005-08-10 16:46 ` Stephen Smalley
2002-08-22 19:03 New to SELinux M. H.
2002-08-19 21:26 Westerman, Mark
2002-08-20 11:37 ` Stephen Smalley
2002-08-19 20:33 Jeremy Kusnetz
2002-08-19 20:47 ` Russell Coker
2002-08-20 10:51 ` Stephen Smalley

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=52D00748.9070205@tycho.nsa.gov \
    --to=sds@tycho.nsa.gov \
    --cc=bryanlharris@me.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.