Bug 757 - AutoPPP dialed-in user shows up as a_ppp
AutoPPP dialed-in user shows up as a_ppp
Status: CLOSED CURRENTRELEASE
Product: Red Hat Linux
Classification: Retired
Component: mgetty (Show other bugs)
5.2
All Linux
medium Severity medium
: ---
: ---
Assigned To: Cristian Gafton
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-01-09 09:29 EST by Daniel Senie
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-04-09 23:34:25 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:


Attachments (Terms of Use)

  None (edit)
Description Daniel Senie 1999-01-09 09:29:59 EST
With RHL 4.2, a user dialed in with AutoPPP and PAP
authentication showed in a "who" display as the user who
successfully logged in.

With RHL 5.2, the who display shows "a_ppp" instead.

This was noticed in converting a box which supports dialup
using Cyclades cards. I upgraded from 4.2 to 5.2 and a
number of problems cropped up, this was one.
Comment 1 ink 1999-04-06 10:24:59 EDT
Actually it's PAM bug. It's very unpleasant because it makes
users accounting impossible on dial-in server.

pppd-2.3.5 relies on the PAM modules for wtmp handling;
on other hand, look at quote from pam_lastlog docs:

  Overview of
module

   This session module maintains the /var/log/wtmp file. Adding an
open
   entry when called via the pam_open_seesion() function and
completing
   it when pam_close_session() is called.
   ...

But this functionality is missing.
So I think the right solution is adding utmp/wtmp stuff to the lastlog
module according its docs, and adding following line to /etc/pam.d/ppp
in the
case of dial-in server:

session    required     pam_lastlog.so

Patch for pam_lastlog follows (I used it successfully last 3 months).
Comment 2 Cristian Gafton 1999-04-09 23:34:59 EDT
fixed in ppp-2.3.7-1 and later source rpms.

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