From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Grubb Subject: Re: Audit filter by TTY Date: Fri, 26 Apr 2013 13:14:13 -0400 Message-ID: <1766954.4AFWyoEiEr@x2> References: <052F8E4E-A8B6-451A-8493-51B8B70D200E@bambenekconsulting.com> <2636990.QdK4Ys10gI@x2> <73A8977A-6242-4F20-8A72-6D60F449ED50@bambenekconsulting.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <73A8977A-6242-4F20-8A72-6D60F449ED50@bambenekconsulting.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-audit-bounces@redhat.com Errors-To: linux-audit-bounces@redhat.com To: John Bambenek Cc: "linux-audit@redhat.com" List-Id: linux-audit@redhat.com On Friday, April 26, 2013 12:03:17 PM John Bambenek wrote: > I would prefer a solution besides a keylogger that, among other things, > happily captures passwords and stores them in the clear in logs. That is being worked on: https://www.redhat.com/archives/linux-audit/2013-March/msg00050.html The patch still isn't ready, but it will be configured by pam_tty_audit. -Steve > On Apr 26, 2013, at 11:56 AM, Steve Grubb wrote: > > On Friday, April 26, 2013 10:07:56 AM John Bambenek wrote: > >> I was playing around and wanted to know if there is plans to allow audit > >> rule filters by TTY, or specifically filter when tty != (none) (i.e. > >> interactive login events). > > > > You can use the pam_tty_audit module to do that. There are no plans to > > configure this by auditctl. > > > > -Steve