Displaying 20 results from an estimated 300 matches similar to: "2.3.0p1, Solaris 7 and last login (fwd)"
2002 Jan 30
0
[Bug 87] New: Last logon that gets reported upon login is the current login time
http://bugzilla.mindrot.org/show_bug.cgi?id=87
Summary: Last logon that gets reported upon login is the current
login time
Product: Portable OpenSSH
Version: 3.0.2p1
Platform: UltraSparc
OS/Version: Solaris
Status: NEW
Severity: normal
Priority: P2
Component: sshd
AssignedTo:
2000 Dec 27
1
PrintLastLog option is not honored
Hi,
here's another bug report against openssh with a patch included (from
the same person who submitted the bug report). Would you please apply
it? Thanks!
> The Debian package of ssh includes patches to recognize a 'PrintLastLog'
> option which can be used to disable the automatic display of the last
> login time. (This is often handled by PAM.) The option is scanned and
2002 Apr 10
1
openssh-3.1p1 on GNU/Hurd
Hi,
I've gone and ported the latest version of openssh, 3.1p1, to GNU/Hurd.
I've tried to learn from the other threads on this topic, but I still had
to get rid of MAXHOSTNAMELEN where I could.
James A. Morrison
diff -urN openssh-3.1p1.old/Makefile.in openssh-3.1p1/Makefile.in
--- openssh-3.1p1.old/Makefile.in Tue Feb 26 14:24:22 2002
+++ openssh-3.1p1/Makefile.in Tue Apr 9 16:16:49
2001 Mar 03
0
[PATCH] PrintLastLog option
Some time ago, Ben wrote about a PrintLastLog patch:
> If the person who originally submitted it wants to write a complete
> patch and submit it. Then we would be happy to debate if it will be
> included.
Well, here it is, because: "You Asked For It!"
PS: I'm tired of maintaining my own version of Debian's ssh just to
have this option available, so I hope you find
2001 Mar 22
0
Solaris UseLogin problem
I was having problems getting the UseLogin option to work
on Solaris.
I would recieve this error:
No utmpx entry. You must exec "login" from the lowest level "shell".
This led me to believe that Solaris login wants a utmpx entry in
order to function. I put together a patch that calls record_login
on Solaris when using the system login. I also noticed that writing
a wtmpx
2001 Apr 04
1
Solaris UseLogin problems
I'm using openssh 2.5.2p2 on Solaris-x86 2.6. I ran into a couple
problems when I set UseLogin to "yes":
The big one seems to have been reported before: login refuses to run
without a utmpx entry. This problem appears to have been caused by
the changes in revision 1.24 of session.c. Before this revision, the
record_login() function was always called, no matter how UseLogin was
2002 Apr 22
0
[Bug 101] session.c modifications for correct UNICOS behavior
http://bugzilla.mindrot.org/show_bug.cgi?id=101
------- Additional Comments From wendyp at cray.com 2002-04-23 08:43 -------
updated patches for 22 april snapshot:
--- session.c.orig Mon Apr 22 14:36:13 2002
+++ session.c Mon Apr 22 16:31:15 2002
@@ -64,6 +64,10 @@
#define is_winnt (GetVersion() < 0x80000000)
#endif
+#ifdef _CRAY
+#include <tmpdir.h>
+#endif /*
2002 Feb 04
0
[Bug 101] New: session.c modifications for correct UNICOS behavior
http://bugzilla.mindrot.org/show_bug.cgi?id=101
Summary: session.c modifications for correct UNICOS behavior
Product: Portable OpenSSH
Version: 3.0.2p1
Platform: Other
OS/Version: other
Status: NEW
Severity: normal
Priority: P2
Component: sshd
AssignedTo: openssh-unix-dev at mindrot.org
2001 Sep 04
0
AIX Warning for expired password
Hi,
I have made a patch for AIX to report the number of days till a password
expire and to prompt for a new one.
This patch was made for openssh-SNAP-20010904.tar.gz (2.9p2) of the CVS
repository.
If you have any suggestion or question to submit, please cc to me,
I'm not in the list.
Bye
--
Pablo Sor
Departamento de Seguridad Informatica - AFIP
psor at afip.gov.ar, psor at ccc.uba.ar
2001 Oct 12
2
bug report: last login time vs PAM in portability release
on hp-ux 11 i see:
$ date;ssh jenny
Fri Oct 12 14:44:13 PDT 2001
Last successful login for stevesk: Fri Oct 12 10:45:42 PST8PDT 2001 on pts/2
Last unsuccessful login for stevesk: Mon Sep 24 22:55:53 PST8PDT 2001
Last login: Fri Oct 12 10:45:43 2001 from 172.31.1.53
You have mail.
so solaris PAM is different. can other solaris+PAM users confirm this?
On Fri, 12 Oct 2001, Benn Oshrin wrote:
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
2002 May 09
0
functions : server_input_channel_req userauth_pubkey
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Greetings,
I am not sure if this is the correct place to ask these question,
if I am at the wrong place please advise.
I am currently working on some modifications to openssh
which record the users rsa/dsa identity comment file to
a log file when the user logs in (password authentication
is disabled).
The ssh1 portion of the modification works
2013 Jul 29
4
[Bug 2134] New: invalid prototype for get_last_login_time()
https://bugzilla.mindrot.org/show_bug.cgi?id=2134
Bug ID: 2134
Summary: invalid prototype for get_last_login_time()
Product: Portable OpenSSH
Version: 6.2p1
Hardware: Other
OS: FreeBSD
Status: NEW
Severity: enhancement
Priority: P5
Component: Build system
Assignee:
2001 Apr 13
0
Fixed patch for Digital Unix SIA
Okay, here is a fixed version of the patch I sent before for fixing the
problems I know about with Digital Unix SIA: displaying too much info
(MOTD, last login, etc.) when access is denied, and the loss of the
error message sometimes when access is denied.
It does break some code out of do_login into a couple of separate
functions. I did this to avoid duplicating the code in a couple of
places.
2001 Jan 03
0
AIX loginsuccess and aixloginmsg ?
Hi,
I noticed that the AIX specific loginsuccess call uses
char *aixloginmsg to retrieve login information. Later this message is
printed in session.c (around line 753). Loginsuccess mallocs space for
this message and according to the aix docs it's the responsibility of the
calling program to free this message.
I didn't notice any code in openssh that would free the aixloginmsg.
Can
2003 Jan 07
0
[Bug 463] New: PrintLastLog doesn't work in privsep mode
http://bugzilla.mindrot.org/show_bug.cgi?id=463
Summary: PrintLastLog doesn't work in privsep mode
Product: Portable OpenSSH
Version: -current
Platform: All
OS/Version: All
Status: NEW
Severity: trivial
Priority: P2
Component: sshd
AssignedTo: openssh-unix-dev at mindrot.org
ReportedBy:
2000 Apr 24
2
OpenSSH 1.2.3, HPUX 10.20 [TCB]
Hello,
already checked the Mailinglist archive for HPUX Problems, but
havent found exact this:
./configure --prefix=/opt --without-pam --with-ssl-dir=/opt/OpenSSL
--with-lastlog=/var/adm/wtmp --with-egd-pool=/dev/entropy
--with-tcp-wrappers --with-pid-dir=/var/run --sysconfdir=/etc/ssh
and get after a make:
gcc -O2 -Wall -D_HPUX_SOURCE -I/usr/local/include -I/opt/include
2000 Jan 31
0
New liblogin 0.3alpha
FYI a new version of liblogin, 0.3alpha, is up on my website at
http://dspace.dial.pipex.com/andre.lucas/liblogin.html
This version fixes a few bugs and has implementations for the full API,
including 'get last login time' support, even for systems without
lastlog.
New OpenSSH patches against 1.2.2 are also available, to enable the last
login time features. Again, the function (in
2001 Nov 20
0
PATCH: Fixing last/utmpx for Solaris
In case it is any help, here is the patch against openssh-3.0.1p1 that
corrects the problem with last reporting on Solaris that I sent to the
list a week or so ago against 3.0p1. There was no conversation about this
aside from Rip Loomis' comment about including it to support BSM auditing
- does this present a problem for other OSes to include the ut_name field
in the utmpx entry? Should this
2002 Sep 23
19
Call for testing for 3.5 OpenSSH
OpenBSD tree is heading into a lock and this includes OpenSSH. So we are
winding up for a 3.5 release. If we can get people to test the current
snapshots and report any problems that would improve the odds that your
platform won't be broke for 3.5.
Issues I know off of right now.
1. I can't test NeXT. So I TRULY need someone in that community to test
for me. Last I heard there was