OS2.GURU - Secure PMVNC with SSHOS2.GURU - Secure PMVNC with SSH

Welcome to eComStation.RU site!

Select your language: Russian English Deutch Spanish Italian Portuguese Czech Polish French

Frequently asked questions and answers:


+7-981-8529467 (Санкт-Петербург)
ru · en · de · es · it · pt · cz · pl · fr
OS/2 is a greatly different operating system for PC (ArcaOS, eComStation, IBM OS/2 Warp)
Applications, news, reviews, support of users, hardware, questions and answers.
      What is OS/2?NewsInstallUpdateUsageFutureCommunityBuy    
(Map of the site)

Report: OS/2 compatible hardware




For developer:

(Пайпы программ)





(Барьеры и решения)


(Применение в науке, лаборатории, ..)



New eComStation:


(Ссылки на другие сайты)

(Картинка дня)

OS/2 artefacts:


Upgrade ArcaOS to NeoWPS level

  • Install original PNG icons drawed by designer, specialized at OS/2 adornation.
  • Install eSchemes 2018 to change colors and buttons on desktop.

Secure PMVNC with SSH

TITLE: Secure PMVNC with SSH

DATE: 2004-11-01 10:38:13

AUTHOR: Eugene Romanenko

Please use online translator
go to http://translate.google.com
and request the translation of http://en.ecomstation./showarticle.php?id=119
to your language

VNC stands for Virtual Network Computing. It is remote control software which allows you to view and interact with one computer (the "server") using a simple program (the "viewer") on another computer anywhere on the Internet. The two computers don't even have to be the same type, so for example you can use VNC to view an office eComStation machine on your Windows PC at home. VNC is freely and publicly available and is in widespread active use by millions throughout industry, academia and privately.

To establish secure VNC connection follow this instructions:

On server, you will need 2 packages (both made by nickk, both can be downloaded from Hobbes):

  1. Install Security/2 package: just execute install.exe and follow instructions. Select "No local logon" during install. Reboot system.

  2. Change root password using "user" command. Type at cmd prompt: 'user -c root' - it will ask about new password.

  3. Install OpenSSH: unpack distributive into, for example, 'c:\ssh' directory. Copy 'ssh' directory from c:\ssh\etc to your ETC path.

  4. Generate server keys: execute command in c:\ssh:
    ssh-keygen -t dsa -f %ETC%\ssh\ssh_host_dsa_key -N ""

  5. Run sshd. (Use -d switch for debugging, if all works ok - run sshd.exe detached).

  6. Also you need change PMVNC settings to allow accepting connections from localhost and, optionally, disallow any other connection. These settings not present in properties dialog, but may be changed by editing profile. PMVNC store settings in User profile file under the ER_PMVNCD key. Use INI-editor or regedit2 to alter these options. Options are string type, even if represents numeric values. Add "AllowLoopback" string type option under ER_PMVNCD key, and set value to "1". If you want use only secure connections with VNC, then add "LoopbackOnly" option with value "1". For more information about these options see pmvnc.html from PMVNC distributive, "Hidden settings" section.

  7. Restart PMVNC after changing profile data.

On client:

  1. Unpack ssh distributive into, for example, 'c:\ssh' directory.

  2. Execute command in c:\ssh:

    ssh -l root -2 -N -L 5900: server_host

    which means:

    connect as user "root" to server_host and also listen on local port 5900, all connections to local port 5900 route to port 5900 of server host using secure tunnel.
    On first connect you may see message
    The authenticity of host '...' can't be established.
    DSA key fingerprint is ....
    Are you sure you want to continue connecting (yes/no)?
    Type "yes".

    Then ssh will ask about password. Type password which you set at step 2 of server setup.

    SSH session will be started.

  3. Execute Vncviewer. It will ask about vncserver location. Type and connect.

    You may run VNC session several times while SSH session is up. To close SSH session press Ctrl-C in SSH window.


  • Client setup procedure is same on any operating system, just use ssh distibution for OS which you use.
  • SSH switch -N needed to workaround OpenSSH/2 problem - if cmd.exe used as user shell, sshd will echo client input, and binary protocols (like VNC) will not work. -N switch disables execution of user shell on server.
  • SSH can compress traffic (useful for modem connections). Use -C option for ssh to enable compression.

Additional information: