|
|||||||||||
|
RE: OPENSSH 3.4p1-3 on AIX 4.3.3
From: Wilson, Richard E <richard.wilson(at)eds.com>
Date: Thu Feb 13 2003 - 17:39:59 EST
I ran into a similar issue with a combination of Sun systems running SSH 1.2.27 and Linux systems running a variety of recent OpenSSH versions. After some research I found that SSH v1 expects a low number (0-1024) port for such connections the logic being that only a privileged process can allocate such ports (used to be true in the early days of UNIX, pretty meaningless now though). OpenSSH doesn't always use one of these "privileged" ports when it connects. It nearly drove me crazy because the behavior was not consistent. I sent this out to the mailing list asking for solutions and never got an answer; I solved my issues by using the ssh-agent process which apparently doesn't look at the ports. Hope this helps,
Richard Wilson
I try to substitute a normal rsh/rlogin environment to a ssh-environment on some AIX 4.3.3 machines. For this environment I want to establish a PasswordAuthentication (with all his security risks) and, if present, a secure login without password using .shosts. Here starts the problem. There is no way, as far as I tested, to use a .shosts file. In any case this file will be ignored, regardless of modes, ownerships or user.
There a two ways of loging into a machine: 1) A normal ssh to a machine and
i have to give the password.
With RhostsAuthentication, I get the only worthful message into the debug message: debug1: Rhosts Authentication disabled, originating port 33754 not trusted. How can the server machine trust a non-privileged port, that is choosen randomly?? What went wrong here? regards Alf Nicolaysen Received on Thu Feb 13 18:47:49 2003 This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:02:54 EDT |
||||||||||
|
|||||||||||