similar to: Need help with buildpkg script

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

if [ ! -f /opt/sldx/slwo/openssh-3.1p1/openssh-3.1p1/contrib/solaris/package/usr/local/etc/moduli ]; then \ if [ -f /opt/sldx/slwo/openssh-3.1p1/openssh-3.1p1/contrib/solaris/package/usr/local/etc/primes ]; then \ echo "moving /opt/sldx/slwo/openssh-3.1p1/openssh-3.1p1/contrib/solaris/package/usr/local/etc/primes to /opt/sldx/

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:

Hi, I have installed Openssh on a HP-UX 11.00 and I am having a problem. It lasts 5 minutes to login, after I enter my login and password. I try to connect from a Windows machine having a Tera Term SSH client to the HP UX with the OpenSSH server ? Why does it take so long time (5 minutes) to establish a connection from a remote machine to this openssh server ? When I do Telnet to the same

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

I gueess it is not a DNS problem, because either using name or IP, I have always the problem. I guess the problem is that I am using ssh on inetd.conf (sshd -i), so It has to generate a key each time I start a session. What do you think ? -----Mensagem original----- De: Dan Kaminsky [mailto:dan at doxpara.com] Enviada em: segunda-feira, 10 de junho de 2002 20:51 Para: Jorge Cleber Teixeira de

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)

I've made some changes to buildpkg.sh to make it easier for package builders to add their local changes. I'd like people that use buildpkg.sh to test and comment on these changes before I commit them to CVS. None of the defaults have changed. Some of the patch is is just moving chunks of code to a different location to make some of the enhancements work. Some things you may find

I am attempting to successfully run the buildpkg.sh script which is located in the contrib/solaris directory. I am receiving the following error: Building pkginfo file... Building prototype file... Building package.. ## Building pkgmap from package prototype file. ## Processing pkginfo file. pkgmk: ERROR: parameter <VERSION> cannot be null ## Packaging was not successful. pkgtrans: ERROR:

Here is a small patch for OpenSSH 3.2.3p1.. When the package postinstall script runs, it presumes that the package will be installed relative to the current / directory.. If this package is installed as part of a Solaris Jumpstart installation, this will not be the case. Consequentially, the /etc/ssh/sshd_config.default will never get copied to /etc/ssh/sshd_config on the new operating system.

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

Can someone else from the Solaris realm that uses our package system verify that this should be done? It looks right, but I want another opinion before commiting. - Ben > On Wed, 27 Feb 2002, Antonio Navarro wrote: > >> Hi Ben, >> >> I have made some modifications to the buildpkg.sh script that is >> distributed with openssh. >> >> I am sending it to

I attempted to setup openssh-3.9p1 on Mac OS X (10.3.7). The ./configure and make work fine but 'make install' fails with: computer:~/XDev/openssh-3.9p1 bcburke$ make install if test ! -z ""; then \ /usr/bin/perl ./fixprogs ssh_prng_cmds ; \ fi (cd openbsd-compat && make) make[1]: Nothing to be done for `all'. (cd scard && make DESTDIR= install)

http://bugzilla.mindrot.org/show_bug.cgi?id=1001 Summary: Error on MAKE while compiling SRPMS and tar.gz but not while installing RPMS Product: Portable OpenSSH Version: 3.7.1p2 Platform: All OS/Version: Linux Status: NEW Severity: critical Priority: P2 Component: ssh

I'm not nearly knowledgeable enough in crypto to fully understand your answer, but I will try. I wonder why moduli are not automatically generated the first time sshd is started though. That would make much more sense than shipping a default moduli file but also asking everyone to replace it with their own. On Fri, Feb 15, 2019 at 5:50 AM Mark D. Baushke <mdb at juniper.net> wrote: >

Hello. First I would like to thank you for making building the OpenSSH package so easy on Solaris 8. I wish it was so easy with all open source software. For your information, I just build and packaged OpenSSH-3.1p1 on my Ultra 5 workstation with the following packages: system SUNWadmr System & Network Administration Root system SUNWarc Archive Libraries system

Hello Ben Lindstrom, I tried your package creation scripts for Solaris which are contributed with the new OpenSSH Version 3.0.0p1. Nice that you develop these scripts but I run into a major problem installing the package which was created by the script. On our Solaris hosts /usr/local is only a symbolic link to /opt/local. After installing the OpenSSH package the symbolic link was removed and a

On Fri 2015-05-22 00:06:29 -0400, Darren Tucker wrote: > On Thu, May 21, 2015 at 11:26 PM, Matthew Vernon <matthew at debian.org> wrote: >> >> You will be aware of https://weakdh.org/ by now, I presume; the >> take-home seems to be that 1024-bit DH primes might well be too weak. >> I'm wondering what (if anything!) you propose to do about this issue, >>

https://bugzilla.mindrot.org/show_bug.cgi?id=2559 Bug ID: 2559 Summary: Warnings from reading moduli file, refer to primes file Product: Portable OpenSSH Version: 7.2p1 Hardware: Other OS: Linux Status: NEW Severity: enhancement Priority: P5 Component: sshd

For various reasons, it makes our life easier at USC to have a 'install-nosysconf' target much like the install-nokeys target that was added a while back. I mentioned this a few months back on this list and people seemed to think it wouldn't be a problem to get it into the mainline tree. I've attached the patch -- it should keep 100% backwards compatibility. Thanks. -- Phil