similar to: Default libexec dir

On Mon, 2 Sep 2024, radiatejava wrote: > I know that I can use --libexec=dir arg when running configure for > openssh code. However, on my ubuntu OS, it seems sshd is using > /usr/local/libexec as the default libexec dir when I do not provide > --libexec=dir during the configure cmd. Can it not use the default > /usr/libexec dir instead? It will use libexec under the --prefix that

Team, We upgraded sshd in our product from OpenSSH 8.6 to OpenSSH 9,.6. After the upgrade, clients are seeing significant increase in time to do ssh to the listener. Normally, a single ssh does not matter much but some of our workflows involve about 3000 to 4000 ssh connect and close and this is hitting us hard, I enabled logging on the server side. I see the most of the increase is here in

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)

On Fri, 30 Aug 2024 at 09:58, radiatejava <radiatejava at gmail.com> wrote: > I am trying to build OpenSSH 9.8p1 with my SSL installed at > /opt/customssl, but it fails. It fails at the configure cmd itself. It > does not seem to be honor --with-ssl-dir=/opt/customssl option. What > could be the issue here? Assuming your custom thing is API compatible, the usual reason for this

Hello team I am trying to build OpenSSH 9.8p1 with my SSL installed at /opt/customssl, but it fails. It fails at the configure cmd itself. It does not seem to be honor --with-ssl-dir=/opt/customssl option. What could be the issue here? $ ./configure --with-pam --with-ssl-dir=/opt/customssl <<some output removed>> checking for openssl... /usr/bin/openssl checking for

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

Currently we hardcode various paths such as $libexec/xen/{bin,boot}, however some downstreams (notably Debian) would like instead to install things into $libexec/xen-X.Y/{bin,boot} as part of allowing multiple versions of the tools packages to be installed. Since this currently involves patching configure its a bit fiddly, provide a configure option for the leaf dir instead, name it

Hi, I just tried building of OpenSSH-2.1.0 on HP-UX 10.20 and found the following items: - The configure command I used at the beginning: CC=cc CFLAGS="-Ae +O2 +DAportable" CPPFLAGS="-I/usr/local/include -I/usr/local/s sl/include -I/usr/include/X11R6" LDFLAGS="-L/usr/local/lib -L/usr/local/ssl/lib -L/usr/lib/X11R6" ./configure --prefix=/usr/local/openssh

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, This may or may not be a bug. However, it is DEFINITELY NOT how I would expect and want to see sshd work! If you run lsof against sshd on a privilege separated user, it shows that sshd's CWD is /. I would hope that the CWD would be at a minimum /var/empty/sshd and I would really have thought it would be something along the lines of

I have tried to update openssh-3.1p1 of our system that uses RH7.2 (Scyld). I is pretty much a standard Redhat 7.2 install with openssl-0.9.6b, zlib-1.1.4 etc. I have gotten openssh to work after some initial issues, but I still have not been able to get openssh/sshd to work with tcp-wrappers. I have in hosts.deny ALL: ALL: and in hosts.allow ALL: localhost, 127.0.0.1, 192.168.1. and still I

Hi all, I build openssh for aix with a dirty hack. This is my configure: export CC=cc export CFLAGS="-I/usr/local/include" export LDFLAGS="-L/opt/freeware/lib/ -L/usr/local/lib" export CPP="cc -E" ./configure --prefix=/usr/local --sysconfdir=/usr/local/etc/ssh \ --with-cflags="-O -D__STR31__

i'm have some trouble rebuilding src rpms for 2.3 on a (mostly) redhat 6.2 machine. i have updated a few of the libraries, and am running rpm version 3.0.4-0.48, which is pretty recent i think. the problem is that the openssh rpm doesn't seem to actually produce an rpm file(s). i run it, everything seems to compile ok, it looks like it tries to build the rpms, but then i can find

Hello, I am having a very aggrivating problem, and I will try and provide all of the necessary information. I have openssh-3.7.1p2 with openssl-0.9.6k installed on Solaris 8. Here is what I've been able to determine so far: 1. Local account authentication works fine (non-NIS+). 1a. NIS+ is running at security level 2 2. Telnet authentication works fine. 2a. When I use the SSH client,

When doing a make with the portable developer version, I came across this error: ssh/ssh_host_ecdsa_key|/opt/etc/ssh_host_ecdsa_key|g' -e 's|/etc/ssh/ssh_host_dsa_key|/opt/etc/ssh_host_dsa_key|g' -e 's|/etc/ssh/ssh_host_rsa_key|/opt/etc/ssh_host_rsa_key|g' -e 's|/var/run/sshd.pid|/var/run/sshd.pid|g' -e 's|/etc/moduli|/opt/etc/moduli|g' -e

I have successfully compiled OpenSSH 3.1p1 for the following systems: Solaris 8 Solaris 7 Irix 6.5.14 Irix 6.5.4 SunOS 4.1.3_U1 Unfortunately, the new sshd is not working on any of the above systems with the exception of Solaris 7. (I then put the Solaris 7 executables on Solaris 8, and they worked there too.) This is the error I'm getting: $ /usr/etc/sshd -D -d -d -d debug3: Seeing PRNG

Hello, I am experiencing some strange behaviour that I am hoping someone can shed some light on. OS and kernel: Red Hat Enterprise Linux AS release 4 (Nahant Update 5) Linux host135 2.6.9-67.9hp.7sp.XCsmp #1 SMP Thu Jul 3 18:55:59 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux built both openssh-5.0p1 and openssh-5.1p1 with the following options: ./configure --prefix=/usr

Rather then implementing kafs in MIT Kerberos, I would like to suggest an alternative which has advantages to all parties. The OpenSSH sshd needs to do two things: (1) sets a PAG in the kernel, (2) obtains an AFS token storing it in the kernel. It can use the Kerberos credentials either obtained via GSSAPI delegation, PAM or other kerberos login code in the sshd. The above two

Here's what I get: bash-2.02# sshd -ddd -p 1234 debug3: Seeding PRNG from /usr/local/libexec/ssh-rand-helper debug1: sshd version OpenSSH_3.5p1 debug1: private host key: #0 type 0 RSA1 debug3: Not a RSA1 key file /etc/ssh/ssh_host_rsa_key. debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1 RSA debug3: Not a RSA1 key file /etc/ssh/ssh_host_dsa_key. debug1: read PEM

On Sun, 28 Jul 2024 at 22:34, radiatejava <radiatejava at gmail.com> wrote: > We upgraded sshd in our product from OpenSSH 8.6 to OpenSSH 9,.6. > After the upgrade, clients are seeing significant increase in time to > do ssh to the listener. Normally, a single ssh does not matter much > but some of our workflows involve about 3000 to 4000 ssh connect and > close and this is

I run OpenSSH on linux @ client which ssh /usr/local/bin/ssh ssh -v OpenSSH_6.7p1, OpenSSL 1.0.1j 15 Oct 2014 @ server which sshd /usr/local/bin/sshd sshd -v unknown option -- V OpenSSH_6.7p1, OpenSSL 1.0.1j 15 Oct 2014 usage: sshd [-46DdeiqTt] [-b bits] [-C connection_spec] [-c host_cert_file] [-E log_file] [-f config_file] [-g login_grace_time]