similar to: [PATCH/cygwin] Fix cygwin specific Makefile and a bug in the ssh-host-config script

Hi, could somebody with checkin rights please apply the below patch? It only changes the Cygwin specific installation so that it doesn't bail out if documentation files don't exist. Last time the WARNING.RNG file disappeared, and the Cygwin post-install step failed. Thanks, Corinna Index: contrib/cygwin/Makefile =================================================================== RCS

Hi, below is a patch which only affects Cygwin. It adds the $(EXEEXT) suffix in calls to install, and it fixes the list of documentation files to install into /usr/share/doc/openssh in a Cygwin installation. Thanks, Corinna Index: Makefile.in =================================================================== RCS file: /cvs/openssh/Makefile.in,v retrieving revision 1.306 diff -u -p -r1.306

Hi, the below patch to contrib/cygwin is a major rework to allow various changes in the installation process on Cygwin machines. The important changes are: - New Makefile, providing a `cygwin-postinstall' target which allows to create a base installation as in the Cygwin distribution, which should be run right after a `make install'. - Additional information given in the README

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

Hello, I'm trying to build a valid public ssh v2 RSA key from a java application but I have some problems understanding how the two numbers (e and n) are base64 encoded into ~/.ssh/id_rsa.pub or ~/.ssh/authorized_keys2 file. My question is what exactly is encoded into the base64 string? For example for this public key: ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEA6p76zG+8aOkFZT1y4O+Y7n

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

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:

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

The attached patch (relative to the current CVS snapshot) uses a perl script to convert the OpenSSH manpages from the BSD -mdoc format to the -man format used by other systems. This allows the unformatted manpages to be installed normally, rather than defaulting to preformatted pages. I'd like to see this patch integrated into the portable version of OpenSSH. Please let me know what you

Hello again, In my constant recompiles of 2.9p1 and 2.9p2, I've noticed that upgrading a current installation with a test compile leads to tons of files being updated even when they don't need to be. The attached patch for Makefile.in splits the install-files target into a bunch of serparate targets: install-dirs, install-prog, install-man, install-conf, which are then all called in

I need ssh-add to fail cleanly if it tries and fails to read a key, rather than prompting the user. I can't seem to figure out how to do that. This is on a Linux 2.6.26 system, running OpenSSH 5.1p1 (as built on debian lenny/sid) First, the things i've tried: * i've unset the DISPLAY and SSH_ASKPASS environment variables, so no X11-style prompting should happen. * i've

Hi, the following patches are in the NetBSD packages collection to get OpenSSH 1.2.2 going. Changes: * /dev/urandom may be there but not in the kernel - make sure * Pull in some more headers needed by configure * Add proper ld-flags for ELF platforms * Some code cleanup * Install example files always to a different dir, and use out build system to DTRT WRT getting them to /etc.

Hey folks-- When ssh creates a known_hosts file for a user, it disregards the currently-set umask, and can actually turn on mode bits that the user has explicitly masked. While i'm happy to have ssh make files *more* secure than my umask (in situations where that's reasonable, like the creation of new ssh keys, etc), i'm not sure that i see the point in ssh making the files more open

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, Currently using openssh-4.5p1 on Solaris 8 in conjunction with Oracle 8i dataguard. Is there a patch available to prevent ssh returning status code 255 for a successful execution of a remote connection/command. Many Thanks, Tim Mann

Hello all, Tested the latest snapshot. ssh-keyscan seems to have gone in. :) Two issues about it (patched): 1) the man pages aren't installed, only uninstalled 2) RH spec file (and the others no doubt..) won't include it. General observations: for RSA keys only?, kinda obsoletes contrib/make-ssh-known-hosts*. -- Pekka Savola "Tell me of difficulties surmounted,

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

Hi, I have already sent this once, but since the problem persists here it is again. Please consider the attached patch for inclusion in the rsync distribution. The patch fixes the problem that 'make install-strip' tries to strip the manpages and thus fails. An other part of the patch adds DESTDIR (for package building). This is nowadays part of all automake generated Makefile's,

This applies to all platforms, I think: $ make install [snip] if [ ! -z "yes" ]; then \ ./install-sh -c -m 644 ssh-rand-helper.8.out /home/dtucker/openssh/openssh-cvs-test/contrib/aix/package/usr/local/man/man8/ssh-rand-helper.8 /bin/sh: 0403-057 Syntax error at line 1 : `then' is not matched. make: *** [install-files] Error 2 Looks like missing line continuation in

hi folks: it looks like ssh-keygen -r can''t export SSHFP records for ECDSA keys: 0 dkg@pip:/tmp/cdtemp.oiRYAS$ ssh-keygen -f foobar -t ecdsa -q -P '''' 0 dkg@pip:/tmp/cdtemp.oiRYAS$ ssh-keygen -r foobar -f foobar.pub export_dns_rr: unsupported algorithm 0 dkg@pip:/tmp/cdtemp.oiRYAS$ the first number in my prompt is the return code of the last command; note that