similar to: FYI: lastlog on AIX

Displaying 20 results from an estimated 100000 matches similar to: "FYI: lastlog on AIX"

2001 Sep 27
1
AIX lastlog change?
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
2001 Nov 09
0
AIX lastlog change
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
2010 Jun 03
10
[Bug 1774] New: wtmp and lastlog on AIX
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
2000 Jun 12
1
AIX and 2.1.1p1
The new login code works fine with AIX 4.3. Two nits, though. If --disable-lastlog is defined, the code still tries to slog through wtmp to determine the last login time. Is this a bug or a feature? If a feature, change the DISABLE_LASTLOG test below to WITH_AIXAUTHENTICATE. Also, a small typo in configure.in, plus an AIX tweak. --- configure.in.orig Thu Jun 8 21:58:35 2000 +++ configure.in Mon
2000 May 15
1
AIX authenticate patches
Here are some patches to re-enable support for AIX's authenticate routines. With them, ssh will honor locked & unlocked accounts, record successful and unsuccessful logins, and deny accounts that are prohibited to log in via the network. Tested with AIX 4.3. It also includes a fix for handling SIGCHLD that may be needed for other platforms (HP-UX 10.20, for example). If I get the time
2003 Sep 29
2
OpenSSH 3.7.1p2 AIX loginsuccess() issue
On AIX 4.3.3 and AIX 5.1, the last successful and unsuccessful logins are no longer printer prior to the motd with either the stock openssh-3.7.1p2 or Darren's openssh-3.7.1p2-pwexp24.patch. In both cases it appears that the loginsuccess() call (auth-passwd.c stock or auth.c Darren's patch) is returning -1 and msg is not appended to loginmsg. /etc/security/lastlog is updated despite
2006 Mar 03
0
[PATCH] contrib/cygwin/ssh-host-config: Handle lastlog with more care
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
2000 Apr 21
0
OpenSSH 1.2.3 on AIX 4.3.3
Hmph. I wish I had checked the list before I wasted a half-day on this. Yes, the problem exists under AIX (mine's 4.3.1). Here's the patch I came up with, which may be a little more straightforward than the original. I confirmed that it works under Solaris 2.[67] too. Don't forget to run autoconf. --- bsd-login.c.orig Sat Dec 25 18:21:48 1999 +++ bsd-login.c Thu Apr 20 18:26:41
1999 Dec 10
5
openssh on AIX v4.3.3 with native compiler
Hello, Was looking in the archives... and haven't seen this one listed. When I compile openssh-1.2pre17 on AIX v4.3.3 with the native compiler I get the following errors. I haven't see this __attribute__ code.. What compiler/libraries are needed to compile this? I have seen that people have compiled openssh on AIX.. Just wondering what you have used. # make cc -g
2001 Sep 12
3
lastlog with hp-ux 10.20
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
2003 Jul 03
0
AIX cleanups: includes and arguments
Hi All. First the questions: Is there anything objectionable in this patch? Is AUDIT_FAIL_AUTH appropriate for the "Reason" field? Now the details: attached is a patch that changes some of the #includes for AIX. It moves the AIX-specific includes to port-aix.h and adds includes that contain the prototypes for many of the authentication functions. The idea isto fix some warnings.
2001 Jan 30
1
HP-UX lastlog / contrib
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
2001 Sep 06
1
lastlog on Solaris with PAM (patch included)
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,
2000 Dec 28
1
Bug in lastlog printing
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.
2003 Sep 22
0
Unnecessary configure option '--(enable|disable)-lastlog'
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>
2004 Apr 06
1
No motd, lastlog, stored pam messages displayed
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
2003 Aug 15
0
Question about struct lastlog
Hello everyone, I have run into a problem with struct lastlog and finding information about it, I don't know anything about this struct, the contents of this struct, which header it comes from. Can anyone direct me in to the right place to find more information about this struct. Thank you, Joey _________________________________________________________________ Tired of spam? Get advanced
2010 Sep 13
5
[Bug 1817] New: lastlog is not recorded with the big uid
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:
2000 Jan 19
3
AIX openssh patches
I have a few patches for AIX. The patchfile is attached below. The patch has been tested on AIX4.2 and AIX4.3. The patch is on openssh-1.2.1pre25, with openssl-0.94, using RSAref. 1) authenticate support - this function allows the system to determine authentification. Whatever the system allows for login, authenticate will too. It doesn't matter whether it is AFS, DFS, SecureID, local.
1999 Dec 28
1
ANNOUNCE: openssh-1.2.1pre22
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have just uploaded 1.2.1pre22 to: http://violet.ibs.com.au/openssh/files/ This release consists of portability fixes and cleanups. It also resolves two issues which may have caused security problems - If you OS header files did not define PATH_STDPATH, then an unsafe path was used by default (it contained an implicit '.'). Thanks