Re: login, telnetd not updating utmp etc on -CURRENT

On Thu, Jan 26, 2006 at 03:45:24PM +0000, Chris Hedley wrote:
> >Your PAM config OK? On my (5.4) system here, I have in /etc/pam.d/login
> >
> >...
> ># session
> >session include system
> >...
> >
> >and in /etc/pam.d/system there is
> >
> ># session
> >#session optional pam_ssh.so
> >session required pam_lastlog.so no_fail
> >
> >In /etc/pam.d/telnetd there is
> >
> ># session
> >#session optional pam_ssh.so
> >session required pam_lastlog.so no_fail
> >
> >So it looks like that's how those updates are done.
>
> Oddly enough sshd is the only one mentioned that _doesn't_ have the
> pam_lastlog plugin listed! <Scratched head> I'll have to do a bit more
> rummaging around to see if there's anything that seems reasonably
> obvious...

I think sshd has the ability to write directly to utmp/wtmp, but it depends
on how it was compiled. On my machine sshd 'session' is just pam_permit.so,
so I guess sshd must be writing those records directly.

Regards,

Brian.
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • [Fwd: Re: FreeBSD Security Advisory FreeBSD-SA-03:12.openssh]
    ... >99% of even the most heavily loaded servers have more than enough ... by generating a different key for each session you get better ... >run sshd out of inetd. ...
    (FreeBSD-Security)
  • Re: Accounting changes
    ... What we should do is add a systemcall or sysctl, so session creators ... sshd would log IP+port and possibly also credential used for auth. ... Isn't this purpose mostly served by joining the accounting record with wtmp on the ll_line field to obtain the IP address from the ll_host field? ...
    (freebsd-arch)
  • Re: login, telnetd not updating utmp etc on -CURRENT
    ... This is happening on both my systems so I'm guessing it's not something weird that I'm doing I've only noticed this recently as prior to a few days back I'd only been using sshd on my FreeBSD systems, but the older one's telnetd is of 13-Oct-2005 vintage, if that's of any use. ...
    (freebsd-current)
  • Re: login, telnetd not updating utmp etc on -CURRENT
    ... > aren't being updated by login and telnetd; however, sshd still seems to be ... > older one's telnetd is of 13-Oct-2005 vintage, ...
    (freebsd-current)
  • Re: Windows / Microsoft Update
    ... > When searching for available updates on the Update site, ... > Alan wrote: ... >> session from datastore, error = 0x80004002 ...
    (microsoft.public.windowsupdate)