Home of x-server with SSH

Home of x-server with SSH
sitemaphomecontact us

X-SecurePro Version 7.4: X-Server with SSH.

Date: 25 September 2003

Labtam is pleased to announce a new software release named X-SecurePro Version 7.4.
This is the third major release for the 2003 year.

X-SecurePro is our latest X-Server based software addition. Not only does it contain the key X-Server elements, it now provides Encryption Security using the SSH standard from PC to host machine. X-SecurePro brings you maximum Security to a PC and a company Lan/Wan or Intranet/Internet.

Integrating the Microsoft Windows and X-Window System environments X-SecurePro is an inexpensive but powerful and effective way to transform a standard PC into a fully functional X-terminal.

Included in the package are the X-Window System, SSH, TCP/IP, FTP, TFTP, LPR, LPD, TELNET and NFS plus a whole lot more.

Everything that you need to run all your remote Unix and X applications is included.

New Features on this release include:

1. FTP :
- saving of settings was improved.

2. Telnet, Telnet_SSH :
- a review of runaway lines (as "old screens") was implemented.

3. NFS-Server :
- the ability to write files of more than 4GB size was implemented;
- the FL_CHRISLESLIE manual setting enables caching upon NFS writing;
- the FL_TZERAN manual setting enables changing the time zone difference.

4. NFS-Client for MS Windows NT4/2000/XP :
- the usage of SSH-2 Dynamic Forwarding was implemented. NFS-Client can access remote NFS-Servers through connections established with Telnet_SSH. Remote NFS-Servers must support TCP/IP access to portmapper, mountd and nfsd daemons;
- the NFS v.3 protocol support was implemented.

5. XServer :
- the "fonts.alias" file name as well as the "fonts.ali" one can be used in Fonts directories;
- the "BlockRWMtopmost" setting was implemented in the xwp.ini file;
- two sample keyboard mapping files, us_ps.kmf and us_ps2.kmf, were implemented for "very poor" keyboards;
- some other improvements were made.

6. X-Clients :
- the following standard X-Clients were added: xrdb, xwininfo, xprop, xfd, xset.

2. The following bugs have been fixed :

1. NFS-Server :
- extra socket listening was removed;
- NFS-Server crashed while processing an incorrect inode number.

2. NFS-Client for MS Windows NT4/2000/XP :
- some bugs were fixed.

3. XServer :
- an obstinate window took place when WM_CHANGE_STATE/IconicState was sent;
- XServer/MSB showed wrong visual's R/G/B masks;
- the Multi-monitors case was not recognized sometimes;
- some other corrections were made.

4. X-Clients :
- correct locale processing was implemented.

Undocumented Features

1. Comsetup :
- tthe "Auto-start XwpPeg Package Watcher" setting was implemented to provide the corresponding control of the XwpPeg facility.

2. Ftp :
- FTP connections (in the "non-Passive", default, mode) can be made through an existing SSH connection with prepared Forwarded ports.
This way does not require a special Telnet/SSH facility and can be used with any SSH-client which provides traditional Forwarding.
All settings are made manually.
Let's assume that you need to access the remote host (say, 192.168.136.41) via FTP, and SSH connection is made with the SSH daemon which is on another remote host (say, 192.168.136.34), and each host is directly accessible one from another (192.168.136.41 <-> 192.168.136.34).
Also, you should know two free ports on local machine (say, 21 and 4444) and one on the remote host connected via SSH (say, 5555 on 192.168.136.34).
At first, two forwardings must be made via SSH-Client facility.
Local-to-Remote: "21->192.168.136.41/21" (that in natural for FTP) and Remote-to-Local Forwarding: "4444<-5555".
After that you must add two lines to the "[FTP]" section in the "xwp.ini" file:
"IP_SSH_FWD=192.168.136.34" and "PORT_SSH_FWD=5555,4444" (i.e., specify the remote and local ports).
Now the FTP can be started. The "host" field must contain "localhost" or "127.0.0.1". The "non-Passive" mode must be set up (i.e. the "Passive Transfer" check box must be unchecked).
After "Connect" the FTP will be connected to "192.168.136.41" with no direct network access (only via SSH connection).

3. NFS-Server :
- the "AUTO_CHECK_ExPortmapper=1" line can be inserted into the "[NFSSERVER]" section of the xwp.ini file to check whether an external portmapper exists to use it;
- the "FL_MITXELENA=1" line can be inserted into the "[NFSSERVER]" section of the xwp.ini file to avoid directory permission problem for some NFS-Clients (e.g. of SCO UNIX 5.0.5).
This setting changes the default directory permission from 755 to 777.

4. NFS-Client for Windows NT4/2000/XP :
- the size of network packets can be changed instead of using the fixed 8K value;
- the full set of settings can be saved to a file and loaded from it later.
- the package is installed with the native Installation procedure (using the "Custom" installation mode) without necessity to deal with an additional separate executable;
- the links support was implemented (3 modes are available to do this).

5. Startup :
- to input any text into the command line before its executing, the "$(INPUTLIP)" macros can be used.
E.g., if the "Command" field contains the following line: "xterm -display $(INPUTLIP):0" then you will be prompted to input the text string (an IP address is assumed).
If you enter "1.2.3.4", then the resulting command line will be: xterm -display 1.2.3.4:0 .
- the "Telnet_SSH/SSH2 (SSH-2 Client)" Start Method is similar to other methods except for the ending of a command line. The usage of the "&" sign is not recommended because of unstable results.
E.g., if you need to start "xterm" remotely, then the "xterm" command line is preferable (and the "xterm&" line is not recommended).

6. XServer :
- the "DontUse_MOTIF_WM_HINTS=1" line can be inserted into the "[XSERVERdeb]" section of the xwp.ini file to prevent from processing the "_MOTIF_WM_HINTS" windows property;
- the "DontCheckWM_SIZE_HINTSinc=1" line can be inserted into the "[XSERVERdeb]" section of the xwp.ini file to prevent from processing the "WM_SIZE_HINTS" windows property;
- the "ILikeLINUX=1" line can be inserted into the "[XSETUP]" section of the xwp.ini file to set up the LINUX's console keyboard mapping;
- the "MyIP=?" line can be inserted into the "[network]" section of the xwp.ini file to allow the manual input of local IP address when the XServer will be started.

7. Telnet_SSH/SSH2 :
- to control the session's restart/completion, the "ExitOnDisconnect=..." line must be added to the "[Telnet]" section of the "xwp.ini" file. The "ExitOnDisconnect=..." setting provides the following modes:
- ExitOnDisconnect=1 - to suppress the start of the new telnet_s session;
- ExitOnDisconnect=2 - to suppress the "Connection lost" message (only to write it into the telnet_s.out file);
- ExitOnDisconnect=3 - to suppress the "...open forwarded connections..." message (only to write it into the telnet_s.out file).

Known problems

1. Uninstallation :
- the uninstallation procedure does not remove components which were installed in additional (non-first) installation sessions. Such additional components should be removed manually.

2. Lpd :
- printers on the remote MS Windows NT 4 hosts are unavailable from the local host under MS Windows NT 4 .

3. NFS-Server :
- there may be problems on PCs with several IP addresses;
- some Linux NFS-3 Clients may issue an error message (about the wrong file ID) because of wrong packets unwrapping in the Linux's "nfs3xdr.c" module.

4. NFS-Client for Windows 9x :
- PC must be restarted after you change the license file, "xwpdllid.dll";
- can fail when connecting to NFS-Server on another PC under Windows 9x if both PCs have Client/Server for Microsoft Networks installed.

5. XServer :
- drawing partial arcs may be very slow ;
- the CDE/XDMCP of the HP-UX host may provide infinite waiting for connection. To avoid this, the new "HP" fonts alias directory should be included into the XServer FontPath;
- the "Forced Backing Store" setting may provide wrong screen re-displaying in some cases (e.g., Netscape scrolling).

Home | Product | Download | Order Now | Upgrade | Support | Pricing | Company Profile | Contact Us


Labtam Copyright 1999 - 2003 LabtamTM Inc.