Bug 187491 - openssh do no write to utmp when audit is not supported by kernel
openssh do no write to utmp when audit is not supported by kernel
Status: CLOSED DUPLICATE of bug 182930
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: openssh (Show other bugs)
4.0
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tomas Mraz
Brian Brock
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-03-31 06:08 EST by Sergey Myasnikov
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-03-31 06:21:40 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Sergey Myasnikov 2006-03-31 06:08:15 EST
Description of problem:
On rhel4-u3 openssh does not write to utmp session data if a kernel does not 
support audit.


Version-Release number of selected component (if applicable):
openssh-3.9p1 (that which comes with RHEL AS4 u3)


How reproducible:


Steps to Reproduce:
1. Boot into a kernel with no audit (audit=0 in kernel cmd line is supposed to 
be enough)
2. Connect to the host via ssh
3. Run who
  
Actual results:
No data is written to utmp.log.  'who' shows no logins via ssh

Expected results:
'who' must show the session.

Additional info:
This happens due to the bug in openssh-3.9p1-audit.patch.  The 3rd hunk 
contains a bug:
@@ -415,6 +422,10 @@
  
        /* set the timestamp */
        login_set_current_time(li);
+#ifdef HAVE_LINUX_AUDIT
+       if (linux_audit_write_entry(li) == 0)
+               return 0;
+#endif
 #ifdef USE_LOGIN
        syslogin_write_entry(li);
 #endif

This should be rewritten without 'if' and 'return 0'
Comment 1 Tomas Mraz 2006-03-31 06:21:40 EST

*** This bug has been marked as a duplicate of 182930 ***

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