similar to: Need configure parameter for SSH_PROGRAM

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 ***

Please excuse me for mailing you directly instead of using the 'sendbug' facility; it seems to be an OpenBSD-only facility, and I didn't see a bug-tracking interface on the web site. I know the "UseLogin" feature is deprecated (to some degree, at any rate), however, on a Red Hat 6.2-based system, it is broken, because ssh.h statically defines LOGIN_PROGRAM as /usr/bin/login,

http://bugzilla.mindrot.org/show_bug.cgi?id=198 Summary: Error getting file with sftp on old F-Secure servers Product: Portable OpenSSH Version: 3.1p1 Platform: Sparc OS/Version: Solaris Status: NEW Severity: major Priority: P2 Component: sftp AssignedTo: openssh-unix-dev at mindrot.org

what do you think about this patch to add the path to scp to _PATH_STDPATH? is there a better or cleaner way to do this? i'm hoping to ward off 'scp doesn't work' questions for the next release. i did *not* add this to a --with-default-path path, because if a user specifies that, they should control its value completely. Index: Makefile.in

http://bugzilla.mindrot.org/show_bug.cgi?id=187 Summary: ssh-keygen not converting from and to SECSH standard correctly Product: Portable OpenSSH Version: 3.1p1 Platform: Sparc OS/Version: Solaris Status: NEW Severity: normal Priority: P2 Component: ssh-keygen AssignedTo:

I've been working on a NetBSD package for openssl-1.2pre12, and I've noticed that Makefile.in installs ssh-askpass in $prefix/lib/ssh ($libdir) instead of $libexecdir/ssh. Since it is an executable, IMHO it should be in the latter spot. In the patch below, I've fixed this, as well as made ASKPASS_PROGRAM used during the install so that it's easier to maintain. Thanks, David ---

Dear openssh-developers, the new external program ssh-rand-helper appeared in OpenSSH 3.1. While the SFTP_SERVER is defined using a _PATH_SFTP_SERVER pointing to SFTP_SERVER in Makefile.in and defining a default-path in pathnames.h the ssh-rand-helper is simply SSH_RAND_HELPER and defined with a fixed path in Makefile.in and not having a default in pathnames.h. I propose a handling analogous to

Below I've includes a patch which helps build OpenSSH outside from a read-only source tree, find OpenSSL on Mac OS X, and fix a typo. This applies to OpenSSH 2.1.1p4. You should already have gotten a note from Melissa O'Neil about a conflict with the crc32() symbol in zlib, which was causing a crash on Darwin. I've noticed another bug. If ssh is setuid, I get a permission

Hi All, Below (and attached) is a patch that will allow openssh to be installed in an alternate location. This is essential when cross-compiling. The cross-compile use case is: configure [bunch-of-options] make DESTDIR=<alt-location> make install-nokeys I believe the patch may also be useful for non-cross-compiling cases. Regards, ...doug ---8<----- diff -uraN

[Please Cc: me, I'm not on the list] fsh (http://www.lysator.liu.se/fsh/) is a program that keeps an ssh tunnel open and multiplexes multiple batch sessions through that single connection, avoiding slower public key crypto for things like cvs. fsh includes an utility called fcp that can multiplex file copies through this single connection. It relies on scp for the actual file copying,

The sshd server normally builds the environment variables from scratch for a shell process it creates. Except when compile for Cygwin, it simply adds settings to its own set of environment variable settings. A comment in the code says this special case is made because in Cygwin, some of sshd's environment is important for child processes too. I don't run Cygwin (I run Linux), but on my

Hi there, I have a need to have scp pass the -P option to ssh to "bypass" the packetfilters that doesn't allow connections to return to arbitary "priviledged" ports, ie. ports <1024. See attached context sensitive diffs against 2.2.0p1 to please integrate. Thanx Hendrik Visage -------------- next part -------------- *** 1.1 2000/10/11 13:31:45 --- scp.c 2000/10/11

Are there multiple ways that Windows clients encrypt passwords? I'm seeing different behavior between two clients. On one, I can access a Samba share just fine. On the other, using the same username and password to access the same share, I get "incorrect password." Looking for the difference in Samba debug traces, I find it comes down to this: smb_password_ok: Checking SMB

If you've applied my previous scp patch with the tempfile options and the erase option, here's a diff that tweaks it a bit more. Previously I had decided to use getcwd() in a certain local-to-local special case (that needs to use scp rather than regular cp). This was because spawing scp via ssh resets the current directory. This patch choose to forego that in favor of a simpler

My libcrypto does dynamic library linking (dlopen(), etc) and consequently prerequires libdl. I.e. if you link with -lcrypto, you must also specify -ldl. I don't know how unique this situation is to me, but it causes configure to fail. The symptom is that configure complains that libcrypto does not exist (because it does a test link to test for existence of libcrypto and assumes that any

I sent an email to samba-bugs@samba.org. I got back an automated reply that said Please go to http://bugs.samba.org and read the instructions before submitting a bug report. I went there, and the instructions (which I found by clicking where it said to click "here" for instructions), say to send email to samba-bugs@samba.org. I suspect what I'm really supposed to do is fill

Hello, in order to use "scp", the scp binary has to be in the compile-time default path on the remote host. For some users (like root), we try to avoid this since scp may be on a network file system (AFS/NFS), and we don't want to hang root's session on network outages. Would a patch to scp be acceptable in the main tree that allows to set the path to remote scp explicity,

Hi there, I've written some enhancements to scp.c and pathnames.h to enable the scp to arbitrarily set the remote scp path. (eg $ scp -e /usr/bin/scp foo user at bar:foo) I did read the "scp: command not found" FAQ entry but I'm not quite sure why we can't do this, unless it's because enhancements to scp are no longer a priority. Any other reason why it "is the

How come "StrictHostKeyChecking ask" doesn't cause Ssh to ask me if I'm OK with a host key having changed and, assuming I say yes, go ahead and update known_hosts? It looks like the program gratuitously runs me through the exercise of editing known_hosts and starting over. Kudos for having the message tell me exactly what I have to delete, though. -- Bryan Henderson

I suggest a warning be added to the ssh-keygen documentation, if not ssh-keygen output, that using the -b option to select fewer than 768 bits will generate a key that can't be used as a host key. Actually, I don't know whose requirement the 768 minimum is, but Openssh's 'ssh' program is coded to reject keys shorter than that. I had availed myself of the the ssh-keygen -b