similar to: Size of /var/log/lastlog

Hi list, this problem is already known and I'm sorry to bother if an acceptable workaround was already debated on the list. I was getting trouble with a 'grep something /var/log*' which caused the "Memory exhausted" message. With some deeper search I found the lastlog file in /var/log/ to be 1.2T sized. This seems to come from the nfsnobody's uid to be 4294967294 on

Hi, just built 2.3.0p1 on HP-UX 10.20 more or less smoothly >From 1.2.3 I had documented --without-lastlog, can't remember why, broke something. So I tried my old configure settings for 2.3.0 which seams to break stuff: loginrec.c:1338: warning: `struct lastlog' declared inside parameter list some more dereferencing pointers and then Error 1 [of course] Omitting the

Hi, I just ltraced ssh to see why it prints the lastlog twice instead of one time. I think the bug seems to be in the parsing of the lastlog-entry and I especially think that the function lastlog_populate_entry is the buggy one, but I'm not sure, as I'm not very familar with the code. So if someone of you, would please trace this bug down and fix it, I would really appreciate that.

Somewhere between 2.9p1 and 2.9.9p2 there was a change to auth2.c that removed the userauth_reply() function. There were a few lines of code in that function, #ifdef'd with WITH_AIXAUTHENTICATE, that handled the AIX method of lastlog type stuff (specifically, a loginsuccess() call). There is a similar call in auth1.c, down in do_authentication(), which is still there in 2.9.9p2. So with

i haven't heard of problems with configure/lastlog on 10.20. i'll copy the development list as there are folks there who use 10.20. On Thu, 6 Sep 2001, Jesse Caldwell wrote: :one last problem with openssh -- building openssh on HPUX 10.20 fails :on loginrec.c (i don't have the errors handy but i would be more than :happy to recreate them). i get the same error with 2.9p2 and 9/6/2001

https://bugzilla.mindrot.org/show_bug.cgi?id=2278 Bug ID: 2278 Summary: 'configure --disable-lastlog' should mark PrintLastLog as unsupported in servconf.c Product: Portable OpenSSH Version: 6.6p1 Hardware: All OS: Solaris Status: NEW Severity: minor Priority: P5

Folks; I couldn't find anything on my archive of the mailing list on this, and it may just be my mis-understanding, but: When I "ssh machine1 -l user1" as user2 on machine2, if user2 has the same uid on machine1, then user2's name ends up in lastlog, instead of user1's. This is a bit disconcerting when user2 is root, and root isn't allowed to remotely log in on

This is very odd. I updated a user's workstation yesterday. This morning, I ran lastlog | grep -v Never, and it shows only another admin and myself, and that's from days ago, but not the user. It shows her as "Never logged in". Meanwhile, last does indeed show her logged in (though not today). Anyone have any ideas? mark

https://bugzilla.mindrot.org/show_bug.cgi?id=1774 Summary: wtmp and lastlog on AIX Product: Portable OpenSSH Version: 5.5p1 Platform: All OS/Version: AIX Status: NEW Severity: normal Priority: P2 Component: Build system AssignedTo: unassigned-bugs at mindrot.org ReportedBy: defrayable at

Hi while testing a new pam module i found this problem: System: Linux 2.4.18/OpenSSH 3.8p1 client/server The output from do_login() in session.c (motd, lastlog, stored pam messages) isn't displayed when Privilege Separation is enabled. I added a fflush(stdout) as the last line of do_login(), now it works. Frank

Hi, below is a patch to Cygwin's ssh-host-config file. So far this script allowed to have a lastlog file as well as a lastlog dir, whatever the user preferred. This is no problem as long as ssh is the only application using lastlog, but that's nothing we can be sure about, so we decided to restrict lastlog to being a file in a Cygwin installation. This also allows reliable porting and

On Solaris, the pam_unix module includes a pam_session which updates the lastlog file. Since OpenSSH calls pam_session before reading the lastlog file, SSH logins to systems with this configuration (as well as similar ones, I'd imagine) report the last login time and remote host as the values from the current session. My solution to this problem is to call pam_open_session in the child,

https://bugzilla.mindrot.org/show_bug.cgi?id=1817 Summary: lastlog is not recorded with the big uid Product: Portable OpenSSH Version: 5.6p1 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: unassigned-bugs at mindrot.org ReportedBy:

--- appliance/excludefiles.in | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/appliance/excludefiles.in b/appliance/excludefiles.in index 9a48db7..c53a913 100644 --- a/appliance/excludefiles.in +++ b/appliance/excludefiles.in @@ -32,12 +32,7 @@ dnl The right kernel modules are added back by supermin. -/usr/share/i18n/* -/usr/share/pkgconfig/* --/var/log/*.log*

As a general FYI for AIX. On a vanilla AIX install, you'll need to run ./configure as root in order to find the lastlog. The lastlog file is found within /etc/security, with permissions to allow root and the security group.

Hi, develop members: When I checked the output of './configure --help', I noticed that the '--(enable|disable)-lastlog' option was unnecessary any longer. This option can be replaced by the '--with(out)-lastlog'. Thanks. --- Norihiko Murase <skeleten at shillest.net>

https://bugzilla.mindrot.org/show_bug.cgi?id=2644 Bug ID: 2644 Summary: [PATCH] set uid for functions that use it to seek in lastlog and wtmp files Product: Portable OpenSSH Version: 7.2p2 Hardware: amd64 OS: Linux Status: NEW Severity: enhancement Priority: P5

This is.... odd. We're seeing a *lot* of sshd[8400]: Timeout, client not responding. So I'm trying to find out whose client is having issues. Trying to figure that, after processes are gone, I tried looking in lastlog, which is where it gets odd. lastlog shows root coming in, and it shows a security account coming in... years ago. I see one of our users logging in a goodly number of

Precedence: bulk Hi, I'm getting the error: sshd[71835]: lastlog_get_entry: Error reading from /var/adm/lastlog: Error 0 from openssh 2.1.1p4 on IRIX (6.5.8m). Looks like there's some confusion about /var/adm/lastlog being a directory and not a file on IRIX. ./configure says: checking for lastlog... no checking if your system defines LASTLOG_FILE... no but I still gets the error

Hi David, I'm sure loginfailed(..) should be called immediately after authenticate(..) returned an error. It is directly related to an invalid password try. (Please see my attached mail from May 2001 to the list). I'm not so sure when loginsuccess(..) should be called (setting the loginfailed counter to zero): Either 1) when somebody logs in successfully using all kinds of valid