Re: SSHD - cant run daemon

From: Nico Kadel-Garcia (nkadel@bellatlantic.net)
Date: 10/29/02

  • Next message: Darren Tucker: "Re: OpenSSH Password Aging/Expiration on UW2.1.3" 

    From: "Nico Kadel-Garcia" <nkadel@bellatlantic.net>
Date: Tue, 29 Oct 2002 00:41:50 GMT

    "Robert" <gojuka@si.rr.com> wrote in message
    news:742c30b4.0210281445.c43058e@posting.google.com...
    > "Nico Kadel-Garcia" <nkadel@bellatlantic.net> wrote in message
    news:<XUUu9.33150$wm6.16973@nwrddc01.gnilink.net>...
    > > "Robert" <gojuka@si.rr.com> wrote in message
    > > news:742c30b4.0210270735.6eaae9ed@posting.google.com...
    > > > I am trying to learn the ssh, and was messing around with the config
    > > > file. At first it was running fine, then all of a sudden it wouldnt
    > > > let me run SSHD anymore. Here is error message:
    > > >
    > > > # /usr/local/sbin/sshd
    > > > sshd: SSH Secure Shell 3.2.0
    > > > sshd[1950]: FATAL: Creating listener failed: port 22 probably already
    > > > in use!
    > >
    > > Does someone else have root privileges to run SSHD with, or have you
    > > accidentally put it in inetd.conf or xinetd?
    >
    > No one else has root priveleges. I checked xinetd.conf and there is
    > no trace of anything there. There is nothing running on port 22
    > (netstat -nat). I dont understand. There is no trace of the sshd
    > running at all (ps -aux | grep sshd) Could this have to do with the
    > configuration file? I also noticed that i have ports 32768 ad 32769
    > open and waiting for connections. They were never there before. Is
    > there a way to find out what software is listening on those ports? If
    > I cant figure this out, is there a way to remove the current sshd and
    > reinstall it? (that seems like the easy way out...:-)

    Uh-oh. Hmm. It wouldn't be in xinetd.conf: it would be in /etc/xinetd.d/*.

    I wonder if you've got something odd going with your SSH installation. Can
    you rip it out and work with OpenSSH, which is superior in a bunch of way?
    In particular, the older ssh.com system of running sshd2 on port 22 and
    having that summon sshd1 if an SSH1 connection is detected was detestable. I
    assume they've eliminated this wackiness with SSH 3.2.0, but do you maybe
    have a dangling sshd1 floating around somewhere?

    Relevant Pages

    • RE: possible ssh hack
      ... What version of SSHD were you running, ... Apache and we can help you out. ... Subject: possible ssh hack ... port 4207 ...
      (Incidents)
    • Re: Odd ssh attacks?
      ... Here is how I defend against ssh attacks. ... That will stop all traffic to servers like sshd that pay attention to ... Have sshd ALSO listen on a non-standard port and open up your router ...
      (Ubuntu)
    • Re: Latest SSH?
      ... >>scan to check that ssh was the only port visible to the outside world. ... >as that's the last OpenSSH advisory published. ... can sshd be prevented from reporting its version number on ...
      (freebsd-questions)
    • Re: OpenSSH 3.4 and firewalls
      ... sshd process on my machine never acknowledges the request. ... You can see that the ssh client is attempting to connect on the ... correct port, which the firewalls should forward to my machine. ... To verify that the firewall was not at fault, I ran tcpdump with the ...
      (comp.security.ssh)
    • Re: ssh alternatives
      ... I wonder if its possible to run sshd on two different ports on ... separate interfaces.. ... > We run ssh on a non-standard port and have no issues with scripts.... ...
      (RedHat)