From: Daniel J Walsh <dwalsh@redhat.com>
To: Ilya Frolov <ilya.a.frolov@gmail.com>,
Bryan Harris <bryanlharris@me.com>
Cc: "selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: new to selinux
Date: Fri, 10 Jan 2014 08:47:22 -0500 [thread overview]
Message-ID: <52CFF9EA.30705@redhat.com> (raw)
In-Reply-To: <CABu+-8pi=O=FWO=t-rGo-_9rSjmYagdFvJcjXyWvFKyd6m_NLQ@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 01/10/2014 04:33 AM, Ilya Frolov wrote:
> On Fri, Jan 10, 2014 at 1:16 PM, Bryan Harris <bryanlharris@me.com
> <mailto:bryanlharris@me.com>> 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.
>
> V/r, Bryan _______________________________________________ Selinux mailing
> list Selinux@tycho.nsa.gov <mailto:Selinux@tycho.nsa.gov> To unsubscribe,
> send email to Selinux-leave@tycho.nsa.gov
> <mailto:Selinux-leave@tycho.nsa.gov>. To get help, send an email containing
> "help" to Selinux-request@tycho.nsa.gov
> <mailto:Selinux-request@tycho.nsa.gov>.
>
>
> Hello Bryan,
>
> have a look at ttyrec -- you can set it as shell to do ssh session
> recording per-user and without fiddling in kernel space, and you can
> enforce it that way even without selinux for non-root users.
>
> If you are interested in restricting root user and maybe play with the
> live system -- feel free to contact me offlist, i've done the similar
> things for my selinux playbox, and (i'll check now) i think its still
> alive.
>
>
> regards, ilya
>
>
>
> _______________________________________________ Selinux mailing list
> Selinux@tycho.nsa.gov To unsubscribe, send email to
> Selinux-leave@tycho.nsa.gov. To get help, send an email containing "help"
> to Selinux-request@tycho.nsa.gov.
>
You might want to look at pam_tty_audit also.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEARECAAYFAlLP+eoACgkQrlYvE4MpobMrGgCbBYR6SKD+9jMAi55fWDZ7t9gE
H/oAoJ+qhVbE4go/k59SBwyJCA/ViUoR
=GPVQ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-01-10 13:47 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 [this message]
2014-01-10 14:44 ` Stephen Smalley
-- 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=52CFF9EA.30705@redhat.com \
--to=dwalsh@redhat.com \
--cc=bryanlharris@me.com \
--cc=ilya.a.frolov@gmail.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.