Displaying 20 results from an estimated 6000 matches similar to: "[Bug 464] New: sshd seems to corrupt the wtmpx"
2003 Jan 08
6
[Bug 464] sshd seems to corrupt the wtmpx
http://bugzilla.mindrot.org/show_bug.cgi?id=464
------- Additional Comments From pas50 at cam.ac.uk 2003-01-09 02:11 -------
This is apparently a bug with compiling in 64 bit.
David foster saw this.
http://www.sunmanagers.org/pipermail/summaries/2002-October/004018.html
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
2004 Feb 10
3
[Bug 464] sshd seems to corrupt the wtmpx
http://bugzilla.mindrot.org/show_bug.cgi?id=464
djm at mindrot.org changed:
What |Removed |Added
----------------------------------------------------------------------------
OtherBugsDependingO| |793
nThis| |
------- You are receiving this mail because: -------
You are the assignee for the
2003 Apr 02
0
[Bug 464] sshd seems to corrupt the wtmpx
http://bugzilla.mindrot.org/show_bug.cgi?id=464
pere at hungry.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pere at hungry.com
------- Additional Comments From pere at hungry.com 2003-04-03 03:03 -------
I see the same problem on IA64 HP/UX
2001 Jun 29
1
wtmpx problem on Solaris 8 sparcv9 (64bit) environment
Hello
When I was using OpenSSH-2.9p2 in Solaris 8 sparcv9 (64bit)
environment, I found some trouble that wtmpx has broken.
The size of utmpx structure object becomes larger than 32 bit environment
in sparcv9 environment.Therefore, instead of using utmpx structure object,
using futmpx structure object is better.
In sparcv9 environment, futmpx structure object is used instead of utmpx
structure
2000 Sep 13
0
Solaris wtmp/wtmpx handling
It appears to be a pervasive assumption in the Portable OpenSSH code
that wtmp and wtmpx records for the end of a session do not need to
include the user name or hostname. Unfortunately Solaris appears not to
go along with that assumption; the Solaris "last" command shows all
login sessions initiated by OpenSSH as never terminating, or sometimes
terminating with the user's next
2002 Feb 24
1
[Bug 122] sshd does not update wtmpx at end of session
http://bugzilla.mindrot.org/show_bug.cgi?id=122
------- Additional Comments From tim at multitalents.net 2002-02-25 05:32 -------
I spent some time looking into this. Initially I did see that last was reporting
users still logged in that had logged out of their ssh connection. I noticed
logintest showed everything working as expected. Now I can not duplicate the
problem. I didn't change
2006 Feb 04
2
OpenSSH 4.3P1: incorrect wtmpx entries
Hi,
I just installed OpenSSH 4.3p1 on our Solaris 8 machines and 'last' now
shows wtmpx entries for ssh logins like
zierke pts/4 Thu Jan 1 01:00 still logged in
zierke pts/3 Thu Jan 1 01:00 - 10:56 (13183+09:
instead of e.g.
zierke pts/3 rzdspc10.informa Sat Feb 4 10:54 - 10:54 (00:00)
zierke pts/2
2001 Jan 29
1
Solaris wtmpx patch
Hi,
Solaris (tested with 2.6) needs a username in the logout record in the wtmpx
file. Currently openssh (version 2.3.0p1) leaves the username (utmpx.ut_user)
empty in logout records, which leads to conflicting results from the last
command. Example:
# last -5 siegert
siegert pts/186 stikine.ucs.sfu. Mon Jan 15 14:26 still logged in
siegert pts/105 stikine.ucs.sfu. Mon Jan 15
2002 Jul 09
0
[Bug 348] New: infinite loop scanning wtmpx
http://bugzilla.mindrot.org/show_bug.cgi?id=348
Summary: infinite loop scanning wtmpx
Product: Portable OpenSSH
Version: -current
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: P2
Component: sshd
AssignedTo: openssh-unix-dev at mindrot.org
ReportedBy: rodney at
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()
2005 Jul 20
1
AIX 5.1 /etc/security/failedlogin entry with OpenSSH 4.1p1
Hello
Ive downloaded OpenSSH 4.1p1 from the portable openssh web pages...
Compiled it up for an AIX 5.1 host (with latest IBM maintenance patches
applied)
using defaults in all cases.
When doing a successful SSH authentication it places an entry into
/etc/security/failedlogin
as well as /var/adm/wtmp
Ive also tried adding "UseLogin yes" to the sshd_config
PAM ISNT configured (infact
2015 Jan 20
0
[ANNOUNCE] sessreg 1.1.0
sessreg is used by display managers such as xdm and gdm to record X sessions
in utmp, wtmp, and lastlog files.
This release attempts to clean up some inconsistencies around the handling
of the various files.
Long long ago, Unix systems had a utmp file to record who was currently
logged in, and a wtmp file to record login history.
Long ago, extended versions of the files & APIs for them were
2002 Oct 24
1
[SUMMARY] Problems with 'last' (when OpenSSH compiled 64-bit)
Problem:
'last' output is incorrect, /var/adm/wtmpx is corrupted. Example:
foster pts/1 Wed Dec 31 16:00 still logged in
foster pts/3 dim Thu Aug 1 14:34 still logged in
Solution: (workaround)
This turned out to be an OpenSSH problem! If OpenSSH (only tested
versions 3.4p1 and 3.5p1) is compiled 64-bit it corrupts the
/var/adm/wtmpx
2005 Apr 28
1
Openssh Solaris problem writing /var/adm/wtmp
Hi :-)
i have rollout a new ssh pakage in our environment.
Apr 27 12:06:03 systemx sshd[869]: [ID 847 auth.info] wtmp_write: problem
writing /var/adm/wtmp: No such file or directory
Solaris 8 has no /var/adm/wtmp, it use /var/adm/wtmpx
In the old package there was many of this messages
I compiled the new package with
--disable-wtmp \
--enable-wtmpx \
but sometimes one of this message are in
2007 Jan 17
0
login_get_lastlog - nss enviornment - works in shell env, doesn't work when sshd calls it.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello to every one!
Maybe this is not exactly the right place,
but I don't know where to ask, so...
I have a FreeBSD-6-STABLE machine,
setuped with custom nss lib which reads from pgsql database.
It seems to be working just fine except
that I can't login trought ssh, when trying the normal method.
When I do
$>ssh host.com tcsh
I get
2000 May 30
0
utmpx bug in openssh-2.1.0p2 using Solaris 8
Hi,
I've installed openssh-2.1.0p2 on a Solaris 8 host (SPARC). The sshd
corrupts utmpx/wtmpx when a client connects to this machine. Observable
error:
$ who
who: Error --- entry has ut_type of 28265
when maximum is 9
It can be repeated and is attributable to the login done by sshd. Now,
Solaris has only utmpx/wtmpx and not the old utmp/wtmp. It get's worse
as more logins take place
2006 Feb 03
4
[Bug 1150] sshd records incorrect login times
http://bugzilla.mindrot.org/show_bug.cgi?id=1150
Summary: sshd records incorrect login times
Product: Portable OpenSSH
Version: 4.3p1
Platform: Other
URL: http://marc.theaimsgroup.com/?l=openssh-unix-
dev&m=113890107022083&w=2
OS/Version: Solaris
Status: NEW
Severity: major
1998 May 11
1
(wtmp) Suggestion to samba
Joao Carlos Mendes Luis <jonny@coe.ufrj.br> wrote:
> I think it would be useful if samba had a utmp log interface.
> I know that it's possible to see who is logged with smbstatus, but
> sometimes a simple who(1) or w(1) is more efficient and ubiquitous.
If you were to search for 'wtmp' in the 1997 archives
(via the Samba web pages), you would find one interesting
2001 Mar 06
3
utmpx/wtmpx problems with 2.5.1p2 on irix...
I installed 2.5.1p2 on an irix system and noticed that if a user logged
in typed "logname" it was providing the wrong username. File creations
were correct, "w" produces the correct output....so something is funky
in p2 that wasn't there in p1.
2002 Jul 14
0
[Bug 348] infinite loop scanning wtmpx
http://bugzilla.mindrot.org/show_bug.cgi?id=348
tim at multitalents.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Additional Comments From tim at multitalents.net 2002-07-15