XSecurePro64 Version 1.1: 64bit X Server.

Date: May 9, 2005

Labtam is pleased to announce a new software release of X-server for Windows - XSecurePro64 Version 1.1. This is the first major release for the 2005 year.

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

Integrating the Microsoft Windows and X-Window System environments XSecurePro64 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.

NOTES on this release (PLEASE READ):

1) Use the "setup -wauto -s" command line (instead of "setup -auto") to start the "Silent Installation"!

2) The Windows NT LPR printer driver is manually installed by running the self-extracting archive file, "lprd.exe".
This file can be found in the directory with the uncompressed package distributive.

3) The Microsoft Windows 9x/ME/NT4/2K/XP NFS-Client can be installed by using the "Custom" installation mode only.

2. Startup:
- implemented the Telnet startup mode (as well as SSH-2)
- implemented the "-lxdn [<DisplayNumber>]" option to set up the "$(DISPLAYNUMBER)" macros (the "-lxdn" option means lookup running XServer)
In this case, the XServer must already have been started
- the "Log File" and "Exit after Timeout" settings are now available for Telnet and the Telnet/SSH mode

3. NFS-Server:
- refuses to close and shut down system if mounts are active
- supports the fixed or static port assignment
- made some changes concerning export names in the graphic interface
- some illegal symbols (such as '*',':','$','|') in file names can be used
(i.e. CATIA often tries to create file names with mentioned symbols)

4. Telnet and Telnet_SSH:
- Telnet can be started as a non-interactive session via the Startup facility (as well as SSH-2)
- implemented the "-mout [<outputfile>]" command-line option to provide a "readable" log-file for the session
- implemented the "-lxdn [<DisplayNumber>]" command-line option to set the "DISPLAY" session environment variable if a remote daemon supports it. (the "-lxdn" option means lookup running XServer)
- Telnet understands the local XServer's "DynamicDisplayNumber" mode and correctly looks for the running XServer

8. XServer:
- the XStartup and Telnet are invoked with the "-lxdn <DisplayNumber>" option (from the XServer's "Run" submenu)
- the last state of the "If Colormap Changed" setting in the XServer's "Options" submenu is saved for future sessions
- XServer/Multiple+RWM provides more convenient behavior of new windows including the XDMCP Logon window
- XServer/GLX/Mesa conforms to Mesa 6.2.1

10. XDK:
- provided support for X-Clients that use the GLX extension. Corresponding ".h" and ".lib"
files are added in the XDK set. Four sample GLX X-Clients are also added (as MS VC 6.0 projects with sources)

The following bugs have been fixed

1. Installation:
- the silent installation did not correctly use some saved installation parameters (i.e. the "Destination directory")

2. NFS-Server:
- fixed the bug when the number of inodes exceeds maximal value
- corrected the 'inremnode failed' message

3. Telnet and Telnet_SSH:
- more correct restarting to remove a possible "restart loop" and crash after the "password->"Disconnect" action

4. NFS-Client for MS Windows NT4/2000/XP:
- the "ls *" command line of MS SFU Korn Shell got caught in an endless loop of NFS requests to the NFS-Server
- processing of the Server List is more correct now
- a name of a mapped drive is shown correctly now

5. XSetup:
- removed some non-actual settings

6. XServer:
- XServer/Multiple+RWM incorrectly processed the disabling (from X-Client) of the shape region
- sometimes the XTRANS/accept() error code was processed incorrectly that led to unexpected error messages
- the composer key is accepted from the KeyPress moment (it was from the KeyRelease moment, that is not correct)
- reanimated the "Raise all windows" action in the XServer's menu
- fixed the possible incorrect processing of "shading"

Undocumented Features

1. Comsetup:
- implemented the "Auto-start XwpPeg Package Watcher" setting 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 the 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 an 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 the 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 the SSH-Client facility. Local-to-Remote: "21->192.168.136.41/21" (natural for FTP) and Remote-to-Local Forwarding: "4444

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 a 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 value of 8K
- 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 the 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 a 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 the "_MOTIF_WM_HINTS" windows property from processing
- the "DontCheckWM_SIZE_HINTSinc=1" line can be inserted into the "[XSERVERdeb]" section of the xwp.ini file to prevent the "WM_SIZE_HINTS" windows property from processing
- 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 a local IP address when the XServer is 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 a new Telnet_SSH 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. Lpd:
- printers on the remote MS Windows NT 4 hosts are unavailable from the local host under MS Windows NT 4.

2. 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

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

4. XServer:
- drawing partial arcs can be very slow
- the CDE/XDMCP of the HP-UX host can 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 can provide wrong screen re-displaying in some cases (e.g., Netscape scrolling)

Single User licenses are at $190.00 USD. Please visit the Software Pricing page for pricing on Multiple Licenses.

If at anytime you require any information or assistance please do not hesitate to e-mail us at: sales@Labtam-inc.com

Download and try XSecurePro64 software for FREE. (Demo version runs 60 minutes at a time.)

PLEASE NOTE:

The programs associated in this package may send and/or receive broadcast IP requests. Since such packets cannot cross the nearest firewall/gateway/router, please be sure that these IP requests are invisible from outside your network. We assume that such behavior cannot be considered as "Hacking" or "Trojan horse's action".