similar to: [Bug 2407] New: OpenSSH uses deprecated APIs on MacOS

Hi, OpenSSH 6.7 is almost ready for release, so we would appreciate testing on as many platforms and systems as possible. This is a big release containing a number of features, a lot of internal refactoring and some potentially-incompatible changes. Snapshot releases for portable OpenSSH are available from http://www.mindrot.org/openssh_snap/ The OpenBSD version is available in CVS HEAD:

Hi, The systrace and rlimit sandboxes have been committed and will be in snapshots dated 20110623 and later. This diff adds support for pre-auth privsep sandboxing using the OS X sandbox_init(3) service. It's a bit disappointing that the OS X developers chose such as namespace-polluting header and function names "sandbox.h", "sandbox_init()", etc. It already forced me to

Hi, When I tested the latest snapshot on FreeBSD 4.2, I noticed some implicit declaration warnings I didn't recall seeing on Linux. I think this is caused by the fact that if autoconf does detect the presence of some BSD capability, necessary header files and declarations may not be included (as these are assumed to be the same ~everywhere, and already included). If such capability is

Hi, OpenSSH 7.4 is almost ready for release, so we would appreciate testing on as many platforms and systems as possible. This release contains some substantial new features and a number of bugfixes. Snapshot releases for portable OpenSSH are available from http://www.mindrot.org/openssh_snap/ The OpenBSD version is available in CVS HEAD: http://www.openbsd.org/anoncvs.html Portable OpenSSH is

Hi. New (2.1.1p1) login code is nicer on AIX (4.2.1.0.06). Thanks. A couple of issues, though, which I haven't really dug into yet. I'm wondering if anyone else has seen them? If not, I'll investigate & report. 1. If I set "UseLogin" to "yes", everything seems fine except that the authentication agent forwarding doesn't work. The "SSH"

One other thing I noticed in the record_utmp_only() function is that it wasn't setting the timestamp in the logininfo structure. The following patch takes care of this: --- old/loginrec.c Wed Jun 6 11:12:14 2001 +++ loginrec.c Wed Jun 6 11:13:42 2001 @@ -448,6 +448,8 @@ login_utmp_only(struct logininfo *li) { li->type = LTYPE_LOGIN; + /* set the timestamp */ +

FYI-- session.c fails from openSSH 2.9.9p2 with SunPro C compiler on Solaris 7, 8. The function do_pre_login had to be moved to before its use in do_exec_pty (a predeclaration would work). It does appear to work correctly, given the above fix. Still having the largefile problem (argh), so if anyone can help with /that/ ... -- Austin David -- Sr. Systems Architect Wink Communications

http://bugzilla.mindrot.org/show_bug.cgi?id=637 Summary: ssh records that the user has logged out even though an sftp session is active Product: Portable OpenSSH Version: 3.6.1p2 Platform: All OS/Version: All Status: NEW Severity: security Priority: P1 Component: ssh AssignedTo:

Hello, I just installed the above openssh onto a Sun Solaris 7 and Solaris 8 system. No problem with that. However, I now seem to get some rubbish processed when I login with slogin. An example: Last login: Tue Jun 13 12:31:27 2000 from jhorne.csd.plymo:tJ` ^[[?1;2c Telnet logs in okay, but just shows 'Last login...jhorne.csd.plymo'. This seems to get passed to the shell, which it of

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

Hi all, just I installed OpenSSH 2.2.0p1 on a HPUX-11 machine and it works. But when I connected to the machine and give "finger -R"-command then in the "Where"-column I see the hostname of the openssh-server instead of the hostname where I came from. Does anybody have an idea? Thanks Stephan -- LDS Brandenburg Dr. Stephan Hendl fon: +49-(0)331-39 471 fax:

Follow-on to Charles Levert's <charles at comm.polymtl.ca> work on utmp_write_direct. Fixed: -- At logout, the utmp entry is cleared. Tested on SunOS 4.1.4. The code I added to loginrec.c is restricted to SUNOS4 pending QA testing on other platforms. This patch incorporates the work done by Charles Levert on 7/25/2000 00:43:22. (Do any of us sleep at

OpenSSH-3.0p1-pre, from CVS as of about 2001-10-30 23:45 UTC. Any particular reason why configure is checking for login() in -lutil, finds it, then checks for it again in -lbsd? Here's the relevant excerpts (Red Hat Linux 6.2, , kernel-2.2.19, glibc-2.1.3, egcs-1.1.2, autoconf-2.52): $ CFLAGS='-O2 -mpentium -Wall'; export CFLAGS $ ./configure

SCO OpenServer 5.0.x Openssh 3.6p1 loginrec.c writes incorrect data into the ut_id field of the utmp file. This has been an issue since at least openssh 3.0.2 but I never bothered to report it. For Openssh 3.6p1, defining WITH_ABBREV_NO_TTY corrects the problem. Below is a brief patch to configure which does this. You can observe the errant results in the "Line" column from the

Outside the known 'Hang-on-exit' bug and the Solaris 'PAM_TTY_KLUDGE' required. *WHAT* other issues *MUST* be address before 3.0 which is approaching fast? Those running NeXTStep I need conformation that it works under NeXT. My current Slab is packed in a storage unit due to a fire in my apartment complex (happened above me so I'm wrapping up dealing with that crap =). -

Fixed: -- On systems such as SunOS4 where the system include files are no help in locating the utmp file (et al.), configure can define their location in CONF_*, but defines.h never used these. -- Might as well put in the usual location for SunOS4. -- In loginrec.c (utmp_write_direct), writing to the utmp file was not done correctly. Remaining: -- At logout, the utmp entry cannot be

The following alteration needs to be made to loginrec.c in the routine record_failed_login() #ifdef USE_UTMP ??????? construct_utmp(&li, &ut); #endif It was missing "#ifdef USE_UTMP" which causes an problem if you are not using UTMP. gt

Hi, In loginrec.c, the 'line' string utility function line_abbrevname() returns the last four characters of the terminal file path. This returned value is assigned to the utmp structure member ut_id[4]. Some sample ut_id values are shown below: /dev/pts/1 will have ut_id set to ts/1 /dev/pts/2 will have ut_id set to ts/2 . . /dev/pts/9 will have ut_id set to ts/9 /dev/pts/10

On Mon, 1 Apr 2019 at 23:23, Kevin Brott <kevin.brott at gmail.com> wrote: [...] > port-aix.c:316:1: error: conflicting types for 'record_failed_login' > record_failed_login(const char *user, const char *hostname, const char *ttyname) I think I just fixed that by changing the function to match the new prototype. Unfortunately I can't currently test it myself. Please

I spent some time with 3.0.2p1 to discover why OpenSSH on HP/UX 11.00 64-bit corrupts the /var/adm/wtmp file. The problem is with the utmp structure itself. When building with 32-bit compilation flags, the size of the utmp structure is 60 bytes. When building under 64-bit, the size is 72 bytes. The size difference is due to structure alignment and using basic types whose size changes depending