PATCH: login reporting (utmp?) problem on Linux

[Rip Loomis]

For validation:

I just built 2.1.1p1 in two separate source
trees on a SPARC 20 (Solaris 7, gcc 2.95.2).
One was the "vanilla" 2.1.1p1, and the other
had Garrick's one-line patch to aclocal.m4
applied (after which I had to autoreconf as
stated in his original message).

After stripping both sets of binaries, they're
100% identical--so at least on Solaris, Garrick's
patch doesn't break anything.  I would recommend
including it into the mainline portable code.

	--Rip

Rip Loomis		
--------------------------------------------------------
Security Engineer
Center for Information Security Technology
Science Applications International Corporation
http://www.cist.saic.com



-----Original Message-----
From: owner-openssh-unix-dev at mindrot.org
[mailto:owner-openssh-unix-dev at mindrot.org]On Behalf Of Garrick James
Sent: Wednesday, June 21, 2000 9:02 AM
To: Phil Karn
Cc: openssh-unix-dev at mindrot.org
Subject: Re: PATCH: login reporting (utmp?) problem on Linux


I have two Debian based machines.  One is stock 2.1r5.  The other is
somewhere between 2.1 and 2.2.  ;-)  Both machines had the utmp problem.

So far, I have seen this problem on or received reports for the problem on
Debian (2.1 and 2.2), Slackware (version?), RedHat (version?), Suse (6.4),
and Mandrake (7.0 and 7.1), though.  The patch I posted fixed the problem
in each case.

Damien, is there anyway I can get my patch tested on other non-Linux
systems and rolled into the official distribution?

-Garrick

On Tue, 20 Jun 2000, Phil Karn wrote:

> FYI, I also encountered this problem, but only after I updated my
> Linux machines from Debian 2.1 (slink) to the Debian "frozen"
> (2.2-potato) release. All my utmp entries are now Wed Dec 31.
> 
> Phil
>