similar to: [Bug 1728] New: unnecessary "./" in slogin and slogin.1 symlinks

Hello, There are three small problems with the "slogin" and "slogin.1" symlinks created upon installation: 1. "./" is included in the target path unnecessarily. 2. Symlinks are assumed to be available, while only hardlinks could. 3. EXEEXT is not respected for slogin. Here is a fix for both problems -- the "./" is simply removed, EXEEXT is added, the

It appears that the redhat/openssh.spec has not been updated to account for the removal of slogin from the build. This breaks rpmbuild. Specifically lines 361 and 362 still have the following: %attr(-,root,root) %{_bindir}/slogin %attr(-,root,root) %{_mandir}/man1/slogin.1* Robert Moucha Geophysics Syracuse University

slogin "deadlocks" if you invoke it with the (useless, but legal) switch "-n". stdin is not passed to it (and the local ssh process ignores stdin), so it is not possible to kill it using <<~.>> Should the "-n_ switch be disallowed for an interactive invocation? Martin -- <Martin.Kraemer at Fujitsu-Siemens.com> | Fujitsu Siemens Fon:

http://bugzilla.mindrot.org/show_bug.cgi?id=509 Summary: slogin.1 is a broken symlink Product: Portable OpenSSH Version: -current Platform: All OS/Version: Linux Status: NEW Severity: trivial Priority: P4 Component: Documentation AssignedTo: openssh-unix-dev at mindrot.org ReportedBy:

We have been using OpenSSH version 2.3.0p1 for a couple of months now with out problems. The same goes for several previous versions we have used over the last year. However, I have just installed version 2.5.2p2 and it is giving me some problems. If it were not for the latest security bulletins strongly suggesting we upgrade, I would reinstall the 2.3.0p1 version. I am running on a SGI

Hello. I noticed that OpenSSH 2.1.1p3 does not check whether it is being called as rlogin or slogin, like it's siblings do. This can get ugly if you have rlogin and rsh symlinked to ssh, and old r* commands are moved off in another place, as I do. Since Solaris rsh is hardcoded to call /usr/bin/rlogin, it will get stuck in an infinite loop. Below is a quick patch I hacked up, based on

Hi, I want to integrate openpam with openssh in our server (which uses QNX632 operating system). I am facing some problems in the "make install" part of openssh. Following are the steps I followed to build zlib, openssl, openpam and openssh. *NOTE*: Since I want the sshd and ssh binaries in my server(using QNX), I had to cross compile the packages for QNX (environment was set to x86)

This is automatically generated email about markup problems in a man page for which you appear to be responsible. If you are not the right person or list, please tell me so I can correct my database. See http://catb.org/~esr/doclifter/bugs.html for details on how and why these patches were generated. Feel free to email me with any questions. Note: These patches do not change the modification

Hi, could somebody with checkin rights please apply the below patch to the Cygwin postinstall Makefile? The patch adds two changes: - Install ssh-copy-id and ssh-copy-id.1 as well. - Gzip all man pages. Thanks in advance, Corinna Index: contrib/cygwin/Makefile =================================================================== RCS file: /cvs/openssh/contrib/cygwin/Makefile,v retrieving

Hi admins, thank you for maintaining useful development resources. But I'm in trouble. Please help. I and some developers are unable to use ssh login over 24 hours. Is there a intended service interruption? Or some problems are lying? I and some developers could slogin to freedesktop.org before the problem had occurred. My local environment has not altered in recent days. my source address:

Hi! I have problems with connections being left open with both 2.2.0p1 and the latest snapshot when using agent-forwarding. (I didn't use this with older versions, so I don't know whether this problem is older.) Scenario: I have a secret key that I run with ssh-agent on host "host-A". I then connect to "host-B" using 'slogin -A host-B'. When executing a

Hi, This patch fixes a couple of small ``problems'' in 1.2pre17 Makefile.in: 1. Avoid making an empty $(libexecdir)/ssh directory. 2. Don't try to uninstall $(mandir)/man1/slogin.1 twice. --- openssh-1.2pre17/Makefile.in~ Thu Dec 9 00:48:58 1999 +++ openssh-1.2pre17/Makefile.in Thu Dec 9 06:51:41 1999 @@ -92,9 +92,9 @@ -rm -f $(mandir)/man1/slogin.1 ln -s ssh.1

Hello, System info: Sparcstation 5, Solaris 2.7, openssl-0.9.8i. I've tried to install openssh-3.9p1 openssh-4.9p1 openssh-5.1p1 all failed the similar way. The following is the last portion of the 'make install' printout. ./install-sh -c -m 0755 -s ssh /usr/local/bin/ssh BFD: /usr/local/bin/stkuaiGw: warning: allocated section `.interp' not in segment ./install-sh -c -m 0755

the configure option --program-prefix does not work although it is listed in teh configure --help output. The attached patch fixes these issues: 1) program prefix is not substituted in configure 2) program prefix is not present in Makefile 3) scp requires use of a known "scp" program -- bryan diff -cr openssh-2.9.9p2.orig/Makefile.in openssh-2.9.9p2/Makefile.in ***

Can any HP/UX users comment? -- | "Bombay is 250ms from New York in the new world order" - Alan Cox | Damien Miller - http://www.mindrot.org/ | Email: djm at mindrot.org (home) -or- djm at ibs.com.au (work) ---------- Forwarded message ---------- Date: Thu, 20 Jul 2000 09:16:23 +0200 From: "[iso-8859-1] SOETE Jo?l" <JSO at EUROPAY.COM> To: "'openssh at

I am not sure where to begin so I will be as verbose as I can to explain the problem. I have 3 servers. Their specs are: Machine A: Redhat 7.1 kernel 2.4.9-34 openssh 3.1p1-5 Machine B: Redhat 7.3 kernel 2.4.9-31 openssh 3.1p1-5 Machine C: Debian Woody kernel 2.4.18-bf2.4 openssh 3.4p1 rsync 2.5.6 I am running an rsync over ssh from Machine C to Machine B with the following: rsync --verbose

Enclosed is a patch against 2.2.0p1 that teaches ssh (and therefore slogin and scp) how to invoke ssh-askpass to request a password, RSA/DSA key passphrase, or an skey challenge response. I've tested this on Linux (i386), for passwords and RSA/DSA key passphrases. I cannot easily test whether the Right Thing will happen for skey challenge responses; I would appreciate it if someone who uses

http://bugzilla.mindrot.org/show_bug.cgi?id=1038 Summary: buildpkg.sh postinstall script does not install RC links using installroot and non-symlinks. Product: Portable OpenSSH Version: 4.0p1 Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component:

Folks: Thanks to all who helped me get ssh up and running on my development box. Now I want to make a distribution package to take and install on the rest of my network. I am not sure what to transfer from box to box and what to run to get started. I did the install on the dev box and all tested fine. Is there a "standard distribution" list of only files required for running ssh on

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: