Displaying 4 results from an estimated 4 matches for "wtmp_write_entri".
Did you mean:
wtmp_write_entry
2001 Jun 21
0
Output of last command is strange on Solaris 2.6/8 (OpenSSH 2.9p2)
Hi.
OS: Solaris 2.6 and 8
OpenSSH: 2.9p2
I found a bug.
Output of last command becomes strange in case of "UseLogin yes"
in sshd_config.
# Two entries are output with one time of login.
strange case:
% last
fuga pts/3 bar.foo.co.jp Thu Jun 21 12:45 - 20:02 (07:16)
fuga pts/3 bar.foo.co.jp Thu Jan 1 09:00 - 12:45 (11494+03:45)
hoge pts/2
2004 Jul 08
1
openssh 3.8.1p1 problem on SCO 5.0.7
On SCO 5.0.7 and openssh 3.8.1p1, two entries are written to /etc/wtmp
and /etc/wtmpx each time a user logs in via ssh. This can be
demonstrated using the last(C) command. Any user connected via ssh will
have two identical login and logout entries.
On SCO, login_write() in loginrec.c calls both wtmp_write_entry() and
wtmpx_write_entry() (USE_WTMP and USE_WTMPX are defined).
wtmp_write_entry()
2000 Nov 27
0
/var/log/btmp logging ?
Hi,
Openssh doesn't log failed logins to /var/log/btmp like login does
(if btmp exists). This is on RH6.2.
Is there a specific reason for not logging to btmp ?
I think that logging to btmp would be a 'good thing'(tm). What about
other unices ? Do they have /var/log/btmp or something similar (AIX has
something like that and I think openssh already logs the failed attempts).
AFAIK
2001 Apr 29
2
PATCH: UseLogin fix for 2.9p1 (w/improved last-login time)
Attached is the latest version of my UseLogin patch that makes
"UseLogin true" work on Solaris and UNICOS. As usual, I have provided
configure.in changes that set the appropriate defines for Solaris, but
I have not provided the configure.in changes for UNICOS (since they
would be incomplete, and Wendy is working on this).
This version fixes a problem with the last-login time always