--9jxsPFA5p3P2qPhR
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Tue, Dec 04, 2001 at 08:15:38PM -0700, Kevin Brown wrote:
> Hmmm... So were you trying to SSH to the external IP? If so, what does =
your
> sshd2_config or sshd_config file have for the IP it is to bind to (if any=
).=20
> What default permissions did it come with for who could log in. I'm used=
to ssh
> from www.ssh.com that comes with it wide open, including letting root log=
in
> remotely (not good :( ).
Yep. Both configuration files don't have an IP to bind to, so they bind to
the only IP avaialable: the outside IP. Config files haven't changed from
the defaults provided by the OpenSSH consortium.
> Also if it was SSH I'm used to it bouncing me back to the password prompt=
over
> and over when I'm not allowed in. That's its way of hiding what is wrong=
with
> the connection (whether it's a bad password or your IP isn't allowed to
> connect). Again this is with SSHd running standalone.
Yeah. I tried running both sshd and ssh with the debug flags, but those only
debug the actual communications protocol -- no error messages show up, only
the standard message for authentication failures.
> Since /etc/hosts.{deny,allow} are both empty that might not be causing a
> problem, but wouldn't discount inetd as the troublemaker.
Point taken, but I've not had a problem running it through inetd on my own
local server (tank.dyndns.org). Config files are identical between the two,
so it has to be something else somewhere...
--=20
Thomas "Mondoshawan" Tate
phoenix@psy.ed.asu.edu
http://tank.dyndns.org
--9jxsPFA5p3P2qPhR
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see
http://www.gnupg.org
iD8DBQE8DZQIYp5mUsPGjjwRAtE9AJ9mK6NdEhzXnxEXYq/9Y7B4WRaoPACfRcJW
xmpG+IHdUFBQHJGlTlwiu84=
=6/jR
-----END PGP SIGNATURE-----
--9jxsPFA5p3P2qPhR--
(text/plain)