> Enable Secure Connections
> To enable secure connections to any host, you must enable ssh. Occasionally you need to connect to the Pano Manager VM using a secure connection. To do so, you must enable ssh on the host.
> Once you enable ssh, you can use non-command line utilities to make secure connections as outlined in Initiate Secure Connections. The vi editor isn’t the most intuitive editor, but you must use it to enable ssh. Once you enable ssh, you can use Notepad from that point forward.
> To enable ssh for an ESX host:

> 1. | Log on to the ESX host using the superuser (root) credentials:

> 2. | Execute the following commands from a shell:

> # vi /etc/ssh/sshd_config

> 3. | Find PermitRootLogin and change to Yes: press ESC, then press Insert.

> 4. | Save the changes: press ESC then type :wq!. If you make a mistake, you can press the ESC key and then type it :q! to quit vi without saving the file.

> 5. | Restart the ssh daemon:

> # service sshd restart

> To enable ssh for an ESXi host:

> 1. | Log on to the ESX host using the superuser (root) credentials:

> a. | At the console of the ESXi host, press ALT-F1 to access the console window.

> b. | In the console, type unsupported, then press Enter. If you typed in the command correctly, you the Tech Support Mode warning and a password prompt appear.

> c. | Type the password for the root login. You should then see the prompt of ~ #.

> d. | Edit the inetd.conf file:

> # vi /etc/inetd.conf

> e. | Find the line that begins with #ssh and remove the #. Then save the file. If you're new to using vi, then move the cursor down to #ssh line and then press the Insert key. Move the cursor over one space and then hit backspace to delete the #.

> 2. | Save the changes: press ESC then type :wq!. If you make a mistake, you can press the ESC key and then type it :q! to quit vi without saving the file.

> 3. | Do one of the following:

> • | (If you edited sshd_config) Restart the ssh daemon:

> # service sshd restart

> • | (If you edited inetd_config) Run the following command to determine the process ID for the inetd process:

> # ps | grep inetd

> The output of the inetd command will be something like 1299 1299 busybox inetd, and the process ID is 1299. Then, run kill -HUP process_id (kill -HUP 1299 in this example), and type inetd to start it again.
> You should now be able to access the host via SSH.

Did you find what you're looking for?
v2.5.1