similar to: Bug Report - sshd invoked by inetd on Solaris 8

It would seem I didn't test this thoroughly enough before I sent my email. I can reproduce the problem (same openssh version) on both Solaris 8 and Solaris 6. (I had thought it was only on Solaris 8.) I haven't checked to see if it exists on other versions of Solaris, but the problem does not exist however on RedHat 6.2 running the same openssh version. I hope that helps. Adam Benjamin

I haven't been able to get scp to work with RedHat 6.2 (select: Bad file descriptor), so... I tried upgrading with openssh-2.3.0p1-1.src.rpm and openssl-0.9.5a-3.src.rpm No joy. When running just ssh, I get "Disconnecting: Bad packet length 795178083." This seems to be a problem with sshd, since the 2.3 ssh client will work fine with a 2.1 server (but not scp, which still gives

http://bugzilla.mindrot.org/show_bug.cgi?id=1344 Summary: DISABLE_FD_PASSING does not work if sshd invoked by inetd Product: Portable OpenSSH Version: 4.6p1 Platform: Other OS/Version: Other Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: bitbucket at

I'm having difficulty getting ssh to connect as any local user under OSX 10.3.8. The odd thing is ssh -l root localhost works fine as a normal user, whereas ssh -l themac localhost (or from any host for that matter) does not. Thanks =============================== debug1: sshd version OpenSSH_4.0p1 debug1: private host key: #0 type 0 RSA1 debug1: read PEM private key done: type RSA debug1:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've seen a few posts, but no solutions as of yet. Here's a bit more info. BoxA - Solaris 2.7, Maintenance Update 01/09/2001, SunWorks cc compiler BoxB - Solaris 2.8, gcc-2.95.2 gcc compiler BoxC - Solaris 2.7, Maintenance Update 01/09/2001, gcc-2.95.2 gcc compiler BoxD - OpenBSD 2.8, patched to STABLE, gcc-2.95.2 _and_ BSD cc compilers

Hello all In a recent spate of paranoia we set our server (SuSE Linux 7.0, kernel 2.2.16) to use SSH version 2 and not SSH1. With openssh 2.3.0p1-5 running as client and server, we find that stdout output is occasionally dropped: ssh server echo "JJJ" usually emits JJJ, but sometimes returns nothing -- although the command is apparently performed. In the happy case the server logs

Hallo all! I've found a repeatable problem concerning openssh 2.3.0p1 running on a Linux-box with kernel 2.2.17. I compiled ssh from sources with pam-support. Let me describe what I'm doing: rsync -e ssh --delete --exclude "/Daten/test*" --exclude /Daten/anonymous --exclude /Daten/comp_logs --exclude /Daten/ehemalige_rwgsysm/cache --exclude

I have installed 2.5.1p1 on two systems, one running Digital Unix 4.0F and the other running Red Hat Linux 7.0. I am having trouble connecting using the 2.5.1p1 client and the version 2 protocol. Here is a connect attempt from the Linux box (this is after I blew away my ~/.ssh directory to make sure there was no "cruft" in it). Note that this also has the all zero key fingerprint that

The segfault logged below occurs on two different Red Hat 6.2 systems running OpenSSH installed from the 2.5.1p2 RPM. (Similar problems occured with the 2.5.1p1 RPM.) The most recent of the Red Hat 6.2 systems tested is stock except for an upgrade of rpm-3.0.5-9.6x.i386.rpm and the install of Red Hat's release of openssl-0.9.5a-3.i386.rpm, both necessary for the OpenSSH RPM install. The

Hi, Connecting from RHL7 with OpenSSH 2.3.0p1 or 2.5.0p1 to OpenSSH 2.3.0p1 on AIX 4.3.1. Protocol 2 doesn't work if you specify 'Ciphers rijndael128-cbc' or Ciphers 'aes128-cbc'. sshd -d -d -d on the server shows _nothing_ about these connections. I'm not sure if rijndael has been left out from sshd somehow, but shouldn't the error message be a little more

Hi all, I just implemented (compiled from tarball) Openssh-2.3.0p1 on two different platform: an HP-UX 11.00 (the client) and a Redhat 6.2 (the server). On server (Linux RH-6.2) side the following compile options are considered: # CC="egcs" \ > ./configure \ > --prefix=/opt/openssh \ > --sysconfdir=/etc/opt/openssh \ > --with-tcp-wrappers \ > --with-ipv4-default \ >

I have a user who's password has expired (ADMCHG) flag is set in /etc/security/passwd under AIX 5.3. For some reason it is not prompting for new passwd. This worked in 3.9. Any ideas? Thanks, Ryan # /usr/sbin/sshd -d debug1: sshd version OpenSSH_4.0p1 debug1: private host key: #0 type 0 RSA1 debug1: read PEM private key done: type RSA debug1: private host key: #1 type 1 RSA debug1: read

Environment: Solaris 2.5.1 Samba 1.9.18p3 We run samba from inetd (no special reason - just how its been done in the past). Then on one server we got masses of Samba daemons running (up to 40 as a time trying to run - load average 40+!), giving following complaints: Sep 28 14:39:06 zeus.brunel.ac.uk smbd[10728]: standard input is not a socket, a ssuming -D option Sep 28 14:39:06

On Thu, 2014-01-30 at 11:25 -0500, Dan Swartzendruber wrote: > Hopefully I'm not out to lunch here. I ported tftp-hpa to our proprietary > OS, VOS (at stratus.com). We've always runs the old legacy tftpd from > inetd, so I wanted to continue doing so with tftp-hpa. It seems to work > okay, but I noticed that the code in tftpd.c has a 'while (1)' loop that > has

I'm trying to start SAMBA from the inetd. I have added the port numbers to /etc/services: netbios-ns 137/udp netbios-ssn 139/tcp To my inetd.conf I have added: netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd After this I killed any samba-prosecces, and refreshed the inetd with:

Hi all, I have noticed a problem with the newly released version 2.1.1p4 (as well as with 2.1.1p3) : If sshd is run from inetd, all interactive sessions are automatically closed right after (successful) login. The problem disappears, if sshd is run from the command line (ie. no -i option) and did not exist in 2.1.1p2. This was noticed on a linux x86 box. I have appended a typescript of the

This is regarding openssh 2.3.0p1 (the following problem was seen on Linux client / server): I have a problem with openssh when i don't "login": ie. i do the following: ssh -2 10.1.6.13 echo 0 It doesn't print the "0". However, i can get it to print the "0" by doing the following: ssh -2 10.1.6.13 echo 0 \; sleep 1 using "ssh -2 10.1.6.13"

> ?????? wrote: > > Hello Sir/Madam! > > my name is dae su kim! > i have a problem diffcult! > The problem is samba process smbd and nmbd no responsing! > This log is my problem! > help me! please help me! > > problem : SAMBA_2.0.7 > > 7 03:13:48 cad1 inetd[179]: netbios-ns/udp server > failing > 7 03:27:03 cad1

> Correct. Like most UDP-based inetd services, tftpd is intended to be run in 'wait' mode. When the first request arrives, inetd starts the service but does not read the incoming packet (it can't, because it has no way to pass it along to the server). After that, inetd ignores that socket until the server exits. This isn't critical for tftp, but it does help to keep down the

http://bugzilla.mindrot.org/show_bug.cgi?id=1185 Summary: remote ssh command runs very slow on windows 2003 Product: Portable OpenSSH Version: 4.3p2 Platform: Other OS/Version: Cygwin on NT/2k Status: NEW Severity: major Priority: P2 Component: sshd AssignedTo: bitbucket at mindrot.org