Bug 187751 - Getting rid of su(pam_unix) console messages
Summary: Getting rid of su(pam_unix) console messages
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: pam
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Tomas Mraz
QA Contact: Jay Turner
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-04-03 14:14 UTC by Dag Wieers
Modified: 2015-01-08 00:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-04-03 15:00:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dag Wieers 2006-04-03 14:14:36 UTC
Description of problem:
Our console has lots of messages like:

  su(pam_unix)[5854]: session closed for user dag                              
                                                                            
  su(pam_unix)[5974]: session opened for user dag by (uid=0)

And for security reasons we don't want to have these on the screen. We don't
want to disclose what users exist on a system.

Since we disabled syslogd/klogd and we still get these messages, they have to
come from pam_unix directly ?

Is there a way to disable this, I haven't been able to find how though.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Tomas Mraz 2006-04-03 15:00:36 UTC
Since you have stopped the syslogd daemon and pam_unix uses LOG_CONS flag when
logging, the messages which would go to the system log are written on console
instead. This is normal behaviour. You can either remove 'session ....
pam_unix.so' from the /etc/pam.d/system_auth configuration or just run the
syslogd to prevent this behaviour.

Note that the session part of the pam_unix module doesn't have any other purpose
than logging these messages so removing it is harmless if you don't want to get
them.



Note You need to log in before you can comment on or make changes to this bug.