Novell ZENWORKS LINUX MANAGEMENT 7.3 IR2, Руководство администратора

Страница: 669 / 684

Establishing SSH Tunneling
J
669
no
vd
ocx
(e
n)
7 Ja
nua
ry 201
0
J
Establishing SSH Tunneling
If you are using Remote Management over a network that is not secure, the data between the
Remote Management Viewer running on the management console and the Remote Management
Agent on the managed device is unencrypted and could be viewed by someone with access to the
intervening network. You should tunnel your Remote Management sessions through a secure
channel such as SSH.
Š
Section J.1, “SSH Tunneling between a Linux Management Console and a Linux Managed
Device,” on page 669
Š Section J.2, “SSH Tunneling between a Windows Management Console and a Linux Managed
Device,” on page 670
Š
Section J.3, “Compression,” on page 671
J.1 SSH Tunneling between a Linux Management
Console and a Linux Managed Device
If you are using Linux, SSH clients and servers are freely available on the internet. The SSH client
and server RPMs can be downloaded from the
OpenSSH site. (http://www.openssh.com) .
J.1.1 Basic Use
SSH provides you with a “Secure SHell” to the remote device. All traffic is encrypted between the
two devices using public key encryption techniques, making it very difficult for anyone else to spy
on it. When SSH is installed, you could connect to a managed device from elsewhere simply by
running the SSH client. For example, if you want to connect to a managed device called “work.” you
use the following command:
ssh work
You are then prompted for the password of your account on the managed device and you are logged
in, just like a telnet session, but safer. You can also request that it listens on a particular port on your
local management console and forwards that down the secure connection to a port on a managed
device at the other end. To do this, use the following command:
ssh -L x:work:y work
This starts an SSH connection to a device named “work” and also listen on port x on the local
management console, and forwards any connections there to port y on “work.”
Remote Management uses two ports on the managed device. By default, the Remote Control service
listens on port 5950 and the Remote Login service listens on port 5951. If you want to enable SSH
tunneling for Remote Control, you need to forward Remote Management data from a port on your
local management console to 5950 of managed device.
Similarly, you should forward data to 5951 if you want to tunnel Remote Login:
Š
If you are running Remote Control service on “work” on 5950 and you want a secure
connection to it from your local management console, you can start the SSH session using: