ssh 2.1.1p1 can't connect; ssh 1.2.3 can

[Gert Doering]

Hi,

On Tue, Jun 20, 2000 at 11:34:06AM -0400, Paul D. Smith wrote:
>   dm> An strace of the client and a tcpdump of a failed connection would
>   dm> help.
> 
> Ugh.  OK, I'm a bit confused.  I couldn't truss it because ssh was
> setuid root, so I made a copy that wasn't.  That copy worked!
> 
> It's apparently something about the privileged ports?, because if I run
> the setuid version with -P, then that works as well.
> 
> _But_, I don't see how it can be a firewall issue, at least not on my
> side, since I can use a privileged port to access my home system (I
> don't need -P for that).  That's what threw me :-/.

Sounds *very* much like a firewall issue - somewhere on the way in
between.  Something of "privileged ports are evil, forbid, forbid!"
without actually understanding things like ssh...

gert
-- 
USENET is *not* the non-clickable part of WWW!
                                                           //www.muc.de/~gert/
Gert Doering - Munich, Germany                             gert at greenie.muc.de
fax: +49-89-35655025                        gert.doering at physik.tu-muenchen.de