Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 28 Feb 2002 10:42:10 -0500
From:      Sandro Mancuso <sandro.m@videotron.ca>
To:        freebsd-questions@FreeBSD.ORG
Subject:   RE: sshd bind to port 22 fails
Message-ID:  <003401c1c06e$7c21ccd0$6400a8c0@windows>
In-Reply-To: <20020228043052.N241-100000@hal.cableone.net>

next in thread | previous in thread | raw e-mail | index | archive | help
You should also disable sshd in inetd.conf as there's no need to have 2
of them running.  Generally speaking if you don't need to have a listen
IP designated.  That's really only if you want people to be able to ssh
in only on a specific IP.  If, in my setup, I'd specify an IP like you
have, I would no longer be able to ssh from one machine to the other
through the internal LAN.  I'd have to specifically SSH to the one in
the sshd conf.  As far as security goes, If you only accept ssh
connections on the sshd u installed from the ports on the Local IP,
there's no real problem there, as no one should be able to get into your
internal LAN.  However, as I previously said, the sshd that is included
in inetd is still running...

Sandro

> -----Original Message-----
> From: owner-freebsd-questions@FreeBSD.ORG [mailto:owner-freebsd-
> questions@FreeBSD.ORG] On Behalf Of Denny White
> Sent: February 28, 2002 5:41 AM
> To: igorr@speechpro.com
> Cc: freebsd-questions@FreeBSD.ORG
> Subject: Re: sshd bind to port 22 fails
>=20
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>=20
> I have OpenSSH 3.0.2 installed on here.
> I'm still sort of new to this. Use it
> mostly since I have a constant connection
> here & 3 machines. I looked in sshd_config
> & saw where ports to listen to were both
> commented out (:: & 0.0.0.0) & I remembered
> seeing that in the error messages, so I
> thought that it must default to that unless
> otherwise entered. So, I bound it to this
> IP on the local area network & it works
> fine now with no error messages. Also, I
> forgot to mention before that I could ssh
> out but no one else could ssh in. Now
> that works too. Are there any security
> issues as far as binding sshd to this
> local IP? I never had to do that on the
> other 2 machines, but this is a newer
> version too, on this machine. Thanks.
>=20
>=20
> On Thu, 28 Feb 2002, Igor Roboul wrote:
>=20
> > Date: Thu, 28 Feb 2002 13:00:19 +0300
> > From: Igor Roboul <igorr@sysadm.stc>
> > Reply-To: igorr@speechpro.com
> > To: freebsd-questions@FreeBSD.ORG
> > Subject: Re: sshd bind to port 22 fails
> >
> > On Thu, Feb 28, 2002 at 03:39:06AM -0600, Denny White wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > Just reinstalled 4.5 on old machine to
> > > use for webserver. When boot finishes,
> > > get following message:
> > > sshd[136]: error: Bind to port 22 on ::
> > > failed: Address already in use.
> > > Same message for localhost.
> > > Checked /etc/services & port 22 is
> > > reserved for ssh. OpenSSL version is 0.9.6a
> > > OpenSSH version is 3.0.2 with patch
> > > openbsd28_3.0.2
> > > If I kill the process & then restart it,
> > > no error messages come up. Thanks
> > > for any help I can get on this.
> > Do you have some ssh port intsalled?
> > pkg_info | grep ssh
> >
> > --
> > Igor Roboul, System administrator at Speech Technology Center
> > http://www.speechpro.com http://www.speechpro.ru
> >
> > To Unsubscribe: send mail to majordomo@FreeBSD.org
> > with "unsubscribe freebsd-questions" in the body of the message
> >
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (FreeBSD)
> Comment: For info see http://www.gnupg.org
>=20
> iD8DBQE8fglBy0Ty5RZE55oRAipXAKC1t1o3SYlM6fguqfBhcq4kMaMGPQCgk3ql
> HBE9vmqKx1OkROPfcRKuqvQ=3D
> =3DjwVO
> -----END PGP SIGNATURE-----
>=20
>=20
>=20
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003401c1c06e$7c21ccd0$6400a8c0>