Home of FTP client

Labtam-inc.com
sitemaphomecontact us

XSecurePro64 Version 1.0: 64bit X Server.

Date: 15 December 2004

XSecurePro64 is our latest X-Server based software addition. Labtamís X Server now provides the power of 64-bit processor and operating system technology to deliver a performance boost for high end CAD (Computer Aided Design), EDA (Electronic Design Automation) and graphics software users running on Linux and Unix servers.

XSecurePro64 includes 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.

XSecurePro64 is a powerful 64-bit software package, which provides a cost effective way to transform your PC into a powerful Secure X Window System workstation. To get started, all you need is the XSecurePro64 package and a 64-bit networked PC (AMD64, or IA64) and Windows XP/64 or Windows Server 2003 64-bit Edition. XSecurePro64 provides full support for multiple X applications, sophisticated window managers, including TWM, FVWM, Motif, Open Look and desktops like CDE, KDE etc.. You have a consistent graphical user interface for all your applications, and get more productivity with less effort. Learning to work in a multiple-computer environment has never been easier. It is the most economical way to bring the Unix and Linux world into your day to day environment.

The XSecurePro64 1.0/Release:20041126 Installation

To install the package, run the "setup.exe" file.

NOTES:

1) 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

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

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 prepared Forwarded ports. This way does not require especial 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 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
- the "COUNT_DUPES=1" line can be inserted into the "[NFSSERVER]" section of the xwp.ini file to disable counting of the same clients

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 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 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 "MyIP=?" line can be inserted into the "[network]" section of the xwp.ini file to allow the manual input of local IP address when XServer will be started
- this article is applicable when the XServer's PC has more than one IP address. In this case, XServer will prompt you to choose one of them. The "SocketCreate_INADDR=." line can be inserted in to the "[XDMCP]" section of the xwp.ini file to communicate with the XDMCP daemon via the IP address chosen. The "SocketCreate_INADDR=IP" assignment can be made to use the IP address to communicate with the XDMCP daemon (e.g. "SocketCreate_INADDR=192.168.0.30")

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. 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 can 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 an NFS server on another PC under Windows 9x if both PCs have Client/Server for Microsoft Networks installed.

5. 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".

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


Labtam Copyright © 1999 - 2003 LabtamTM Inc.