XSecurePro V8.3 - Help Manual - Labtam Inc · Telnet/SSH2 as SOCKS4 Proxy Details of a Session Telnet_SSH Menu Options The Help Menu The Commands Menu The Edit Menu The View Menu

This page is a part of XSecurePro online Help Manual. X-SecurePro is X-Server for windows by Labtam bringing your PC to Unix and X-Windows. Seamless Secure integration from PC to Unix and X-Window System. Bringing Maximum Security while still finding all of the standard access of X11, TCP/IP, FTP, TFTP, LPR, TELNET, NFS and SSH. Visit Home of X Server for windows

for more information.

1. About This Manual2. Introducing to XSecurePro

What is in XSecurePro

3. The XSecurePro RequirementsPC Hardware & Software RequirementsHost Requirements

4. Installing XSecureProRunning Setup

Extracting Package Installation FilesRunning SetupThe Silent Installation ModeInstallation NotesExporting XServer's Settings During Installation

Running UNINSTALLUpgrading XSecureProMulti-user Installation

5. The XSecurePro DatabaseKeyboard Definition FilesThe Color Definitions File

6. Configuring XSecureProUsing ComSetup

The Communication Setup TabThe All Trace Tab

The Network trace BoxThe XwpPeg Utility

The TCP/IP Retransmission Timeout ParametersUsing XSettings

The Startup TabThe Window Mode ListThe Use XDMCP Box

The Mouse_Keyboard TabThe Mouse Settings BoxThe Keyboard Settings Box

The Screen TabThe Screen Settings BoxThe GLX Extension Box

The Font Control TabThe Advanced Tab

The Access Control BoxSome Hints about Authorization and Host Access Policy

The Troubleshooting TabThe Trace Tab

The Network trace BoxThe Run Box

The XServer TabThe NFS-Server service Tab

Installing the NFS-Server ServiceUninstalling the NFS-Server ServiceUsing the NFS-Server serviceConfiguring the NFS-Server ServiceThe Properties Box

http://www.labtam-inc.com/

The Windows Firewall Box

7. Telnet_SSHStarting and Terminating Telnet_SSH

Starting a Telnet SessionStarting an SSH SessionExample of Initiating a Telnet Session via SSHTerminating a SessionTelnet/SSH2 as SOCKS4 Proxy

Details of a SessionTelnet_SSH Menu Options

The Help MenuThe Commands MenuThe Edit MenuThe View MenuThe Options MenuThe Settings OptionThe Keys TabThe Type TabThe Text TabThe Text Tab for the XTERM TypeThe User Defined Tab

The Logging TabThe ExtScreen Tab

The Keyboard Mapping OptionList Assigned FunctionsEdit function

The Forwarding OptionThe Port Forwarding BoxThe X Forwarding BoxThe Save FWD Settings Option

Terminal Emulation in Telnet_SSHRunning Telnet_SSH with Command Line ParametersThe "[TELNET]" Section of the ini-file

8. FTP/SFTP/NFSBrowserStarting and Terminating the FTP ProgramThe Main FTP WindowThe Server MenuThe Options MenuPerforming File TransferConnecting to the FTP Server

Example of initiating the FTP session via SSHDisconnecting from the FTP ServerChanging to a User NameProfileTransfer Options

Setting Transfer OptionsOperations with Files

Copying FilesAppending One File to AnotherRenaming FilesDeleting FilesRe-getting or Re-putting Files Transferred PartiallyPreviewing Files

Operations with DirectoriesMaking DirectoriesRemoving DirectoriesCopying Directories

The Quote TabDetermining Commands the FTP Server Supports

Getting Help on a CommandSending a String to the FTP Server

Running FTP with Command Line ParametersThe "[FTP]" Section of the ini-file

9. TFTPStarting and Terminating the TFTP ProgramTFTP Menu Options

The Settings ItemThe PutFiles ItemThe GetFiles Item

10. PingStarting and Terminating the Ping UtilityPing Menu Options

The Settings ItemThe Start ItemThe Stop Item

11. LPR - Remote Printing ProgramStarting and Terminating the LPR ProgramEntering LPR Info

OptionsPrinting FilesConfiguring a Network Printer

Adding a Network PrinterDeleting a Network Printer

Canceling OutputThe lpr.inf File

12. LPD - Network Print ServerStarting and Terminating the LPD ProgramConfiguring the Network Print Server

The Available Printers BoxAdding a New Network PrinterChanging Printer SettingsRemoving a PrinterThe Queue Directory BoxThe User Access Box

The Printers StatusThe "[LPDAEMON]" Section of the ini-file

13. StartupStarting and Terminating Startup

Running a Startup FileExecuting a Command/File

Entering Startup InfoThe Start Method BoxThe Login BoxThe Command BoxExample of Initiating the REXEC Session via SSH

Startup JobsSaving a JobOpening a Job

Running Startup with Command Line ParametersThe "[Startup]" Section of the ini-file

14. Network File System Server (NFS-Server)Starting and Terminating NFS-Server

Checking Access to Exported DirectoriesConfiguring NFS-Server

The Export Directories BoxThe Name Conversion Box

Changing the NFS User Access Table

Adding a UserRemoving a UserThe Status Report Window

RestrictionsRunning NFS-Server with Command Line ParametersThe "[NFSSERVER]" Section of the ini-file

15. Network File System Client (NFS-Client)NFS-Client Settings under MS Windows 9x/ME

Removing NFS-ClientThe Authentication TabBrowsing Network for NFS ServersThe FileNames TabUnix-to-Windows File Name ConvertingWindows-to-Unix File Name ConvertingThe Network TabThe Network Settings BoxThe Cache Settings BoxThe Servers TabThe About Tab

Mounting an NFS File System under MS Windows 9x/MEMounting in Network NeighbourhoodDisconnecting a Currently Mounted NFS

NFS-Client Settings under MS Windows NT4/2000/XPThe NFS Servers TabEditing Remote NFS Server ParametersThe Authentication TabThe Authentication Type BoxUID/GID Used for MountingBrowsing Network for NFS ServersUsing the NET USE UtilityThe Permissions TabThe Unix access permissions for new objects BoxThe Network TabThe Network Settings BoxThe Network Caching BoxThe Name Converting TabUnix-to-Windows File Name ConvertingWindows-to-Unix File Name ConvertingThe Advanced TabThe About Tab

Mounting an NFS File System under MS Windows NT4/2000/XPMounting a network drive (NFS File System)Dismounting a network drive (NFS File System)

Installing NFS-Client under MS Windows NT4/2000/XPInstalling NFS-ClientRemoving NFS-Client

16. Using XServerStarting XServerInitiating Remote Login Sessions

The XDMCP MethodThe Telnet MethodREXEC, RSH and RLOGIN Methods

Terminating XServerA Note on Copy and PasteSingle Window Mode

Example of Initiating a Login Session by Using REXEC to Start xtermFull Screen Mode

Example of Initiating a Login Session by Using XDMCPMultiple Window Mode

Example of Initiating a Login Session by Using Telnet to Start xtermThe X Client's Menu

Multiple+RemoteWM ModeExample of Initiating the REXEC Session to Start xterm via SSHExample of Initiating a Login Session by Using Telnet to Start xterm via SSH

XServer CommandsThe Edit MenuThe Options MenuThe Macros MenuThe Run MenuOther Commands on the X Client's Menu

Running XServer with Command Line ParametersRunning Several X-sessionsUsing LBX

About LBXAbout lbxproxyRunning xterm from Telnet_SSHRunning xterm from StartupAbout xfindproxyAbout proxymngrProxy Manager Config-FileProxy Manager Details

The "[XSETUP]" Section of the ini-file

17. Font ControlFont Path

Font DirectoryFont ServerEditing Font PathFont ServiceUnderstanding the Font List

Pseudo FontsPseudo Fonts DirectoryCreating Pseudo FontViewing Pseudo FontDeleting Pseudo FontCompiling Pseudo Font to the X11 formatCreating Pseudo Fonts on X Client RequestEnabling to Use

Restriction of Windows Fonts Accessibility

18. X Development KitIntroducing the XSecurePro X Development Kit

About the XSecurePro XDKInstalling the XSecurePro XDK

What is in the XSecurePro XDKDLL FilesLIB FilesResource FilesProject TemplateSample ProjectsX11 Locale Files (International Support)Local X and Motif Clients

Developing Local X Client ApplicationsX Window Application Development OverviewBuilding an X Window ApplicationRunning an X Window Application on Microsoft Windows

Porting X Window Applications to XSecureProMemory ManagementThe gethostname FunctionSetting the Locale for an X Client

Accepting Localized InputRestrictions on Developing X Applications with XDK

Appendix A Keyboard Mapping File FormatKeyboard Mapping File FormatThe KEYS SectionThe COMPOSERS_XKK SectionAvailable Keyboard Mapping Files

Appendix B Description of Terminal CapabilitiesDescription of Terminal CapabilitiesTerminal Parameter Settings

Appendix C TroubleshootingFTPNFS-ServerXServer & XSettings & Font Service

Appendix D The PingNFS UtilityAppendix E The NFSprobe Utility

The NFSprobe UtilityThe RPC_Info CommandThe Time CommandThe Diagnose CommandThe Network File System Checking WindowThe NFStrace Utility

Appendix F Local X and Motif ClientsLocal X and Motif Clients

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

Copyright © 1999 - 2009 LabtamTM Inc.

http://www.labtam-inc.com/index.php

http://www.labtam-inc.com/index.php?act=products

http://www.labtam-inc.com/index.php?act=download

http://www.labtam-inc.com/index.php?act=purchase

http://www.labtam-inc.com/index.php?act=upgrade

http://www.labtam-inc.com/index.php?act=support

http://www.labtam-inc.com/index.php?act=pricing

http://www.labtam-inc.com/index.php?act=companyinfo





content | next >

1. About This Manual

This User's Manual describes how to install, configure and use the XSecurePro package on a 32-bit IBM PC or compatible personal computer running one of the following operating systems: MS Windows 9x/ME/NT4/2K/2K3/XP/Vista. A small volume of the manual reflects simplicity of using this software tool created nevertheless on the basis of up-to-date information technologies.

The following items will be covered:

● Purpose and composition of XSecurePro● Hardware & Software requirements of XSecurePro● Installation procedure for XSecurePro● XSecurePro database composition● Configuring XSecurePro● XSecurePro working sessions.

content | next >
















< previous | content | next >

2. Introducing to XSecurePro

XSecurePro is a complicated product for integrating the Microsoft Windows and TCP/IP network environments. XSecurePro is an inexpensive but effective way to transform a standard PC running under MS Windows (9x/ME/NT4/2K/2K3/XP/Vista) into a multi-function terminal. Being based on the TCP/IP open standards, the package integrates a PC into an interoperable computer network. The network of dissimilar computers and operating systems becomes perfectly transparent to you. XSecurePro enables you to work on your PC's screen with several applications executed simultaneously on various network nodes. As a result, a heterogeneous network appears to you as a unified large computer system arranged directly on your desktop.

By using the industry standard Secure Shell (SSH1/SSH2) protocol for remote logins, intended to provide secure encrypted communications between two untrusted hosts over an insecure network, the package brings you typical remote system administrating, file transferring, and access to corporate resources over the Internet. With its SSH1/SSH2 features support, the package brings Security to your PCs, company LAN/WAN, or Intranet.

















2. Introducing to XSecurePro < previous | content | next >

What is in XSecurePro

XSecurePro is an integrated and powerful 32-bit software tool consisting of the following functional parts:

Telnet_SSH virtual terminal emulator

Telnet_SSH is a communications and terminal emulation program for logging into remote machine and executing commands in a remote machine. It allows you to connect to and communicate with hosts that support:

● The Telnet protocol and run a Telnet service over an insecure channel

● The Secure Shell protocol, SSH1/SSH2, and run an SSH1/SSH2 service to provide strong authentication and secure encrypted communications between two untrusted hosts over an insecure network. X11 connections and arbitrary TCP/IP ports can also be forwarded over the secure channel. TCP forwarding features make it possible to communicate across a firewall. The "Dynamic Port Forwarding" feature (an extension of the standard SSH1/SSH2 protocols for inter-task requests in multi-task environment) allows you to start other package's utilities (e.g., FTP) through established SSH1/SSH2 connections without direct access to remote hosts.

Telnet_SSH includes the following features:

● Compatibility with SSH protocol version 1.5 (a SSH1-client)

● Ciphers (for the SSH1-client): 3DES, Blowfish, DES, RC4

● Compatibility with SSH 2.0 protocol (a SSH2-client based on OpenSSH 3.4)

● Ciphers (for the SSH2-client): 3DES, Blowfish, CAST128, ARCFOUR, AES128, AES192, AES256-cbc

● Password authentication

● RSA authentication

● Compression support (with auto-selection of the compression mode supported by both sides)

● Connection forwarding, including full support for X-protocol connection forwarding

● "Dynamic Port Forwarding" that provides other tasks on the same PC with requested port forwarding.

While you are using Telnet_SSH, you can:

● Initiate and control remote login sessions in the Telnet or SSH1/SSH2 modes


● Set some options for particular implementations of Telnet_SSH

● Change fonts of text displayed in the Telnet_SSH window

● Select a terminal emulation mode in the Telnet_SSH session.

The Telnet_SSH program can emulate XTERM, AT386, ANSI, VT52, VT100, VT125, VT220 and VT240 terminals for character-mode applications. Advanced users can edit the terminal capabilities description file to suit to the special environment.

By using the Keyboard Mapping option (i.e. keymap editor invoking), you can load, change (re-define keys and create a new keyboard layout), and save any keyboard definition file.

The FTP Program

The FTP program is a client implementation (i.e. a user interface) of standard File Transfer Protocol. FTP allows you to transfer both text and binary files and directories between your PC and remote computers running the server implementation of File Transfer Protocol (on multiple server platforms) over the Internet and intranets.

By using the FTP program, you can:

● Set up parameters and modes for operations

● Navigate through directory structures on your PC or remote FTP servers

● Make/Remove a local/remote directory

● Select directories and files in a local/remote directory

● Copy/Rename/Delete selected local/remote files and directories

● Transfer selected files and directories between two remote FTP servers

● View a local/remote file (in Notepad)

● Append a file from your PC to a file on a remote FTP server

● Execute FTP commands on a remote FTP server.

FTP operations may be done either by direct insecure access to a remote host or through one of the established SSH1/SSH2 protocol connections as well. You can access resources you need from behind your corporate firewalls. Also, FTP supports the SFTP mode.

While you are connected, you can perform a number of tasks (commands) on the remote computer (FTP server) by using its various options.

The TFTP program

The TFTP program is a client implementation (i.e. a user interface) of standard Trivial File Transfer Protocol. TFTP allows you to transfer both text and binary files between your PC and a remote computer running the server implementation of Trivial File Transfer Protocol.

LPR - Remote Printing Program

LPR is a client implementation program that allows you to access printers attached to remote computers on your TCP/IP-network. The computers must support the Berkeley Line Printer protocol.

While using LPR, you can:

● Enter data required to connect to a remote computer and to choose a target printer

● Specify print job options (a number of copies, titles and banner pages, a file type)

● Print one or more files from your PC on the remote printer

● View print jobs in the queue, remove jobs from the queue.

LPD - Network Print Server

LPD is a Network Print Server (daemon) that provides access to your local (attached to your PC) and Microsoft-network-accessible printers from remote computers across TCP/IP network. The remote computers must use the print program that supports the Berkeley Line Printer protocol (lpr client).

While using LPD, you can:

● Change the printer list and printer parameters (add/remove a network printer, edit settings of network printers)

● Enable or disable printing files from remote computers

● Specify the list of users who can print files on your networked printers.

LPD provides German and/or French messages and text labels under the corresponding national version of MS Windows.

The Ping program

You can test that the TCP/IP transport is installed and configured correctly by using the Ping utility. Ping can help you isolate network hardware problems and incompatible configurations by allowing you to verify a physical connection to a remote host.

To ping remote hosts, you can select the standard MS Windows ICMP interface protocol or the TCP protocol.

You can choose the IPv4 mode or the IPv6 mode for pinging remote hosts (for both the ICMP and TCP protocols).

Ping can automatically choose the protocol (ICMP or TCP) and the mode (IPv4 or IPv6) for pinging remote hosts.

You can use the '*' wild card symbol in the IP address to scan up to 256 hosts in your LAN to see at once which hosts are alive.

The Startup Program

Startup is a program for automating host access with using the REXEC, RSH, RLOGIN, or Telnet protocol. REXEC and Telnet operations may be done either by direct access to a remote host or through one of the established SSH1/SSH2 protocol connections as well.

By using the Startup program, you can:

● Enter one or more commands in a single line and execute them on a host

● Run a local startup file (with a sequence of executable commands) on a host

● Enter a command line to run a local executable file (e.g., telnet, local X clients, etc) and execute it on your PC

● Create/save/select/remove/open/execute startup jobs.

Startup job is a task with a certain set of parameters (start method, login information, command line, settings). You can create a job (i.e. store current parameters under a certain name). A job may be launched by clicking on its icon.

Network File System Server

NFS-Server is a network file server that supports the NFS protocol version 3. It has a multi-threaded code developed for the Win32 environment and is designed to work with the built-in MS Windows TCP/IP-32 protocol stack.

The main feature of NFS-Server is to provide access to hard disk space and files residing on your PC to users working on other network nodes under different operating systems (with NFS client support and TCP/IP).

NFS-Server can be installed under one of the MS Windows operating systems (9x/ME/NT4/2K/2K3/XP/Vista) to share your local drives and folders with other networked users, no matter which operating system they are running on their workstations. Only an NFS client is required on that system for users to mount your disks as part of their system.

By using NFS-Server, you can:

● Add new directories to the Exported Directories Table or remove them from it

● Add new remote users to the NFS User Access Table or remove them from it for any selected exported path

● Change access rights for remote users defined in the NFS User Access Table (i.e. specify each user's read and write permission to your exported path)

● View status information on those directories of your PC that remote users are currently accessing (i.e. active NFS clients' connections)

● Suspend/resume current activity of NFS-Server.

NFS-Server provides German and/or French messages and text labels under the corresponding

national version of MS Windows.

Network File System Server as MS Windows Service

The functionality and settings of the NFS-Server service are just the same as of NFS-Server itself. Additionally, you can control the behavior of NFS-Server as a MS Windows service.

You can:

● Install and uinistall the NFS-Server service

● Configure startup options and make settings for the NFS-Server service (i.e., how it is started and how it will communicate with NFS clients)

● Add/remove the NFS-Server service definition to/from Windows Firewall to allow (or not) the service to be accessed from local or remote NFS clients' computers.

● Manage the service session: start, stop, pause, resume, or disable the service.

Network File System Client

NFS-Client is a program running under the MS Windows operating system in order to mount one or more shared network resources from one or more NFS servers and to share access to files and directories with other PCs and UNIX users across the network. A shared network resource is any folder that the administrator makes available to be mounted and its subdirectories.

NFS-Client does not turn your PC into a fully qualified file server. Instead, it allows a simple access to folders and files for a limited number of systems on the network.

NFS-Client has a multi-threaded code developed for the Win32 environment and is designed to work with the built-in MS Windows TCP/IP-32 protocol stack. NFS-Client is able to operate in multi-home environment (i.e. with non-single IP address) with no limitations.

NFS-Client can be installed under one of the MS Windows operating systems (9x/ME/NT4/2K/2K3/XP/Vista/XP-x64) to enable you to benefit from network NFS server services. With the help of NFS-Client you can mount disks and folders from network, no matter under which operating system they reside, and make them as part of your familiar local desktop environment.

NFS-Client for MS Windows NT4/2K/2K3/XP/Vista/XP-x64 can perform NFS operations either by direct insecure access to a remote host or through one of the established SSH2 protocol connections as well. You can access resources you need from behind your corporate firewalls.

XServer

The XSecurePro's XServer is a program that emulates the X terminal on your PC. It is the X-server implementation of the X11R6.6 release of the X Window System. XServer allows you to run one or more X Window based client applications (X clients) that are resident on host computers. The host can be any computer that supports the X protocol across your TCP/IP network.

X client applications can be displayed in individual windows, as multiple windows contained in a single XServer's window, or in a full-screen mode outside the Microsoft Windows graphical environment. The first two methods include functions to copy and paste data between X clients and the Microsoft Windows clipboard.

While running XServer, you can initiate a login session by using Telnet, XDMCP, or Startup (REXEC, RSH, RLOGIN) methods. You can launch several X-sessions that will be running simultaneously each with its own settings. XServer can work on multi-monitors PCs.

While running XServer, you can launch any local X client supplied with the package.

The macro options of XServer let you create macro-files to remember sequences of your keystrokes. Then, whenever you want, you can play back these keystroke macros in a target X-application window by choosing an appropriate macro-file.

XServer provides German and/or French messages and text labels under the corresponding national version of MS Windows.

XServer supports the following X Extensions:

● Extended-Visual-Information● XinputExtension● MIT-SUNDRY-NONSTANDARD● SHAPE● XTEST● XC-MISC● XC-APPGROUP● GLX for OpenGL● RENDER● SECURITY● LBX

XServer can connect to a remote LbxLoxy service (a Low Band Width X proxy) either by direct access to a remote host or through one of the established SSH1/SSH2 protocol connections as well.

XServer can use MESA (6.2.1), an open-source implementation of the OpenGL specification.

Font Service

Fonts installed on your system can be used by any graphical X Window System application. A remote font server is started automatically with your graphical environment, and then all fonts installed on your system are automatically available to all of your X Window System applications. X clients request character information from the font server, which can return data in various formats, ensuring high quality display of a variety of font styles and sizes.

You can use your familiar host-based X fonts via XSecurePro's XFontset Service. The XFontset Service utility provides:

● Rasterized fonts with outline data to all X applications

● Wide range of local X fonts (the standard font sets supplied by MIT along with X11 R6)

● Support for different locale 16-bits fonts including Chinese, Japanese, or Korean fonts, etc.

● Use of uncompressed PCF, SNF, and BDF format files as well as these fonts compressed with the 'compress' or 'gzip' utility

● Font Compiler to compile Microsoft Windows fonts into the X11 format

● Microsoft Windows fonts support in X-sessions.

X Development Kit

The XSecurePro X Development Kit (XDK) is a software development package designed to allow software developers to design and port existing X Window applications from UNIX, Linux or VMS systems to the Microsoft Windows PC platform.

The XSecurePro XDK is the X Development Kit, i.e. it is the software development environment to create X applications (or X clients). The XSecurePro XDK provides possibility to compile and link X clients by using Microsoft Visual C++ Studio (Version 6.0). A ported X application is a Win32 executable. You can run it under MS Windows (within the run-time X environment, which is another part of the XSecurePro XDK).

Local X support provided permits X clients to be started and/or displayed locally or remotely on available X servers in the network. A ported X application uses an X server on an MS Windows machine just like any other UNIX X client communicates with an X server for displaying the windows.

The XSecurePro XDK is a set of various .DLLs, include-files, and libraries (i.e., all the X Window System standard libraries and toolkits) that you can use to develop GUI or console X client applications that run on your PC under MS Windows instead of a UNIX or Linux host. You can develop a local X client from scratch using the XDK, or you can port the code of an existing UNIX or Linux X application and rebuild the project so that the application runs locally (i.e. on a PC under MS Windows).

The XSecurePro XDK also includes Motif libraries and include-files for developing local Motif clients. Local Motif clients are clients that use the current implementation of the OSF/Motif Widget set and are built to run on your PC under MS Windows instead of a UNIX host.

The current version of the XSecurePro XDK supports X11R6.6 and Motif 2.2.2.

The XSecurePro XDK provides support for X-Clients that use the GLX extension. The corresponding ".h" and ".lib" files are added to the XDK file set. The XSecurePro XDK also includes four sample GLX X-Clients (as MS VS 6.0 projects with sources).

To create a local X client application, you can use the contents of the XSecurePro XDK in conjunction with the Microsoft Visual Studio 6.0 application development tool.

Local X Clients

While running Startup or XServer, you can launch the following local X clients supplied with the package:

● mwm (based on OpenMotif 2.0)● glxinfo (the GLX extension local X Client)● glxgears (the GLX extension local X Client)● xclock● xdpyinfo

● xev● xfd● xfontsel● xkill● xlsfonts● xmodmap● xprop● xrdb● xset● xshowcmap● xwininfo

They are developed with the X Development Kit supplied with the package. You can use the local X clients when remote ones are inaccessible or inconvenient to run. You can launch the local X clients the same way as remote ones using their command line syntax.

2. Introducing to XSecurePro < previous | content | next >
















3. The XSecurePro Requirements

Your computer system must meet the following hardware, software, host and network requirements for you to install and use XSecurePro.

PC Hardware & Software Requirements

● A standard 32-bit IBM PC (e.g., i486, or Pentium) or 100% compatible● 8 Mbytes RAM● Color graphics controller supporting SVGA video modes● Mouse Unit compatible with Microsoft Windows● 25 Mbytes free hard disk space.

Note that this disk requirement does not account for the disk cluster size. The larger the cluster size the greater the disk requirement.

In addition to the above requirements, you need one of the following operating systems:

● MS Windows 9x/ME/NT4/2K/2K3/XP/Vista● TCP/IP facility with Windows Sockets Interface.

Host Requirements

● TCP/IP protocols over Ethernet or Serial port connection● Optional server implementations of FTP and TFTP● Virtual terminal protocol Telnet● SSH1/SSH2 encryption protocol● Optional server implementation of Berkeley Line Printer protocol● Login account on the host machine.


















4. Installing XSecurePro

This chapter describes how to install the XSecurePro software. The chapter assumes that you have one of the Microsoft Windows 9x/ME/NT4/2K/2K3/XP/Vista operating system installed as described in the corresponding user's guide for the product.

This chapter and the rest of the manual refer to the following two installation directories whose names you should specify at the installation steps:

● the home (or destination) directory (in which you install the package components files for all users)

● the configuration files directory (in which you store your particular configuration files, e.g. ini-files).

If you install XSecurePro in a directory different from the default, simply supply your directory name when appropriate directories are requested.

The installation of the package is carried out by running the Setup program.

















4. Installing XSecurePro < previous | content | next >

Running Setup

The software product comes normally as a self-extracting archive file that contains the package installation files.

The installation procedure consists of two steps:

1. Extracting the package installation files into a temporary distributive directory

2. Running Setup from the distributive directory.

You can run Setup manually in the default mode or use the "silent" installation mode of Setup to simplify multiple secondary installations.

Extracting Package Installation Files

This section describes how to extract the package installation files from the self-extracting file (compressed and created by WinZip).

To extract the package installation files, you should do the following:

1. Download the self-extracting archive file to your hard disk

2. Execute the file and select OK.

In the dialog box that appears, you can enter a name for a temporary distributive directory in the Unzip to folder edit field or use the Browse button to select it. By default, the installation files will be extracted to the distributive directory shown in the field.

Later (after successful installation), you can remove the temporary distributive directory or use it to start Setup for multiple secondary installations.

3. Choose Unzip to start extracting the files and then installing the package automatically. The archive file will be uncompressed and the installation files will be placed in the specified distributive directory.

4. After extracting the package installation files, choose OK in the box appeared.

The installation procedure (i.e. running Setup) will start automatically from the temporary distributive directory if you enable the When done unzipping open: .\setup.exe check box.


Running Setup

As soon as you start the installation process, you will see a number of dialog boxes with instructions for each installation step. These boxes have three buttons. The Cancel button quits the installation process. The Back button returns you to the previous step. When you press the Next button, the Setup program proceeds to the next installation step.

At any step of installation, you can use the Cancel button. The Exit Setup window appears.

You can confirm exiting or choose to continue installing.

For the first installation of the package, the procedure steps are as follows (with the dialog's names):

Welcome

At this step, it is strongly recommended that you exit all MS Windows programs before running Setup.

Software License Agreement

At this step, you must choose whether you accept all the terms of the Software License Agreement shown within the window or not before running Setup.

User Information

In this box, you should enter the Person name, the Company name, and the product serial number (for registration purposes).

Choose Destination Location

In this box, you should specify the folder where the package will be installed in (i.e. the home directory for the package). You can use the default folder name, enter your destination folder name, or select another folder using the Browse button.

To install to the specified folder, click Next. If the folder does not exist, Setup will create it. If Setup detects the package in the directory you specified, then it will prompt you to upgrade the package. (See section Upgrading XSecurePro below.)

Setup Type

At this step, you can choose components of the package you want Setup to install.

There are three Setup types: Typical, Compact, and Custom.

For the Typical type, Setup installs all the components of the package (the most common options).

For the Compact type, Setup installs the package without On-Line Help Files (the minimum required options).

For the Custom type, the Select Components dialog box appears on your display. Choose components that you wish to install (clicking on the checkmark positions).

At the bottom of the window, you can see how much Space Required will be used to install the components you choose and Space Available on your disk.

Select Program Folder

At this step, you should specify the Program Folder to contain shortcuts for the components being installed. In the Select Program Folder dialog box, you can use the default folder name, enter a new folder name, or select another folder from within the Existing Folders list.

Setup will add program icons to the Program Folder specified.

Setup

With the data specified, Setup begins to install the package. It shows how files of the components are being installed into the destination directory. Finally, Setup creates the XSecurePro Program folder with shortcuts for the package components. It also adds the XSecurePro item to the Programs menu.

Setup complete

At this step, Setup informs you that the package is ready to run. In the Setup complete dialog box, click Finish to complete Setup.

You may run the installed programs by clicking program's icons from the XSecurePro Programs' folder.

The Silent Installation Mode

The "silent" installation mode of Setup may be used for multiple secondary installations on different computers working with similar package installation environment (i.e. drive letters, installation directory name, presence of the package, etc).

The "silent" installation process consists of the following two steps:

1. Normal first installing of the package with creating a script file

2. Using the script file for multiple secondary installations.

1) To install the package with creating the script file, setup.iss, run Setup with the options:

setup -r -f1PATH\setup.iss

The -f1 option enables you to specify an alternative file location and script file name. It is recommended to specify the absolute PATH for the option.

With these arguments, Setup performs normal installation of the package and creates the script file you specified in the command in the directory according to the specified PATH. The file contains data you specified for Setup to install the package. (See section Running Setup above.)

Setup performs secondary installations using the script file, so you have to specify no input data (you only watch "silently" how Setup works automatically).

2) To perform secondary installation, make sure that the script file created at the first step is located in the distributive directory (where the setup.exe file exists). If not, then copy the script file to the distributive directory, and then run Setup with the following command line:

setup -s -wauto

With this argument (and without the -f1 option), Setup will install the package according to the setup.iss script file. Setup will search for the file in the distributive directory.

Also, you can use the following command line to perform secondary installation:

setup -s

This is the same as the "-wauto" option with the only difference: the Finish dialog message is suppressed in this case.

When running an InstallScript MSI or InstallScript installation in silent mode (i.e., using the -s option), the log file, setup.log, is by default created in the same directory and with the same name (except for the extension) as the response file. The -f2 option enables you to specify an alternative file location and log file name. It is recommended to specify the absolute path for the option as in the following example:

.\PackInstall\Setup.exe -s -f1C:\PackInstall\Setup.iss -f2C:\PackInstall\Setup.log

After Setup has finished (successfully or not) you can find the ASCII tracing file, mkltrace.out, in the distributive directory and look it through for error messages. Note that the "silent" installation may require interactive actions if Setup detects serious problems.

Installation Notes

LPR printer driver

The LPR printer driver for MS Windows NT4 is manually installed by running the self-extracting archive file, lprd.exe. This file can be found in the distributive directory with uncompressed package installation files.

NFS-Client for MS Windows 9x/ME

NFS-Client for MS Windows 9x/ME can be installed manually after installation of the main package. You can do this from the XWPNFS32.W95 subdirectory in the home directory (see the XWPNFS32.W95\readme file for more information). NFS-Client should only be installed using the Custom installation type of Setup. You must restart your PC after installation of NFS-Client to activate its driver. Also, you must restart your PC after you change the license file, xwpdllid.dll.

To install NFS-Client for MS Windows 9x/ME:

1. Copy the files from the XWPNFS32.W95 subdirectory in the home directory into a separate directory on your floppy or hard disk

2. On the DESKTOP, choose My Computer, Control Panel, and Network; then click on the Add button

3. Select Client and press Add

4. From within the Select Network Client window, press the Have disk button

5. In the Install From Disk window, specify the full path defined in step 1 and press OK

6. From within the Select Network Client window, select XWPNFS32 Client for NFS Networks and press OK to start installing.

The XWPNFS32 Client installation will result in including the XWPNFS32 Client for NFS Networks into the list of network components installed on your system. To finish installation, press OK.

NFS-Client for MS Windows NT4/2000/XP

NFS-Client for MS Windows NT4/2000/XP can only be installed by using the Custom installation type of Setup. You must restart your PC after installation of NFS-Client to activate its driver.

Exporting XServer's Settings During Installation

You can port XServer's settings on other PCs by creating and using the xsetup.ini file as follows:

1. Install the package and save its distributive directory

2. Make desired XServer's settings (resulting in the "[XSETUP]" section in the xwp.ini file under the home directory)

3. Copy the "[XSETUP]" section from the xwp.ini file into the xsetup.ini file except line "FontPath"

4. Put the xsetup.ini file into the distributive directory of the package

5. Use your new distributive directory (with the xsetup.ini file) as a distributive directory for the secondary "silent" installations on other PCs. The resulting home directory of the package will contain the xwp.ini file with your "[XSETUP]" section in it.

NFS-Client

The Installation procedure (Setup) can read in a file you prepared beforehand to contain your settings for NFS-Client. The file must have the nfsclnt.cpr name and locate in the package distributive directory (where the setup.exe file is located). The settings will be placed in the xwp.ini file. This is especially useful for "silent" installations.

Telnet

The Installation procedure (Setup) can read in a file you prepared beforehand to contain your settings for Telnet. The file must have the prosets.ini name and locate in the package distributive directory (where the setup.exe file is located). The settings will be placed in the xwp.ini file. This is especially useful for "silent" installations.

















Running UNINSTALL

You can uninstall the package by choosing the Uninstall item from the Program Folder. The program will prompt you to confirm removing the package from your computer.

When Uninstall completed, some elements might not be removed. You should manually remove items related to the application.

To uninstall NFS-Client for MS Windows 9x/ME (solely, without uninstalling other programs of XSecurePro):

1. On the DESKTOP, choose My Computer, Control Panel, and Network

2. Select XWPNFS32 Client for NFS Networks from within the list of network components installed, click Remove and then OK.

To uninstall NFS-Client for MS Windows NT4/2000/XP (solely, without uninstalling other programs of XSecurePro):

1. Run Start->Programs-> NFS Client->Uninstall.

Note that Uninstall XSecurePro will uninstall NFS-Client too.

You must restart your PC after un-installation of NFS-Client to deactivate its driver.


















Upgrading XSecurePro

If you specify the home directory that contains the package installation files, the Setup program will detect it and prompt you to upgrade or configure it.

If you choose YES, i.e. to upgrade the installed package, Setup brings up the Upgrade Type window. You can choose Typical, Compact, or Custom installation type (like you do it at step Setup Type of the normal installation sequence). This allows you to upgrade the package or to reconfigure it without reinstalling binary programs.

If you choose NO, Setup returns you to the Software License Agreement step of the normal installation sequence. This allows you to completely reinstall the package.

If you specify the destination directory that exists, Setup brings up the Choose Installation Type window.

In this box, if you choose Reinstall, Setup will return you to the Setup Type step.

If you choose Upgrade/configure, Setup returns you to the Upgrade Type step. If you choose Only Configure, Setup goes to the Select Components step. Then, in both cases, the Choose Configuration Location window appears.

In this box, you should specify the configuration directory (i.e. configuration path) in which you store your particular configuration files (e.g. ini-files) and the configuration components you selected. Then, Setup prompts you to Select Program Folder.

Note that if you choose Only Configure, then Setup will make no changes in the home directory of XSecurePro detected.


















Multi-user Installation

Multi-user installation is intended for installing a single copy of XSecurePro on a disk that will be shared by multiple users. XSecurePro must be configured for each user on each PC it will be used on. Corresponding files that define user's local XSecurePro configuration will be created in a specified directory (see Choose Configuration Location).

Multi-user installation is carried out as follows:

1. By running the Setup program, install the package on a disk that will be used for storing the shared copy (i.e. under the home directory of XSecurePro).

The next step must be done by every user of the shared copy.

2. Run the Setup program. In the installation dialogs, you must specify the home directory of XSecurePro for the shared copy (step Choose Destination Location), and a local directory where files defining a particular package configuration will be resident (step Choose Configuration Location).

Note that these secondary steps make no changes in the home directory of XSecurePro created at the first step.


















5. The XSecurePro Database

The package database is represented by three ASCII files

● terminfo.ini● lpr.inf● rgb.txt

and also by 35 keyboard definition files with the file name extension .KMF.

The terminfo.ini file contains information for terminal emulation and is described in Appendix B.

The lpr.inf file is described in Chapter LPR - Remote Printing.

















5. The XSecurePro Database < previous | content | next >

Keyboard Definition Files

XSecurePro has 35 keyboard definition files allowing you to use one of the 35 international PC keyboards. Each of them corresponds to the country your keyboard was designed for. These files are listed in Appendix A.

Your Keyboard Definition file has the .KMF extension. It resides in the XSecurePro's configuration files directory (in the location you specified when installing XSecurePro).

The basic purpose of a keyboard file is to assign PC keys to generate specific keysyms. A keysym is a key code that corresponds to a specific symbol supported by the X protocol.

A Keyboard Definition file is an ASCII source file that defines what key sequence is sent to a client when you press a given key on your PC's keyboard (i.e. keyboard mapping).

You can customize a keyboard by one of two ways:

● By modifying a selected (on installation) keyboard file

● By choosing the userkbd.kmf keyboard file and then editing it.

These are some of the things you can do:

● Make any key on your keyboard send any supported X keysym to the host

● Make use of extra keys on non-standard keyboards to send special keysyms to the host or to a client.

You can view and modify Keyboard Definition Files by using the Telnet_SSH' Keyboard Mapping option. (See section The Keyboard Mapping Option in Chapter Telnet_SSH).

The Keyboard Mapping File format is described in Appendix A.

All keyboard files are written for keyboards with a separate cursor keypad. Note that there are two U.K. keyboard files supplied. One is for a 101-key U.K. keyboard, and other is for a 102-key keyboard. The 101-key U.K. keyboard is identical to the U.S. keyboard except that holding Shift and pressing 3 produces a POUND sign instead of a '#' sign.

To input the Euro currency sign, the recommended Alt_R+E combination was inserted into the following KMF-files:

us15.kmf, danish.kmf, belgian.kmf, decemfrc.kmf, decemfr.kmf, decemgr.kmf, decemuk.kmf, dutch.kmf, frencan.kmf, french.kmf, german.kmf, hungarn.kmf, italian.kmf, latinam.kmf, norwegia.kmf, portugue.kmf, slovenia.kmf, spanish.kmf, swedfinn.kmf, swedish.kmf, swissfre.kmf, swissger.kmf, uk102.kmf, and uk102m.kmf.


The msus.kmf, uk101.kmf, decemus.kmf, userkbd.kmf, us.kmf, dvorak.kmf, and jpn106.kmf files do not provide for the Alt_R+E input.

The us15.kmf file is a copy of the us.kmf file with the Alt_R key description changed from XK_Alt_R to XK_Mode_switch.

In many European languages (e.g., France, Germany), users need to enter some special characters by combining a Diacritic (or composer) character and a normal letter. KMF files allow for this feature for national keyboards.

Note: if you need to send the four MS Windows specific key combinations to X clients, you have to enter the substitution strings into the [XSETUP] section of the xwp.ini file (for package's communication programs can use them).

For example:

CtrlEsc2=255.173 To send Ctrl + Esc, press Ctrl+KEYPAD MINUS SIGN

CtrlAlt2=255.171 To send Ctrl + Alt, press Ctrl+KEYPAD PLUS SIGN

AltEsc2=255.173 To send Alt + Esc, press Alt+KEYPAD MINUS SIGN

AltTab2=255.171 To send Alt + Tab, press Alt+KEYPAD PLUS SIGN

















The Color Definitions File

The rgb.txt file shipped by MIT jointly with the X Window System contains predefined colors in the form of correspondence between their specific RGB values and symbolic color names. The color values are present in the RRR GGG BBB format, where R, G and B represent single decimal digits and determine the intensity of the red, green and blue primaries that make up each color.

Some sample lines in the rgb.txt file may look like the following (in the "RRR GGG BBB color's alias" format):

160 32 240 purple255 0 0 red255 0 255 magenta


















6. Configuring XSecurePro

This chapter describes how to configure the XSecurePro package with the configuration utilities. The utilities allow you to set up XSecurePro for your preferences, your host system and your PC.

XSecurePro supplies two configuration utilities:

● ComSetup allows you to make communication settings relating to the networking aspects of XSecurePro that operate with the TCP/IP transport interface

● XSettings is used to make control settings relating to all aspects of XSecurePro (mainly for XServer) except networking.















This page is a part of XSecurePro online Help Manual. X-SecurePro is X-Server for windows by Labtam bringing your PC to Unix and X-Windows. Seamless Secure integration from PC to Unix and X-Window System. Bringing Maximum Security while still finding all of the standard access of X11, TCP/IP,

FTP, TFTP, LPR, TELNET, NFS and SSH. Visit Home of X Server for windows for more information.

6. Configuring XSecurePro < previous | content | next >

Using ComSetup

You can start ComSetup by clicking on the Settings item in the XSecurePro Programs' folder (i.e., from the Start/Programs/XSecurePro menu).

The Settings window will appear on your display:

The File/Open menu item of the Settings window lets you choose an .ini file (xwp.ini by default), then load its settings and make them current for applications to run. You can edit the settings before running your applications.

The File/Save as menu item of the Settings window lets you choose an .ini file (xwp.ini by default) to save current settings.

The Close menu item of the Settings window simply closes it.


By clicking Apply, any new settings you make to the Communication Setup tab will be saved in the xwp.ini file (by default).

The following sections are available:

● The Communication Setup Tab● The All Trace Tab● The XwpPeg Utility

The Communication Setup Tab

The following input fields are available:

Hosts File

This field is used to specify a location of the hosts file. You must enter the hosts file that is used by MS Windows (C:\WinNT\System32\drivers\etc\hosts for MS Windows NT4/2000/XP and C:\Windows\hosts for MS Windows 9x/ME).

The hosts file is a list of remote computers in the standard format (IP-address hostname aliases). The contents of the hosts file will be used by other programs of the package when you want to select a host to connect to from the host list box.

WinSock DLL

This field specifies the DLL that provides Windows Sockets Interface to existing TCP/IP stack. By default, wsock32.dll of the Microsoft Windows' TCP/IP will be used. You can specify to use any other TCP/IP stack by entering its 32-bit Windows Sockets Interface DLL.

Auto-start XwpPeg Package Watcher

With this check box enabled, the XwpPeg utility is started automatically with starting any package's application. Otherwise, you can launch XwpPeg manually.

Enable TCP/IP KeepAlive mode

This check box specifies the package's applications to use the TCP/IP feature, KeepAlive, when communicating with remote computers over your network. When enabled, this prevents your connection from interrupting by a remote computer when your PC does not send messages to it for a long time.

Enable Logotype

This check box toggles displaying the Logotype image each time the package's application starts up.

Disable Log Output

When selected, this check box prevents any program of the package from writing log information to the ".out" and ".ini" files.

Silent Bell

When enabled, this check box will block all sounds from all applications of the package (i.e., internal sounds and the TCP/IP protocol bell requests).

Not Warn to Save Settings

Normally, you should not forget to Apply your changes to a tab when you leave it. If this check box is clear, then the warning will appear each time you take to another tab or section of the window.

The warning will not appear if you select the check box.

Default

This button will initialise all these parameters to their default values.

The If non-single IP address Box

If your PC has more than one IP address (i.e. 'multi-home' PC – with non-single TCP/IP stack, e.g. for Ethernet + modem), then you should specify a mode for choosing one of them.

Always Use the First IP addressAlways Use the Last IP address

These modes allow XSecurePro's programs to automatically choose the local IP address.

Ask to Choose

You can set up this mode to specify that you will choose the address in the box brought up by the programs. The default mode is Ask to Choose.

The TCP/IP Info Box

Refresh

When you click on this button, ComSetup will search for available TCP/IP information and, if found, display in the info field the IP address and name of your PC according to mode settings.

Create 'sp_ghbn.out' Info file

If this check box is enabled, then all information found will be stored in the file. This allows you to check accessibility and obtain description of the TCP/IP stack used.

















Using XSettings

The XSetup dialog box consists of 7 tabs described below:

● The Startup Tab● The Mouse_Keyboard Tab● The Screen Tab● The Font Control Tab● The Advanced Tab● The Troubleshooting Tab● The Trace Tab

By clicking Apply, any new settings you make to the XSetup box will be saved in the xwp.ini file (by default).

You can cancel any changes you have made to the box and close it by pressing Close.


















The All Trace Tab

Options that you can specify within this tab are for debug purposes. They exert influence on all applications of the package.

The Network trace Box

When the Network trace check box is selected, it enables network tracing for applications of the


package.

Network trace level name

A value in this field that you can choose from the list box denotes a tracing level for collecting network trace information to the log file.

Trace file name

In this entry field, you can specify a name for a log file to store network trace data.

Number of lines for trace buffer

In this entry field, you can type in a length for the allocated memory (in number of lines) to flush it to the trace file.The value of 0 means a "very large" buffer (as much as your system allows).Caution: when a system crash happens, the data in the allocated memory is lost.

















The XwpPeg Utility

XwpPeg is a program designed to check the state of the package license accounts. XwpPeg informs users about exceeding the allocated license accounts over the specified limit. If all users of the same package have XwpPeg running simultaneously with running any package's application (and terminate after completion of the last one) then all those users will have true information about the number of concurrent package users who use package license accounts (i.e. the allocated accounts).

You can launch XwpPeg either automatically or manually. With the Auto-start XwpPeg Package Watcher check box enabled, XwpPeg is started automatically with starting any package's application.

Users can independently launch XwpPeg (before starting any package's application) to check/allocate one license account in advance. If the user starts XwpPeg manually then he/she must also manually terminate it to free the package license account allocated. Since XwpPeg is only informational, users can freely terminate it at any time; however they cannot automatically check the current number of concurrent users of the same package in that case.

You can start XwpPeg by double-clicking on the XwpPeg icon in the XSecurePro Programs' folder:

If you do not want to display the XwpPeg window, you should set to zero the value of the WorkMonitor variable in the "[XWPWATCH]" section of your xwp.ini file (e.g., WorkMonitor=0). To display the window, set the value to unit.

If you click on the Settings button, the following dialog box appears:


When you have made desirable settings, press OK.

The TCP/IP Retransmission Timeout Parameters

TCP starts a retransmission timer when each outbound segment is handed down to IP. If no acknowledgment has been received for the data in a given segment before the timer expires, then the segment is retransmitted, up to the TcpMaxDataRetransmissions times. The default value for this parameter is 5.

When a TCP connection is established, the retransmission timer is initialised to three seconds; however, it is adjusted on the fly to match the characteristics of the connection using Smoothed Round Trip Time (SRTT) calculations (as described in RFC793). The timer for a given segment is doubled after each retransmission of that segment. Using this algorithm, TCP tunes itself to the normal delay of a connection. TCP connections over high-delay links will take much longer to time out than those over low-delay links.

By default, after the retransmission timer hits 240 seconds, it uses that value for retransmission of any segment that needs to be retransmitted. This can be a cause of long delays for a client to time out on a slow link.

MS Windows NT4/2000 provide a mechanism to control the initial retransmit time, and then the retransmit time is self-tuning. The following is based on the Microsoft Knowledge Base and Microsoft MSDN Library.

To change the initial retransmit timeout parameters, you can modify the following values in the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters

Value Name: InitialRttData Type: REG_DWORDValid Range: 0-65535 (decimal)Default: 0xBB8 (3000 decimal)

The InitialRtt parameter controls the initial retransmission timeout used by TCP on each new connection. It applies to the connection request (SYN) and to the first data segment(s) sent on each connection. For example, the value data 5000 decimal sets the initial retransmit time to five seconds.

Value Name: TcpMaxDataRetransmissionsData Type: REG_DWORD - NumberValid Range: 0 - 0xFFFFFFFFDefault: 5

The TcpMaxDataRetransmissions parameter controls the number of times TCP retransmits an individual data segment (non-connect segment) before aborting the connection. The retransmission timeout is doubled with each successive retransmission on a connection. It is reset when responses resume. The base timeout value is dynamically determined by the measured round-trip time on the connection.

Caution

The above text contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. Using Registry Editor incorrectly can

cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.

For information about how to edit and restore the registry, view the "Changing Keys and Values" and "Restoring the Registry" Help topics in Registry Editor (in Regedit.exe) or the "Add and Delete Information in the Registry", "Edit Registry Data", and "Restoring a Registry Key" Help topics (in Regedt32.exe).

Note that you should back up the registry before you edit it. If you are running MS Windows NT/2000, you should also update your Emergency Repair Disk (ERD).

















The Startup Tab

The Window Mode List

This item allows you to make a choice of the XServer startup mode. Select a desired window mode by clicking on a mode name. (For more information, see related sections in Chapter Using XServer.)

● Multiple


In this mode, MS Windows works as a local window manager for your X clients. When an X client starts, it appears in a window like any other displayed by MS Windows. Each client you start creates its own window on your display. The client window's controls (i.e. its borders, the Control Menu box, move window functions, etc.) are all handled by MS Windows on your PC.

● Single

This mode presents all X clients in a single X-session window. Within the window, the window management and all other functions are typically controlled by an X Window System manager you start on a host. The X-session window itself can be sized and moved like any other MS Windows window.

● Full Screen

This mode presents all X clients in a single root window taking up full the screen outside the MS Windows graphical environment. The window management and all other functions are typically controlled by an X Window System window manager you start on a host.

● Multiple+RemoteWM

This mode is the above Multiple mode, but the local MS Windows window manager does not control windows of X clients and a user has to run any suitable remote window manager. The mode is very convenient when users use CDE-like interface where a remote window manager provides its own tool/task bar.

The Use XDMCP Box

X Display Manager Control Protocol (XDMCP) is a popular method of starting remote login sessions. Once XServer configured to use XDMCP has initiated X-session for the first time, it contacts an 'xdm' process running on a host system.

XDMCP settings are used to control the XDMCP startup method. The Use XDMCP check box lets you specify the XDMCP settings.

Change XDMCP settings only after consulting with your system administrator.

The XDMCP Mode Box

You can check one of the following XDMCP modes:

● Query

In this mode, a particular host used to establish the X connection must be specified in the Connect Host field.

● Broadcast

This mode does not allow you to specify a host in the Connect Host field. Instead, XServer will broadcast a request to start the X connection to every host named in the Broadcast List

File.To use this mode, you must create a Broadcast List File.

If you select the Broadcast mode, then the Select XDMCP Host window will appear after loading XServer. In this window, you will see the XDMCP hosts running on your network, and you can select one of them to start the X-session.

● Indirect

The query will be sent to the host specified in the Connect Host field. Then this host will either start up or broadcast a request for one or more other hosts to start the X connection.

Connect Host

This field is used to specify a network node name or IP address for the host you want to connect to in the Query or Indirect startup mode.

When you click on the scroll arrow beside the Connect Host box, a drop-down box will display host definitions listed in your hosts file. To select a host, just click on an appropriate definition.

If the hosts file does not contain the host definition you need, you can enter the host's IP address in the field (in the standard dotted IP address notation).

Broadcast List File

In the Broadcast startup mode, specify a file that contains a list of hosts that your PC will transmit a 'broadcast' message to.

The file consists of text lines each of the following format:

IP_address commentorname comment

Names must be specified as official host names or aliases in your hosts file. Note that the syntax allows you to use the hosts file as the Broadcast List File.

Note: if you leave this field empty or enter either 0.0.0.0 or 255.255.255.255 (these special destination addresses specify a broadcast), then this will provide the XDMCP broadcast mode (when your PC will transmit a 'broadcast' message to every host on your local network to query all XDMCP daemons).

Reset XServer at XDMCP Close

If checked, this check box enables closing all X clients if the remote XDM daemon terminates the XDMCP session with XServer.

XDM/CDE Special Processing

Check this check box if you are going to use the CDE XDMCP mode, i.e. with CDE installed on the remote XDMCP host (for the XServer's Multiple window mode only).

Connect to 1st answered to broadcast

This option provides the "old-style" way of using the XDMCP broadcast mode.

XDM Authentication/Authorization

This check box allows you to enable the XDM-AUTHENTICATION-1 and XDM-AUTHORIZATION-1 schemes. If your host is using XDM authentication or XDM authorization scheme, set up the values in the Display ID, Display Class, and Key fields and report them to your system administrator.

If you disable XDM authentication/authorization, then XServer will use the default client authorization scheme, MIT-MAGIC-COOKIE-1.

Notes:

According to the XSECURITY manual page of X Window System, X provides mechanism for implementing many access control systems. The sample implementation includes some mechanisms with MIT-MAGIC-COOKIE-1 (using shared plain-text "cookies") and XDM-AUTHORIZATION-1 (using secure DES-based private-keys) being two of them.

● MIT-MAGIC-COOKIE-1

When using MIT-MAGIC-COOKIE-1, the client sends a 128-bit "cookie" along with the connection setup information. If the cookie presented by the client matches one that the X server has, the connection is allowed access. The cookie is chosen so that it is hard to guess; xdm generates such cookies automatically when this form of access control is used. The user's copy of the cookie is usually stored in the .Xauthority file in the home directory, although the environment variable XAUTHORITY can be used to specify an alternate location. Xdm automatically passes a cookie to the server for each new login session, and stores the cookie in the user file at login.

The cookie is transmitted on the network without encryption, so there is nothing to prevent a network snooper from obtaining the data and using it to gain access to the X server. This system is useful in an environment where many users are running applications on the same machine and want to avoid interference from each other, with the caveat that this control is only as good as the access control to the physical network. In environments where network-level snooping is difficult, this system can work reasonably well.

This system uses 128 bits of data shared between the user and the X server. Any collection of bits can be used. Xdm generates these keys using a cryptographically secure pseudo random number generator, and so the key to the next session cannot be computed from the current session key.

● XDM-AUTHORIZATION-1

Sites in the United States can use a DES-based access control mechanism called XDM-AUTHORIZATION-1. It is similar in usage to MIT-MAGIC-COOKIE-1 in that a key is stored in the .Xauthority file and is shared with the X server. However, this key consists of two parts - a 56-bit DES encryption key and 64 bits of random data used as the authenticator.

When connecting to the X server, the application generates 192 bits of data by combining the current time in seconds (since 00:00 1/1/1970 GMT) along with 48 bits of "identifier". For TCP/IP connections, the identifier is the address plus port number; for local connections it is the process ID and 32 bits to form a unique id (in case multiple connections to the same server are made from a single process). This 192-bit packet is then encrypted using the DES key and

sent to the X server, which is able to verify if the requestor is authorized to connect by decrypting with the same DES key and validating the authenticator and additional data. This system is useful in many environments where host-based access control is inappropriate and where network security cannot be ensured.

This system uses two pieces of information. First, 64 bits of random data, second a 56-bit DES encryption key (again, random data) stored in 8 bytes, the last byte of which is ignored. Xdm generates these keys using the same random number generator as is used for MIT-MAGIC-COOKIE-1.

Default

This button sets up the default values for check boxes and edit fields in the Use XDMCP box.

The XDM Authentication/Authorization Parameters Box

Display ID

If XDM authentication or XDM authorization has been enabled on the XDM host, your system administrator will need to know the value displayed in this field. This field should normally never be changed. The Display ID value consists of these two parts separated by hyphen: the Display Class value and the arbitrary numerical value.

In very rare cases, your system administrator may determine that your Display ID is a duplicate and will ask you to generate a new one. To do this, use arrows on the right side of the Display ID field. The up arrow increases the numerical value of the Display ID, and the down arrow decreases it.Do not do this without consulting with your administrator.

Display Class

This field can be used to group classes of XDM nodes. The field should only be modified at the request of your system administrator. Otherwise it should be left unchanged.

Key

This field defines the key used in XDM authentication. If your host is using XDM authentication, your system manager will need to know the contents of your XDMCP Key and Display ID fields. This field should only be modified at the request of your system administrator. Otherwise it should be left unchanged.

















The Mouse_Keyboard Tab

The Mouse Settings Box

Middle Button Emulation

The default setting specifies a two-button mouse with the check box enabled. If you are using a 3-button mouse, click to disable the check box. The middle mouse button is emulated by clicking


simultaneously both left and right mouse buttons.

Use Mouse Wheel

This check box enables/disables XServer to process the mouse wheel (i.e., to translate its rotation to the Button4 and Button5 press/release X-events).

Note that the mouse wheel does not take effect in the non-maximized Single Window mode (because of Scrollbars).

The Keyboard Settings Box

Keyboard File List

You can configure XServer to support different international PC keyboards. The package supplies a set of keyboard mapping files that define assignments of key functions to physical keys on appropriate keyboards. The files are listed in Appendix A.

You can enter any kmf-file name in the edit field or select an appropriate keyboard file from the Keyboard File List by clicking on its file name. The default keyboard file is us.kmf.

For more information, see section Keyboard Definition Files in chapter The XSecurePro Database.

Local NumLock Key

If this check box is enabled, XServer (not X clients) will process the NumLock key.

Unlatched NumLock

If this check box is enabled, XServer will consider the NumLock key as a normal key (non-toggling). The NumLock key is unlatched by default. This was implemented to suppress the NumLock state's influence on some X Window managers and programs.

Local ScrollLock Key

This is important only for the XServer's Full Screen mode. The key is used for iconifying the XServer's window. If this check box is enabled, XServer (not X clients) will process the ScrollLock key.

Unlatched ScrollLock

If this check box is enabled, XServer will consider the ScrollLock key as a normal key (non-toggling). The ScrollLock key is unlatched by default.

Block KeySyms Changing

If enabled, this check box prevents the XServer keyboard's KeySyms mapping from external changes (e.g., by the "xmodmap" utility). The default is On.

Block Modifiers Changing

If enabled, this check box prevents the XServer keyboard's Modifiers mapping from external changes (e.g., by the "xmodmap" utility). The default is On.

Keyboard Mapping for Linux

If this check box is enabled, XServer will provide a "close-to-Linux" keyboard mapping (i.e., the Linux console keyboard mapping). This setting would be useful when using some applications of the KDE 3.x package (e.g., the "kwrite" editor) that do not correctly recognize some keys (e.g., "Shift+arrows" key combinations).

Default

This button sets up the default values for check boxes and edit fields in the tab.

















The Screen Tab

The Screen Settings Box

Enable Animation

If checked, this check box causes XServer to more precisely display color images.


Local Screen Saver

If enabled, this check box causes a Local Screen Saver program to be run (for the XServer's Full Screen and Single modes only).

Forced Backing Store

This option can be used if the Backing Store mode is enabled. (See the Advanced Tab.)

If this check box is checked, the Backing Store mode will be used with all X clients. The option will cause XServer to use Backing Store on all windows, even if the X-application does not request it.

Certain X-applications will request the Backing Store mode on windows that are complicated to draw. If this check box is clear, XServer will only use Backing Store on those windows that the X-application does request it.

Enable RENDER Extension

This option enables XServer to use the RENDER extension (not available in the 8-bits X depth mode). This also provides a wider range of available pixmap depths.

Color Mouse Cursor

If this check box is checked, then XServer is allowed to use the color mouse cursor when X clients use it.

The Display Number Box

Display Number

You can specify a display number for a particular X-session. This allows you to run simultaneously several X-sessions, each with different Display Number (e.g., several Window Managers). Section Running Several X-sessions in chapter Using XServer describes examples of using the Display Number setting.

According to X11 documentation, from the user's prospective, every X server has a display name of the form: hostname:displaynumber.screennumber .This information is used by the application to determine how it should connect to the server and which screen it should use by default (on displays with multiple monitors).

The hostname specifies the name of the machine to which the display is physically connected. For the TCP/IP type of connections, the hostname part of the display name should be the server machine's IP address name. Full Internet names, abbreviated names, and IP addresses are all allowed.

The phrase DisplayNumber is usually used to refer to collection of monitors that share a common keyboard and pointer (mouse, tablet, etc.). Most workstations tend to only have one keyboard, and therefore, only one display. Larger, multi-user systems, however, frequently have several displays so that more than one person can be doing graphics work at once. To avoid confusion, each display on a machine is assigned a display number (beginning at 0) when the X server for that display is started. The display number must always be given in a display name.

Some displays share a single keyboard and pointer among two or more monitors. Since each monitor has its own set of windows, each screen is assigned a screen number (beginning at 0) when the X server for that display is started. If the screen number is not given, screen 0 will be used.

Each Display Number corresponds to the known Port Number of XServer (0-6000, 1-6001, etc.).

Note that output log files for different Display Numbers have different names, xserver[N].out, with N being Display Number.

Auto

This check box enabled activates XServer to dynamically generate Display Number.

In this mode, any new X-session will have new Display Number and a lot of XServer instances (X-sessions) can be started with no changes in the ini-file. This feature is especially useful with NT/2000 Terminal Servers.

Note: no XServer instances must use equal Display Numbers when running simultaneously on your system (even for different users).

The Virtual Root Size Box

When you select either Single or Full Screen modes for XServer, you can fill in the Width and Height fields. This lets you set the default size in pixels for the XServer's root window. You can make the virtual screen size larger than your display if you want to (e.g., for multi-monitor systems).

The maximum virtual root size is limited by the expression of "width*height sq. pixels <= 56Mbyte" pixels.

Fit to Screen Size

If selected, this check box allows you to skip input for virtual Width and Height. XServer will use the values returned by the MS Windows display driver for a single display.

If this check box is clear, you can specify the Width and Height fields as the default size in pixels that XServer will use for its root window.

If the Width and/or Height fields are zero or negative values, then the actual screen size will be the sum of the value and the corresponding dimension of the PC's screen. For Multiple and Multiple+RWM modes, the "0" and "-1" values are only allowed.

The X depth (bits per pixel) Box

These radio buttons let you choose the color depth and visual mode that XServer will use:- 8-bit or 256-color visual mode (up to 256 colors);- 16-bit or HiColor visual mode (up to 65536 or 32768 colors);- 24-bit or TrueColor visual mode (up to 16777216 colors).

The Auto choice causes XServer to use current video settings of MS Windows (except for 32-bit, in which case XServer can use up to the 24-bit mode).

Note: if MS Windows is set up to the 8-bit visual mode (256 colors), then XServer will use the same mode.

The FullScreen Mode Box

● Minimize on Activity Losing

If this check box is enabled, the XServer's window will be iconified each time the focus changes to another window. Otherwise, it can be obscured by other windows.

The Image Format Box

● LSB

This sets up the Image Format to the LSB (Least Significant Byte/Bit first) mode (when every X client must work with XServer using imageByte- and bitmapBit- orders in the LSB format; e.g., X clients on Intel-platform machines).

This is the default setting (since XServer works with X clients without Image Format conversion).

● MSB

This sets up the Image Format to the MSB (Most Significant Byte/Bit first) mode (when every X client must work with XServer using imageByte- and bitmapBit- orders in the MSB format; e.g., X clients on SUN workstations).

● Auto

This specifies that X clients will define the Image Format for XServer.

Default


The GLX Extension Box

The GLX Extension check box enables XServer to work with X clients that use OpenGL.

XServer can work with a number of X clients simultaneously (in a multi-thread mode of GLX), and X clients may create several GLX windows.

Use Single Buffer

This button allows XServer and X clients to use one buffer for GLX operations (the GLX Single-Buffer mode).

Use Double Buffer

This button allows XServer and X clients to use two buffers for GLX operations (the GLX Double-Buffer mode). This is the default mode.

Use Mesa Emulation

This check box allows XServer and X clients to use Mesa.

Use the Mesa Emulation mode together with the Enable RENDER Extension check box selected.

Mesa is an open-source implementation of the OpenGL specification. OpenGL is a programming library for writing interactive 3D applications. Mesa 5.x supports the OpenGL 1.4 specification. Mesa is used as the core of the open-source XFree86/DRI hardware drivers. Mesa allows OpenGL to be used on systems that have no other OpenGL solution. See www.mesa3d.org for more information.

















The Font Control Tab

This tab allows you to manage font sources that can be used in X-sessions and to specify how XServer will use fonts in X-sessions.

Priority ordered path

XServer uses the Priority ordered path list on X client's requests for any font. XServer searches for the required font according to the order of font sources till the first matching occurs. In the Font


search path group box, you can rearrange the Priority ordered path list for XServer with the Insert before, Insert after, Cut, and Delete buttons.

You can enter a font directory path in the Font directory edit field, or use the Browse button to select it, or highlight a font path from within the Priority ordered path list and press Cut.

XServer must have access at least to the fixed and cursor fonts. The \FONTS\MINIMAL and \FONTS\MISC font subdirectories contain them. So the Priority ordered path list must contain these font directories.

You can specify that you want to use a font server running on one or more hosts. Instead of forcing XServer to read all fonts from your PC, the X FontServer Protocol makes it possible to manage fonts separately from XServer, directing XServer to request fonts from a font server. For example, the tcp/hp9000:7100 path specifies the font server host called hp9000 on port 7100:

For more details, see section Font Path in chapter Font Control.

Enable Scaled Fonts

If this check box is checked, then it allows XServer to use scaled fonts.

Default


Pseudo fonts

If you plan to use MS Windows fonts in X-sessions, press the Pseudo fonts button to choose MS Windows fonts and assign aliases to them. This means creating pseudo fonts.

MS Windows font specifications and aliases for Pseudo Fonts are stored in the Pseudo Fonts Directory. The Pseudo Fonts Directory, WINFONTS subdirectory, is located under the home directory (by default) of the software package.

If you need some X font that is inaccessible, XServer allows you to use any MS Windows font instead of it. MS Windows fonts do not support X11 font naming conventions. Therefore, pseudo names (aliases) are used to access them. To use a MS Windows font, you should create a pseudo font for it (i.e. choose one and assign a desirable alias). Pseudo fonts can be created in advance or immediately in the X-session.

Loading pseudo fonts takes some time to create their images. Reading font image from the X11 format file is faster. It becomes essential if X client uses a lot of fonts. To prevent this time loss, you can compile and save images of frequently used pseudo fonts in the X11-like format in your Pseudo Fonts Directory or in any font directory for later use. This will require some disk space.

You can also create a pseudo font directly in the X-session on particular X client's font requests. Unfortunately, pseudo fonts created on X client's requests become accessible only after restarting the X-session. In the current X-session, XServer uses the default font instead of requested one.

You can define whether to use pseudo fonts in the X-session or not. You should define priority of Pseudo Fonts Directory among other font sources in the Priority ordered path list. XServer will use pseudo fonts as well as X fonts.

On how you can manage pseudo fonts, see section Pseudo Fonts in chapter Font Control.

















The Advanced Tab

X-session title

In this entry field, you can specify your title for an X-session (and its icon) instead of its default title.Note: A full title is the X-session title followed by its virtual DisplayNumber.

Initial TCP port number


In this entry field, you can change the default (6000) initial port number for your X-session that XServer will use.

Max size of XSELECTION

This option is used to change the default (1MB) size for X-Selection that may be copied to/from the MS Windows' Clipboard (in Bytes).

Total multi-monitors widthTotal multi-monitors height

With these two values, you can set the forced multi-monitors mode if XServer cannot detect the multi-monitors mode automatically.WWW is the sum width and the HHH is the sum height of your "monitors".In the Full Screen mode, XServer can only use the MAIN monitor.

Quick X-session termination

This option is used to prevent from displaying the confirmation message on closing X-sessions.

Check of XDesk manager

This option is used to provide the correct focus processing by the XDesk virtual desktop manager.

Enable MS Windows Context Menu

This option is used to enable the standard MS Windows Context Menu (when right-clicks on the window's title bar provide the standard drop-down menu).

Enable Backing Store

This option lets you enable XServer to process the Backing Store mode. See also Forced Backing Store on the Screen Tab.

If this check box is checked, the Backing Store mode will be used with all X clients. This allows X Window System displays to be saved off-screen so that X clients do not have to refresh a window display after it has been obscured by another window. Saving a copy of the information obscured when windows overlap each other reduces network traffic. Certain X-applications will request the Backing Store mode on windows that are complicated to draw. The option will cause XServer to use Backing Store on all windows that the X-application requests it.

If this check box is clear, the Backing Store mode will be turned off so XServer will not save copies of windows information, even if the X-application does request it.

Icon on system TaskBar

This option enables your system to keep the X-session icon (as well as icons of applications started from the XServer's Run menu) in the system taskbar (for the Multiple modes).

Not reset XServer at last X client closing

This option is used to prevent XServer from resetting after the last X client closes its session (for not removing those resources that have been created by X clients run).

Terminate XServer at last X client closing

This option is used to automatically terminate XServer after the last X client closes its session.

Silent Bell

When enabled, this check box will block all sounds from all X applications of the package (XServer, X Clients, etc ...) (i.e., internal sounds and the X-protocol XBell requests).

Auto Clipboard Copy&Paste

This check box controls the mode of connection between the MS Windows Clipboard and the current X Selection. When enabled, then changing of the MS Windows Clipboard contents will force the same change in the current X Selection. Also, changing of the contents of the current X Selection (from the active application window) will automatically cause copying it into the MS Windows Clipboard (so you are ready to paste).

Reduce heavy Graphic

If this check box is selected, then XServer will use some methods to speed-up drawing (e.g., lossy drawing of images).

Default

This button sets up the default values for check boxes and edit fields in the box.

The Access Control Box

This box contains the following items that allow you to restrict access to your XServer from remote hosts. You can give access only to the hosts you authorized in the Authorize File and/or you specified in the Valid Hosts File.

Host Access Check

If this check box is checked, then XServer will check host access by using a file you specify in the Valid Hosts File field.

If this check box is disabled, then XServer will not check host access, so every host on your network will have access to your XServer (and the Authorization Check state does not matter).

Valid Hosts File

Use this field to specify a file you created to give access to hosts (and X clients) you wish to connect to your XServer.

This file will be used only if the Host Access Check check box is checked.

The file consists of text lines each of the following format:

IP_address commentorname comment

IP addresses are specified in the dotted IP address notation. Names must be specified as official host names or aliases in your hosts file.

Note that the host definition syntax allows you to use your hosts file as the Valid Hosts File.

Authorization Check

If this check box is checked, then XServer will make standard authorization check by using a file you specify in the Authorize File field.

If this check box is disabled, then XServer will not make standard authorization check.

Authorize File

Use this field to specify a file you created to give access to hosts you wish to connect to your XServer (for either XDM and non-XDM clients).

This file will be used only if the Authorization Check check box is checked.

Note: to use the Authorize File, you should copy the standard authorization binary file, ~HOME/.Xauthority, created with the 'xauth' utility on your host.

Auto-reject non-authorized X clients

If this check box is checked, then XServer will suppress the Authorization Audit message. This setting is useful if you want to reject any unauthorized X clients automatically (with no confirmation dialog).

Default

This button sets up the default values for check boxes and edit fields in the Access Control box.

Some Hints about Authorization and Host Access Policy

XServer checks permissions of hosts (and X clients) to establish connection by the following rules:

1. XServer will (firstly) make standard authorization check (if the Authorization Check check box is checked) and will (secondly) check host access (if the Host Access Check check box is checked).

So if the Host Access Check check box is disabled, then every host on your network will have access to your XServer.

2. If the Authorization Check check box is enabled, and a host is found in the Authorize File, then XServer will give access to the host.

3. If the Host Access Check check box is enabled, and a host is found in the ValidAccessFile, then XServer will give access to the host.

4. If the Host Access Check check box is enabled, but the ValidAccessFile field is empty or the file you specified in the field cannot be normally read or the file is empty, and the Authorization Check check box is disabled, then access to your XServer is disabled for all hosts.

5. To authorize hosts that are absent in the ValidHostsFile, you can enable the Authorization Check check box and specify the Authorize File.

















The Troubleshooting Tab

Options that you can specify within this tab are mainly for debug purposes.

Level for slow network

This option enables XServer to avoid the focus-problem when your network (or X client's machine) is slow, and XServer processes the "ButtonRelease" mouse event before it receives the "AllowEvents"/"GrabKeyboard" requests from the corresponding X client.


A slider position defines a priority level of kbd/mse events when redrawing an image that is associated with the mouse pointer position or key. For slow network or X client's machine, it may be preferable to reduce traffic due to reducing mouse pointer positions transmitted to X client and so reducing image redrawing.

Display Number for XDMCP

This option enables you to provide a "virtual" value of DisplayNumber for XServer. This value is sent to a remote XDMCP daemon instead of the real value.

Note: These settings are necessary for some programs running on remote computers to communicate with your PC from outside proxy (e.g., for VPN and other proxy-like programs).

Your IP address for XDMCP daemons

This option enables you to specify an IP address that XServer will use to communicate with the XDMCP daemon.This is applicable when the XServer's PC has more than one IP address. In this case, XServer will use the IP address specified.

MS OpenGL32 pixel format

An integer value in this entry field specifies an appropriate pixel format used by MS Windows OpenGL32 (not in the MESA mode; see GLX Extension on the Screen Tab).

If you enter 0 or leave the field empty, then MS Windows OpenGL32 will use MSDN function ChoosePixelFormat. The ChoosePixelFormat function attempts to match an appropriate pixel format supported by a device context to a given pixel format specification.

If you enter a positive integer, then MS Windows OpenGL32 will use the value to match an appropriate pixel format to a given pixel format specification.

If you enter a negative integer, then MS Windows OpenGL32 will use MSDN function DescribePixelFormat to find an appropriate pixel format. The DescribePixelFormat function obtains information about the pixel format.

Timeout to Font Server

This slider changes the default timeout value used for access to remote font servers.

Disable XServer's options

This entry field disables items from the XServer's Control menu:Restore, Move, Size, Minimize, Maximize, Close,Edit, Options, Refresh, LocalRef, Restart, Macros, Run, Messages,About, Help, LocalWin, Readme.

To disable some of the menu items, enter them in the field comma separated.

IP address to access to XServer

This option enables you to bind an IP address to the XServer's listening socket.E.g., the 127.0.0.1 value allows access to XServer from local X clients only.

Block font path changing

If disabled, this check box prevents from changing the XServer Font Path by external requests (so remote X clients are not allowed to change Font Resources). The default is OFF.

Refresh screen on changing color cells

This option is used to set the immediate refresh of screen after any color cell of the active colormap is changed.Be ready that this setting significantly slows down the XServer's performance.

Operate with Linux SuSE 9.0

This option enables XServer to be operational with Linux SuSE 9.0.

This option is relevant to the TrueColor visual mode with the Enable RENDER Extension check box cleared. In this case, XServer will "emulate the 8-bit pixmaps creation" allowing X applications (running under Linux SuSE 9.0) to use 8-bit pixmaps. To enable RENDER Extension is the most correct way.

The Multiple+RemoteWM Window Mode Box

Display remote WMs in background

This option is used to allow a remote window manager to display in background if it provides this (e.g., olwm does not provide, but dtwm does). Such a background window is suppressed by default because it covers all non-X windows.This setting is for the XServer's Multiple+RemoteWM mode.

Display any X over all MS windows

This option allows XServer to display any X windows on top of MS windows. This setting is for the XServer's Multiple+RemoteWM mode. In this case, it is convenient to use local mwm.

The Multiple Window Mode Box

Not use _MOTIF_WM_HINTS property

This option enables XServer to prevent from processing the "_MOTIF_WM_HINTS" windows property (that may be requested by remote X clients).

● Use _MOTIF_WM_HINTS_move

This option enables XServer to prevent from processing the "_MOTIF_WM_HINTS_move" windows property (that may be requested by remote X clients).

Not check of WM_SIZE_HINTSinc

This option enables XServer to prevent from processing the "WM_SIZE_HINTS" windows property (that may be requested by remote X clients).

Emulate WM window substrate

If this check box is selected, XServer will emulate a window substrate of a remote Window Manager (for some Client applications that require it to work properly). This is a special mode for some non-standard X11-Clients which require the existance of a parent window for the Client's window as a sign of running Window Manager.

Sound when XServer uses Clipboard

This check box enables system bell sound when XServer will perform Edit operations (i.e., from the Edit menu) with Clipboard.

Not start remote Window Managers

If this check box is selected, XServer will disable starting a remote window manager in answer to its request since there is another window manager already running (for Single and Full Screen modes). In the Multiple modes, only local window managers are allowed to run.

Check of X client's Backing Store

This option is only used in the Multiple and Multiple+RemoteWM modes.

If this check box is enabled, XServer will use the Backing Store mode, when the X-application requests it. But XServer will not use Backing Store while re-displaying an X-application's window in some cases.

If this check box is clear, XServer will use the Backing Store mode, when the X-application requests it.

To try this option may be useful when an X client uses the Backing Store mode and the windows are not properly redrawn.

See also Enable Backing Store on the Advanced Tab.

Enable XKEYBOARD Extension

If this check box is selected, XServer will use standard XKEYBOARD Extension (for some Client applications that require it to start up properly).

Default


















The Trace Tab

Options that you can specify within this tab are for debug purposes. They exert influence on all X applications of the package (XServer, X Clients, etc ...).

Keyboard trace level

A value (one from None, Minimal, Advanced, Full) in this field denotes a tracing level for


collecting keyboard trace information for your X-session (e.g., Events of pressing/releasing of keys) to the log file.None disables keyboard tracing.

XDMCP/ACCESS debug trace into 'c:\xservert.dat' file

If checked, this check box enables writing out any special debugging information into the c:\xservert.dat trace file.Be careful when using this option because of significant decreasing the XServer's performance and a large size of the trace file.

Trace Fonts Requests

If this check box is checked, then all font requests from X clients (with resolve messages) will be stored in the xserver.out file. This option is useful for analysis of the font accessibility and resolving font problems by XServer.

The Network trace Box

When the Network trace check box is selected, it enables network tracing between XServer and remote X clients.

Network trace level name

A value in this field that you can choose from the list box denotes a tracing level for collecting network trace information for your X-session to the log file.

Trace file name

In this entry field, you can specify a name for a log file to store network trace data.

Number of lines for trace buffer

In this entry field, you can type in a length for the allocated memory (in number of lines) to flush it to the trace file.The value of 0 means a "very large" buffer (as much as your system allows).Caution: when a system crash happens, the data in the allocated memory is lost.
















17. Font Control < previous | content | next >

Font Path

Font Path is an ordered table of font sources (a Priority ordered path list). A font source is one of the following: a font directory, a reference to a remote font server, and a pseudo font directory. XServer uses Font Path on X client's requests for any font. XServer searches for the required font according to the order of font sources till the first matching occurs.

XSecurePro provides wide range of local X fonts (standard font sets supplied by MIT along with X11 R6). These font sets are immediately available after installing the package. They appear in Font Path as font directories under the FONTS subdirectory in the XSecurePro home directory.

Also, XServer can use different locale 16-bits fonts including Chinese, Japanese, or Korean fonts, etc.

To manage Font Path, choose XSetup and then select the Font Control tab in the Settings window.


Note: The FONTS subdirectory shown in pictures of this chapter is not under the XSecurePro home directory. Users can move it to a desired location in their file systems (see section Editing Font Path below) after installation of the package.

The Apply button in the tab writes new Font Path into the xwp.ini file located in the XSecurePro configuration directory.

If the Enable Scaled Fonts check box is selected, it allows XServer to use scaled fonts.

Font Directory

A font directory contains a number of font description files in the X11 format. Setup installs a set of font directories under the FONTS subdirectory in the XSecurePro home directory (by default).

Any font directory must have the fonts.dir file (that contains the font description list according to font files of the directory), the fonts.ali file (with font aliases), and a set of font description files (with the .pcf, .snf, or .pgz file name extension).

The fonts.alias file name as well as fonts.ali can be used in the FONTS directories.

Note: XServer can only use uncompressed .pcf (X11R5 or later), .snf (X11R4), and .bdf files. Also, XServer can use these font files compressed with the compress or gzip utility (for X11R6.3 only).

If your remote X server supports 'compressed' fonts (X11R6 server does. X11R6.3 server supports 'gzipped' fonts too), you may compress the .pcf and .snf font files with the 'compress' or 'gzip' utility (for X11R6.3 only).

You have to convert each .bdf file to .pcf (X11R5 or later) or .snf (X11R4) with the bdftopcf and bdftosnf utilities.

To convert each font.bdf file in the set, run the following command line:

● in X11R5, bdftopcf font.bdf > font.pcf● in X11R4, bdftosnf font.bdf > font.snf

XServer must have access at least to the fixed and cursor fonts. The \FONTS\MINIMAL and \FONTS\MISC font subdirectories contain them. So Font Path must contain these font directories at least.

Font Server

You can specify that you want to use a font server running on one or more hosts. Font servers are defined in the X11 R6 release of the X Window System. Instead of forcing XServer to read all fonts from your PC, the X FontServer Protocol makes it possible to manage fonts separately from XServer, directing XServer to request fonts from a font server via the X Consortium standard network protocol. In addition, for fonts that take a long time to open, this allows XServer to continue with

other clients while the font server services the font requests.

A font server specification for TCP/IP has the following format:

tcp/name: port [/catalogue+catalogue+...]

name

The network name or IP address for the host that the font server is running on.

port

The remote port that the font server is listening on. The port number value is usually of 7100 or 7500 depending on the operating system used, but check this with your system administrator.

catalogue

An optional list of the font catalogue(s) you want to use. If more than one catalogue is specified, separate each name with a 'plus' sign (+).

For example, the following specifies the font server host called hp9000 on port 7100:

tcp/hp9000:7100

You can include more than one font server specification into the Font Path list.

Note: You must add an entry (with the host name and IP address for the remote font server you want to use) into the hosts file used by MS Windows:

● C:\WinNT\System32\drivers\etc\hosts for MS Windows NT4/2000/XP

● C:\Windows\hosts for MS Windows 9x/ME.

Editing Font Path

To remove a highlighted font source from Priority Ordered Path, press Delete.

To move a highlighted font source from Priority Ordered Path to the Font directory edit field, press Cut.

To insert the Font directory edit field into Priority Ordered Path, select a path from within the Priority ordered path list and then click Insert before or Insert after.

Also, to fill in the Font directory edit field, you can manually enter a font directory path or use the Browse button to select it (i.e. a path to a fonts.dir file).

Pressing Default places font paths in the Priority ordered path list according to a default order.

You can use the 'minus' and 'space' characters in the Font Path items. The total length of the Font Path items can be up to 2040 characters.

Also, see Appendix C Troubleshooting for examples.

Font Service

The XFontset Service utility allows you to view fonts accessible for X clients in the current X-session. You can use this option instead of running the xlsfonts and xfd X clients.

When you click on the XFontset Service icon in the XSecurePro Programs' folder,

the Font Directories dialog box appears:

Also, to display this box, you can run Font Manager from the X-session Control menu.

This dialog box shows font directories existing in Font Path (i.e. a Priority ordered path list).

You can check how XServer resolves a particular X client's font request by typing the requested font name in the edit field and then pressing the Resolve Font Request button. The program will show you the font directory and the font file corresponding to the requested name. You can use the 'asterisk' sign (*) as the wildcard character in the edit field.

You can check data consistency of any highlighted font directory by pressing Check. The program will tell you about detected unresolved font aliases and unresolved references to font files in this font directory. This might be useful after you made any manual changes in the font directory.

You can get all font names existing in any font directory by highlighting it and then pressing Show Font List, or double-clicking on a font directory. The Entire Fonts List dialog box will appear.

This dialog box shows font files and respective font names and aliases (from the fonts.dir file). For any font highlighted, you can view (in Notepad windows) Font Info, Properties, Char Info (and save these text files). Also, pressing Image will display a box like below with character images of the selected font.

To find a particular font name in a long font list (and then to view font info), you can use the Browse button, and then press Search in the dialog box that will appear.

Note: You cannot view a font that is shaded by a similar font name in the font directory preceding it in Font Path. To view and use such a font, you should place its directory first in Font Path.

Understanding the Font List

You can list the fonts available on your remote system by typing the following command in an X window:

xlsfonts | more

A list appears displaying one font per line. This "font name" is typical:

-adobe-courier-bold-o-normal--10-100-75-75-m-60-iso8859-1

The hyphen-separated fields designate the following:

● adobe Foundry

● courier Family

● bold Weight

● o Slant

● normal Set Width

● Additional Style

● 10 Pixel Size

● 100 Point Size

● 75 Y Resolution

● 75 X Resolution

● m Spacing

● 60 Average Width

● iso8859 Character Set Registry

● 1 Character Set Encoding

The most important properties to consider are the Family, Weight, Slant, and Point Size.

Family is the style of the letters. Some common examples are Helvetica, Courier, and Times.

Weight is the width of the line making up the letter. The options are regular and bold.

Slant is the angle of the letters. The most common are R for Roman (meaning upright), I for italic, and O for oblique (similar to italic). Whether the slant is designated as I or O depends on the family.

Point Size is the size of the letters. The number refers to decipoints. Multiply the point size to get the decipoints (10 point type is 100 decipoints).

















17. Font Control

Fonts installed on your system can be used by any graphical X Window System application. A remote font server is started automatically with your graphical environment, and then all fonts installed on your system are automatically available to all of your X Window System applications. X clients request character information from the font server, which can return data in various formats, ensuring high quality display of a variety of font styles and sizes.

You can use your familiar host-based X fonts via XSecurePro's XFontset Service. The XFontset Service utility provides:

● Rasterized fonts with outline data to all X applications● Wide range of local X fonts (the standard font sets supplied by MIT along with X11 R6)● Support for different locale 16-bits fonts including Chinese, Japanese, or Korean fonts, etc.● Use of uncompressed PCF, SNF, and BDF format files as well as these fonts compressed with

the 'compress' or 'gzip' utility● Font Compiler to compile Microsoft Windows fonts into the X11 format● Microsoft Windows fonts support in X-sessions.

This chapter describes how you can manage local and remote font sources for XServer to access and to resolve all font requests from X clients.

The Font Control tab of XSetup in the Settings dialog box lets you specify how XServer will use font sources that can be available in X-sessions (including scaled fonts).

The Pseudo fonts button in the tab allows you to define how XServer will use MS Windows fonts in X-sessions.

You can run Font Manager from the X-session Control menu (or run XFontset Service from the XSecurePro's Program Folder) to view:- the ordered font sources list- the font list of each font directoryfont information, font properties, font metrics- images of any available font.

If the Trace Fonts Requests check box in the Trace tab of XSetup in the Settings dialog box is checked, then all font requests from X clients (with resolve messages) will be stored in the xserver.out file. This option is useful for analysis of the font accessibility and resolving font problems by XServer.


















Pseudo Fonts

If you plan to use MS Windows Fonts in the X-session, press the Pseudo fonts button in the Font Control tab in the Settings window. Then you can choose MS Windows fonts and assign aliases to them. This means creating pseudo fonts.

You can compile a pseudo font into the X11 format and save it in any font directory for later use. You can also create a pseudo font directly in the X-session on particular X client's font requests. To enable this, switch on the Use pseudo fonts and Create pseudo on X client request check boxes in the Pseudo fonts dialog box. Pseudo fonts created in the X-session will only become accessible after restarting XServer.

If you need some X font that is inaccessible, XServer allows you to use any MS Windows font instead of it. MS Windows fonts do not support X11 font naming conventions. Therefore, pseudo names (aliases) are used to access them. To use a MS Windows font, you should create a pseudo font for it, i.e. choose one and assign a desirable alias. Pseudo fonts can be created in advance or immediately in the X-session.

You can manage pseudo fonts by using the Pseudo fonts dialog box.

The Save button writes all changes to Pseudo Fonts Directory. This cannot be undone if you press Cancel in the Pseudo fonts dialog box or in the Font Control Tab afterwards.


Pseudo Fonts Directory

MS Windows font specifications and aliases for Pseudo Fonts are stored in the Pseudo Fonts Directory. The Pseudo Fonts Directory, WINFONTS subdirectory, is located under the home directory (by default) of the software package.

Creating Pseudo Font

To create a pseudo font, press the Create pseudo button in the Pseudo fonts dialog box. The Font dialog box will appear on your display. Select a suitable font and press OK. In the Specify alias for selected font box, enter a pseudo font alias and click OK.

The created pseudo font will appear in the Select pseudo font list box lexicographically ordered.

The alias must only contain alphanumeric characters (including the 'underscore' sign). The alias must be unique among existing pseudo fonts.

Viewing Pseudo Font

To view a pseudo font, select it in the Select pseudo font list box and click the View button. The

Font sample window will appear with the font sample in it.

Note that the font image is displayed by the MS Windows (not by XServer). This option is for font identification only. To see how XServer displays a font image, you can use the 'xfd -fn <alias>' command in the X-session.

Deleting Pseudo Font

To delete a pseudo font, highlight it in the Select pseudo font list box and click the Delete pseudo button. You can delete more than one font at a time.

You should confirm removing each font and the total number of the selected fonts.

Compiling Pseudo Font to the X11 format

Loading pseudo fonts takes some time to create their images. Reading font image from the X11 format file is faster. It becomes essential if X client uses a lot of fonts. To prevent this time loss, you can save images of frequently used pseudo fonts in the X11-like format in your Pseudo Fonts Directory. This will require some disk space. To save the image, highlight the required font in the Select pseudo font list box and click the Compile into X11 button. In the Place X11 font to box, specify a font directory to store the X11 font file.

You can enter the font directory path in the Font directory edit field or use the Browse button to select it. If the specified directory is not the font directory (e.g., it is empty), then the fonts.dir file will be created in it.

You should confirm compiling each font. To use the font directory, include it into Font Path.

Creating Pseudo Fonts on X Client Request

Pseudo fonts can be created immediately in the X-session on particular requests of X clients. If the requested font is not found, you will be prompted to create a new pseudo font. Creating pseudo fonts in the X-session is especially useful when you run X applications for the first time.

Creating pseudo fonts in an X-session is the same as in the Pseudo fonts dialog box. You can use the requested font name as the pseudo font alias. To enable creating pseudo fonts in the X-session, check on the Create pseudo on X client request check box. For batch X clients, it is preferable to disable the option to avoid interactive requests.

Unfortunately, pseudo fonts created on X client's requests become accessible only after restarting the X-session. In the current X-session, XServer uses the default font instead of requested one.

Enabling to Use

You can define whether to use pseudo fonts in the X-session or not.

To disable pseudo fonts, check off the Use pseudo fonts check box. Pseudo Fonts Directory will be removed from Font Path. XServer will only use X fonts. You will not be able to create pseudo fonts in the X-session.

To enable pseudo fonts, check on the Use pseudo fonts check box. The Pseudo fonts priority dialog box will appear.

You should define priority of Pseudo Fonts Directory among other font sources in Font Path. To insert Pseudo Fonts Directory into Font Path, select a position and use the Before selection or After selection buttons. XServer will use pseudo fonts as well as X fonts.

















The Run Box

Options that you can select are for running services.

● The XServer Tab● The NFS-Server service Tab

The XServer Tab


The Run with XWP.ini Box

This box allows you to start up or to restart XServer.

Run

This button starts up XServer with current settings if it is not already running (thus beginning a new X-session).

Restart

This button restarts XServer (with reading in the XWP.ini file) that is currently being run.
















16. Using XServer < previous | content | next >

The "[XSETUP]" Section of the ini-file

The "[XSETUP]" section of the ini-file may have the following entry lines you can customize for particular needs and applications. These settings are absent in the XSettings dialog box.

On how to port XServer's settings (i.e., the "[XSETUP]" section of the ini-file) onto other PCs, see subsection Exporting XServer's Settings During Installation in section Running Setup in chapter Installing XSecurePro.

AllowCONTEXTMENU=1

You can use this binary setting to enable the standard MS Windows Context Menu (i.e. the standard drop-down menu will appear with right-clicking on a window's title bar).

ConnectXWClipboards=p

This option specifies the mode of connection between MS Windows Clipboard and a current X Selection.

ConnectXWClipboards=7 is the default value (when the Auto Clipboard Copy&Paste check box in the XSettings window is checked).

Three of the least significant bits in p specify one of three main kinds of auto-copying:

● bit e1=1 enables copying from MS Windows Clipboard to X Selection;

● bit e2=1 enables copying from X Selection to MS Windows Clipboard;

● bit e3=1 makes copying from X Selection to MS Windows Clipboard when any window controlled by XServer loses its activity.

ConnectXWClipboards=0 disables automatic copying MS Windows Clipboard and X Selection when they are changed, i.e. there is no immediate link between MS Windows Clipboard and X Selection (when the Auto Clipboard Copy&Paste check box in the XSettings window is not checked).

DisableRENDERAnimCursor=1

You can use this binary setting to display the standard arrow cursor instead of real cursors of X-Clients. This helps accelerate displaying cursors.

ILikeAIX=1

This option specifies the "old-style" keyboard mapping (like it was on the AIX X console, X-Terminals, etc.). This is the actual mode for some AIX X-Clients that work with fixed keyboard mapping only.


ILikeXWinPro52=1

This binary setting allows XServer to only use the "PseudoColor" visual with the "888" colors weight instead of the default value of "666". This mode of XServer (in the 8-bits mode) is useful for some old CAD/CAE systems.

MiddleButtonTimeout=10

This option is used to set up the value for the 'MiddleButton wait timeout', in msec.

TerminateOnSuspend=1

You can use this binary setting to provide a graceful termination of X-Clients on suspending PCs.

Emulate WM window substrate=1

This option is for the Multiple mode of XServer. In this mode, the local window manager provides usual behavior, but each top-level non-popup X window has a parent window controlled by the window manager.

UnlatchedCapsLock=1

This option toggles the actual CapsLock keyboard key to unlatched mode, i.e. XServer will consider the CapsLock key as a normal key (non-toggling).

This is the actual setting if you re-map the CapsLock key in the kmf-file (say, interchanging the CapsLock and LeftControl keys, that is popular among some users on SUN machines).

Use_8_3_fonts_alias_file=1

This option specifies for XServer to use the standard fonts.alias file name.

Historically, XServer uses the fonts.ali name to list font aliases in the file.

This setting is useful when XServer uses a mounted font directory.

UseUsualSelect=1

This setting provides the "old-style" way of using the select WinSock API request.

















Restriction of Windows Fonts Accessibility

The current version of XServer provides access only to those MS Windows fonts that are available in the MS Windows System Font Table. Therefore, accessibility of a particular MS Windows font depends upon MS Windows session history. If you try to use a MS Windows font that is inaccessible, MS Windows will give you some other font with the closest metrics. XServer guarantees getting of the exactly requested MS Windows font if you create the pseudo font for it immediately after starting MS Windows or compile it into the X11 format file.


















The NFS-Server service Tab

This tab allows you to install and uninstall NFS-Server as MS service. Also, you can make settings and control NFS-Server as MS service on your system.

Services overview

A service is an application type that runs in the background and is similar to UNIX daemon applications. Service applications typically provide features such as client/server applications, Web


servers, database servers, and other server-based applications to users, both locally and across the network.

You can use Services to:

● Start, stop, pause, resume, or disable services on remote and local computers (including remote computers running Windows NT 4.0.). You must have the appropriate permissions to start, stop, pause, restart, and disable services.

● Manage services on local and remote computers (on remote computers running Windows XP, Windows 2000, or Windows NT 4.0 only).

● Create custom names and descriptions for services so that you can easily identify them (on computers running Windows XP or Windows 2000 only).

● Configure startup options for MS services.● Set up recovery actions to take place if a service fails, for example, restarting the service

automatically or restarting the computer (on computers running Windows XP or Windows 2000 only).

● Enable or disable services for a particular hardware profile.● View the status and description of each service.

Services permissions

Each service has special permissions that you can grant or deny for each user or group. You can set permissions for individual services by using Security Templates.

According to MS Windows Help Manual, Services must log on to an account in order to access resources and objects on the operating system. Some services are configured by default to log on to the Local System account, which is a powerful account that has full access to the system. If a service logs on to the Local System account on a domain controller, that service has access to the entire domain. Other services are configured to log on to LocalService or NetworkService accounts, which are special built-in accounts that are similar to authenticated user accounts. These accounts have the same level of access to resources and objects as members of the Users groups. This limited access helps safeguard your system if individual services or processes are compromised.

Services running as the LocalService account access network resources as a null session with no credentials. Services running as the NetworkService account access network resources using the credentials of the machine account.

Installing the NFS-Server Service

Click Install to install NFS-Server Service and to add the service to the Services list on your system.

The service name of NFS-Server Service is XWP NFS server.

When started, NFS-Server will be listening on port 2049 (default) for NFS clients' requests.

To configure how NFS server is started (Automatic or Manual), you should choose the Startup type and then press Set.

You should test that you have configured NFS-Server Service to operate successfully in the Normal mode before attempting to run it as a MS Windows Service. (Refer to section Using NFS-Server.)

Uninstalling the NFS-Server Service

You can remove NFS-Server from the Services list on your system by pressing Uninstall in the NFS-Server Service tab.

Click Yes to confirm removing NFS-Server from the Services list on your system. You need not restart your PC.

Note that NFS-Server correctly stops and disconnects active NFS clients, and closes the port used for communications on your computer when uninstalling NFS-Server.

Using the NFS-Server service

This section describes how to start and use NFS-Server as a standard MS Windows service. The advantage of services is that they can be started at boot time independently of any logon session, and will continue to run as users log on and off of the machine.

The functionality and settings of the NFS-Server service are just the same as of NFS-Server itself. Additionally, you can control the behavior of NFS-Server as a MS Windows service.

Configuring the NFS-Server Service

To configure how NFS-Server will communicate with NFS clients, you should press Run as Settings.

You specify settings just in the same manner as you configure NFS-Server. (See section Configuring NFS-Server in chapter Network File System Server (NFS-Server).) Additionally, you control NFS-Server Service as a MS Windows service with the Service status box.

Refresh

This button refreshes the status of the service.

The Properties Box

If you have a typical installation, many services are configured as Automatic (that is, they start automatically when the system starts or when the service is called for the first time). If a service is configured as Manual, you must start the service manually before it can be loaded by the operating system and made available for use. If a service is configured as Disabled, it cannot be started automatically or manually.

To configure how NFS-Server is started, you can choose the Startup type and press Set. Then you can manage the service session by pressing the Start/Stop and Pause/Resume buttons with watching the Service status.

To start, stop, pause, resume, or restart a service (as administrator), you can also open the Services window (clicking Start/Settings/Control Panel/Administrative Tools/Services), right-click your service, and then click Start, Stop, Pause, Resume, or Restart.

The Windows Firewall Box

Windows Firewall monitors all aspects of the communications that are sent and received, and inspects the source and destination address of each message that it handles. In Microsoft Windows XP Service Pack 2 (SP2), Windows Firewall is turned on by default for all Internet and network connections. If you choose to install and run another firewall, turn off Windows Firewall.

When Windows Firewall is On, it blocks all unsolicited requests to connect to your computer, except for requests to programs or services selected on the Exceptions tab. When your computer gets an unsolicited request, Windows Firewall blocks the connection. If you choose to unblock the connection, Windows Firewall creates an exception. You can add a service as an exception so that the firewall will allow client's information to reach your computer and the service (through open ports for it). For programs that open ports automatically as needed to connect to your computer, Windows Firewall must allow the program to open the correct port. For these programs to work correctly, they must be listed on the Exceptions tab in Windows Firewall.

You can add a new service to your network by installing the service software on one of your network computers and then adding the service definition so that Internet Connection Sharing (ICS), if enabled, will allow the service to be accessed from the Internet. The information that you must enter to add a service definition includes: the description of the service (a name that you can easily recognize), the name or IP address of the computer hosting the service, and the TCP or UDP port number for the service (the port number that external computers use to contact this service).

Add

This button adds the XWP NFS server definition (i.e., the description of the service) to the Exceptions tab in Windows Firewall to allow the service to be accessed from NFS clients' computers.

When you add or change settings for a service or program, you must choose whether to open the port to any computer or only to computers on your network. If you choose Any computer in the Advanced tab of Windows Firewall, anyone from the Internet or your network can connect to your computer. If you choose My network only, only computers on your local network can connect. If you prefer, you can click Custom, and then type a custom list of IP addresses and subnets that should be allowed access.

Delete

This button removes the XWP NFS server definition from the Exceptions tab in Windows Firewall.

















16. Using XServer

The XSecurePro's XServer is a program that emulates the X terminal on your PC. It is the X-server implementation of the X11R6.6 release of the X Window System. XServer allows you to run one or more X Window based client applications (X clients) that are resident on host computers. The host can be any computer that supports the X protocol across your TCP/IP network.

X client applications can be displayed in individual windows, as multiple windows contained in a single XServer's window, or in a full-screen mode outside the Microsoft Windows graphical environment. The first two methods include functions to copy and paste data between X clients and the Microsoft Windows clipboard.

While running XServer, you can initiate a login session by using Telnet, XDMCP, or Startup (REXEC, RSH, RLOGIN) methods. You can launch several X-sessions that will be running simultaneously each with its own settings. XServer can work on multi-monitors PCs.

While running XServer, you can launch any local X client supplied with the package.

The macro options of XServer let you create macro-files to remember sequences of your keystrokes. Then, whenever you want, you can play back these keystroke macros in a target X-application window by choosing an appropriate macro-file.

XServer provides German and/or French messages and text labels under the corresponding national version of MS Windows.

XServer supports the following X Extensions:

● Extended-Visual-Information● XinputExtension● MIT-SUNDRY-NONSTANDARD● SHAPE● XTEST● XC-MISC● XC-APPGROUP● GLX for OpenGL● RENDER● SECURITY● LBX

To get X Extensions supported by your system, run the following command line:

xdpyinfo -display IP_address_of_your_PC:0

XServer can connect to a remote LbxLoxy service (a Low Band Width X proxy) either by direct access to a remote host or through one of the established SSH1/SSH2 protocol connections as well.


XServer can use MESA (6.2.1), an open-source implementation of the OpenGL specification.

This chapter describes how to use XServer in all four possible modes: Full Screen mode, Single window mode, Multiple window mode, and Multiple+RemoteWM mode.














This page is a part of XSecurePro online Help Manual. X-SecurePro is X-Server for windows by Labtam bringing your PC to Unix and X-Windows. Seamless Secure integration from PC to Unix and X-Window System. Bringing Maximum Security while still finding all of the standard access of X11,

TCP/IP, FTP, TFTP, LPR, TELNET, NFS and SSH. Visit Home of X Server for windows for more information.


Using LBX

About LBX

Low Bandwidth X (LBX) is a network-transparent protocol for running X Window System applications over transport channels whose bandwidth and latency are significantly worse than that used in local area net works.

The design centre for LBX is to use a proxy as an intermediary between the client and server, so that the low bandwidth/high latency communication occurs between the proxy and server. The proxy re-encodes and compresses requests, events, replies and errors, as well as the resulting data stream to reduce the volume of data that must be sent over the wire. Additionally, the proxy can cache information from the server to provide low-latency replies to clients. This reply generation by the proxy is known as short-circuiting. A proxy can handle multiple clients for a given server, but does not prevent clients from connecting directly to the server. The design allows the proxy to multiplex multiple clients into a single data stream to the server.

LBX employs several different compression and short-circuiting methods. Use of these methods is negotiable, and in some cases, the algorithm used by a given method is negotiable as well. LBX also provides for negotiation of extensions to LBX.

About lbxproxy

Applications that would like to take advantage of the Low Bandwidth extension to X (LBX) must make their connections to an lbxproxy. These applications need to know nothing about LBX, they simply connect to the lbxproxy as if it were a regular server. The lbxproxy accepts client connections, multiplexes them over a single connection to the X server, and performs various optimizations on the X protocol to make it faster over low bandwidth and/or high latency connections.

With regard to authentication/authorization, lbxproxy simply passes along to the server the credentials presented by the client. Since X clients will connect to lbxproxy, it is important that the user's .Xauthority file contain entries with valid keys associated with the network ID of the proxy. lbxproxy does not get involved with how these entries are added to the .Xauthority file. The user is responsible for setting it up.


Synopsis of lbxproxy:

lbxproxy [:<display>] [option]

If :<display> is specified, the proxy will use the given display port when listening for connections. The display port is an offset from port 6000, identical to the way in which regular X display connections are specified. If no port is specified on the command line option, lbxproxy will default to port 63. If the port that the proxy tries to listen on is in use, the proxy will exit with an error message.

The lbxproxy program has various options, all of which are optional. It is recommended to use them with their defaults.

The -display dpy option specifies the address of the X server supporting the LBX extension. If this option is not specified, the display is obtained by the DISPLAY environment variable.

See lbxproxy manual for more details.

Running xterm from Telnet_SSH

Suppose that your PC has the network name xtp. Run XServer, then run Telnet_SSH and connect to remote machine supporting LBX. After logging in, you can launch lbxproxy and then xterm in the main Telnet_SSH window by using the following commands ($ is a prompt sign):

$ lbxproxy :62 -display xtp:0 &$ xterm -display :62 &

or (with setting the DISPLAY environment variable and using it by default):

$ DISPLAY= xtp:0; export DISPLAY$ lbxproxy :62 &$ xterm -display :62 &

After that xterm will work with display :62.0 (corresponding to port 6062) and will use LBX protocol. In the xterm window, you can run the echo $DISPLAY command resulting in :62.0 (for our example).

If the port that the proxy tries to listen on (6062) is in use, the proxy will exit with an error message. To locate available proxy services, you can use the xfindproxy program communicating with a proxy manager (see About xfindproxy below).

Terminating XSession terminates lbxproxy.

You can launch more than one lbxproxy-xterm pairs, each with different displays available (e.g., :61.0 in addition to above).

Note: to run lbxproxy under Solaris, you must have rights as root.

Running xterm from Startup

The Startup utility automatically runs XSession and then prompts you to specify data for connection and commands for execution. You can connect to remote machine supporting LBX and start up lbxproxy-xterm pair by entering in the Command field and sequentially executing the following commands (e.g., from xtp:0 and for port 6061):

/usr/X11R6/bin/lbxproxy :61 -display xtp:0/usr/X11R6/bin/xterm -display :61

Note that you should enter the full file specification to execute such commands. (You can use locate lbxproxy

or which lbxproxy commands to determine the path on the remote machine.)

Note that –zlevel 6 is the most optimal option you can set for the Zlib compression level used by lbxproxy for stream compression.

About xfindproxy

xfindproxy is a program used to locate available proxy services. It utilizes the Proxy Management Protocol to communicate with a proxy manager. The proxy manager keeps track of all available proxy services, starts new proxies when necessary, and makes sure that proxies are shared whenever possible (see About proxymngr below).

Synopsis of the xfindproxy:

xfindproxy -manager managerAddr -name serviceName -server serverAddr [-auth] [-host hostAddr] [-options opts]

The -manager argument is required, and it specifies the network address of the proxy manager. The format of the address is a standard ICE network id (e.g. "tcp/a.b.c:6500").

The -name argument is required, and it specifies the name for the desired proxy service (e.g. "LBX"). The name is case insensitive.

The -server argument is also required, and it specifies the address of the target server. The format of the address is specific to the proxy service specified with the -name argument. For example, for a proxy service of "LBX", the address would be an X display address (e.g. "xtp:0").

The -auth argument is optional. If specified, xfindproxy will read 2 lines from standard input. The first line is an authorization/authentication name. The second line is the authorization/authentication data in hex format (the same format used by xauth). xfindproxy will pass this auth data to the proxy, and in most cases, will be used by the proxy to authorize/authenticate itself to the target server.

The -host argument is optional. If xfindproxy starts a new proxy service, it will pass the host specified. The proxy may choose to restrict all connections to this host. In the event that xfindproxy locates an already existing proxy, the host will be passed, but the semantics of how the proxy uses this host are undefined.

The -options argument is optional. If xfindproxy starts a new proxy service, it will pass any options specified. The semantics of the options are specific to each proxy server. In the event that xfindproxy locates an already existing proxy, the options will be passed, but the semantics of how the proxy uses these options are undefined.

If xfindproxy is successful in obtaining a proxy address, it will print it to stdout. The format of the proxy address is specific to the proxy service being used. For example, for a proxy service of "LBX", the proxy address would be the X display address of the proxy (e.g. "a.b.c:62").

If xfindproxy is unsuccessful in obtaining a proxy address, it will print an error to stderr.

See xfindproxy manual for more details.

Example

Suppose that your PC has the network name xtp (with XServer running), and the network address of the proxy is "a.b.c:6500". Execute the following command (in Telnet_SSH or Startup as described above):

xfindproxy -manager a.b.c:6500 -name lbx -server xtp:0

For a proxy service of "LBX", the proxy address would be the X display address of the proxy (e.g., "a.b.c:62") printed to stdout. (See also Proxy manager details below.)

After that you can execute the following command (see Running xterm from Telnet_SSH above):

xterm -display :62 &

Note that XSession must be running in your PC when you execute proxymngr and xfindproxy (xtp:0 in commands above is the address of the target X server).

Note: terminating XSession terminates lbxproxy.

About proxymngr

The proxy manager (proxymngr) is responsible for resolving requests from xfindproxy (and other similar clients), starting new proxies when appropriate, and keeping track of all of the available proxy services. The proxy manager strives to reuse existing proxies whenever possible.

There are two types of proxies that the proxy manager deals with, "managed" and "unmanaged" proxies. A managed proxy is a proxy that is started "on demand'' by the proxy manager. An unmanaged proxy, on the other hand, is started either at system boot time, or manually by a system administrator. The proxy manager is made aware of its existence, but no attempt is made by the proxy manager to start unmanaged proxies.

Synopsis of proxymngr:

proxymngr [-config filename] [-timeout seconds] [-retries #] [-verbose]

The command line options that can be specified to proxymngr are:

-config

Used to override the default proxymngr config-file. See Proxy Manager Config-File below for more details about the config-file.

-timeout

Sets the number of seconds between attempts made by the proxy manager to find an unmanaged proxy. The default is 10.

-retries

Sets the maximum number of retries made by the proxy manager to find an unmanaged proxy. The default is 3.

-verbose

Causes various debugging and tracing records to be displayed as requests are received and proxies are started.

Proxy Manager Config-File

The proxy manager maintains a local configuration file describing the proxy services available. This configuration file is installed in /usr/X11R6/lib/X11/proxymngr/pmconfig during the installation of proxymngr. The location of the configuration file can be overwritten using the -config command line option.

Aside from lines starting with an exclamation point for comments, each line of the configuration file describes either an unmanaged or managed proxy service.

For unmanaged proxies, the format is:

<service-name> unmanaged <proxy-address>

service-name

Is the name of the unmanaged proxy service, and must not contain any spaces, for example "XFWP''. service-name is case insensitive.

proxy-address

Is the network address of the unmanaged proxy. The format of the address is specific to the service-name. For example, for the "XFWP'' service, the proxy-address might be "firewall.x.org:100''.

If there is more than one entry in the config-file with the same unmanaged service-name, the proxy manager will try to use the proxies in the order presented in the config-file.

Example

xfwp unmanaged firewall:4444

For managed proxies, the format is:

<service-name> managed <command-to-start-proxy>

service-name

Is the name of the managed proxy service, and must not contain any spaces, for example "LBX''. service-name is case insensitive.

command-to-start-proxy

Is the command executed by the proxy manager to start a new instance of the proxy. If command-to-start-proxy contains spaces, the complete command should be surrounded by single quotes. If desired, command-to-start-proxy can be used to start a proxy on a remote machine.

Example

lbx managed /usr/X11R6/bin/lbxproxy

Proxy Manager Details

When the proxy manager gets a request from xfindproxy (or another similar client), its course of action will depend on the service-name in question.

For a managed proxy service, the proxy manager will find out if any of the already running proxies for this service can handle a new request. If not, the proxy manager will attempt to start up a new instance of the proxy (using the command-to-start-proxy found in the config-file). If that fails, an error will be returned to the caller.

For an unmanaged proxy service, the proxy manager will look in the config-file to find all unmanaged proxies for this service. If there is more than one entry in the config-file with the same unmanaged service-name, the proxy manager will try to use the proxies in the order presented in the config-file. If none of the unmanaged proxies can satisfy the request, the proxy manager will timeout for a configurable amount of time (specified by -timeout or default of 10) and reattempt to find an unmanaged proxy willing to satisfy the request. The number of retries can be specified by the -retries argument, or a default of 3 will be used. If the retries fail, the proxy manager has no choice but to return an error to the caller (since the proxy manager cannot start unmanaged proxy services).

See proxymngr manual for more details.

To run proxymngr, check its config-file and execute the following command with options you need:

/usr/X11R6/bin/proxymngr

Note: to run proxymngr, you must have rights as root.

















18. X Development Kit

This chapter describes the XSecurePro X Development Kit (XDK) for Microsoft Windows 9x/ME/NT4/2K/2K3/XP/Vista.

The chapter covers the following:

● What the XSecurePro XDK provides

● How to install the XSecurePro XDK

● What is in the XSecurePro XDK

● How to use the XSecurePro XDK to develop a local X client

● How to port a UNIX or Linux X client to a PC and recompile it.


















7. Telnet_SSH

This chapter describes how to start and use the Telnet_SSH program supplied with XSecurePro.

Telnet_SSH is a communications and terminal emulation program for logging into remote machine and executing commands in a remote machine. It allows you to connect to and communicate with hosts that support:

● The Telnet protocol and run a Telnet service over an insecure channel

● The Secure Shell protocol, SSH, and run an SSH service to provide strong authentication and secure encrypted communications between two untrusted hosts over an insecure network. X11 connections and arbitrary TCP/IP ports can also be forwarded over the secure channel. TCP forwarding features make it possible to communicate across a firewall. The "Dynamic Port Forwarding" feature (an extension of the standard SSH1/SSH2 protocols for inter-task requests in multi-task environment) allows you to start other package's utilities (e.g., FTP) through established SSH1/SSH2 protocol connections without direct access to remote hosts.

To provide terminal emulation from your computer running MS Windows, the remote host must be configured with the TCP/IP program, the Telnet or SSH1/SSH2 service program (daemon), and a user account for your PC.

Telnet_SSH includes the following features:

● Compatibility with SSH protocol version 1.5 (a SSH1 client)

● Ciphers (for the SSH1 client): 3DES, Blowfish, DES, RC4

● Compatibility with SSH 2.0 protocol (a SSH2 client based on OpenSSH 3.4)

● Ciphers (for the SSH2 client): 3DES, Blowfish, CAST128, ARCFOUR, AES128, AES192, AES256-cbc

● Password authentication

● RSA authentication

● Compression support (with auto-selection of the compression mode supported by both sides)

● Connection forwarding, including full support for X-protocol connection forwarding

● "Dynamic Port Forwarding" that provides other tasks on the same PC with requested port forwarding.

Once you have established a connection, you can use Telnet_SSH to start X clients and perform other operations outside the X Window System environment.


While you are using Telnet_SSH, your PC emulates one of the following terminal types: XTERM, ANSI, AT386; DEC VT52, VT100, VT125, VT220 or VT240, using connection-based services of TCP. You can specify the terminal emulation settings for the current connection by making the appropriate settings on the Settings option.

By using the Keyboard Mapping option (i.e. keymap editor invoking), you can load, change (re-define keys and create a new keyboard layout), and save any keyboard definition file.

You can start more than one Telnet_SSH session, and use Telnet_SSH to open multiple Telnet_SSH windows on a single host or different hosts at the same time.
















14. Network File System Server (NFS-Server) < previous | content | next >

Configuring NFS-Server

To configure NFS-Server, click on the Export button. The NFS Server - Settings dialog box appears on your display.

You can then change the Exported Directories Table and the NFS User Access Table.

You can add new directories to the Exported Directories Table or remove them from it.

You can add new remote users to the NFS User Access Table or remove them from it for any selected exported path.


The Export Directories Box

Adding an Exported Directory

To add an exported directory to the current list, click on the Add directory button. The Select directory window will appear on your display.

Specify the Drive and Directories fields for export.

After clicking OK the selected directory will appear on the Export Directories list box in the NFS Server - Settings window. Clicking on Cancel will not change the current list.

Removing an Exported Directory

To remove a directory from the Export Directories list:

1. Select a directory in the Export Directories list box;

2. Click on the Remove button.

WebNFS Enable

With the WEBNFS protocol, NFS-Clients can directly mount a shared directory (i.e., not using protocols PORTMAP and MOUNT).

If you select an export directory and press the WebNFS Enable button, then you allow NFS-Clients

to use the WEBNFS protocol for mounting that directory.

To disable using the WEBNFS protocol for a shared directory (marked with the "public" attribute), select it and press the Unset as WebNFS button.

The Name Conversion Box

Mode

NFS-Server supports (by default) the 'best for UNIX' name re-mapping, i.e. remote UNIX NFS clients (and UNIX programs which use mounted files) are able to perform all UNIX file operations (including full case-sensitivity).

MS Windows does not distinguish the upper/lower case in directory/file names. For example, two different file names for UNIX, A.a and a.A, are the same names for MS Windows. So remote NFS clients may be confused when operating with such directory/file names. With using the Shift Symbol, NFS-Server can help NFS clients to work around this.

You can choose one of the three modes to convert directory/file names passing through NFS-Server:

● Use shift symbol - converting names with using the Shift Symbol● Lower case - converting remote directory/file names to lower case

(for example, FILEname => filename, Aa => aa)● Upper case - converting remote directory/file names to upper case

(for example, FILEname => FILENAME, Aa => AA)● Allow illegal chars - converting names with allowing for some special characters that may be

used in directory/file names (by remote NFS clients)(i.e., illegal in names, such as '"', '*', ':', '$', '|', etc).

The default mode is Use shift symbol.

Shift Symbol

If you select the Use shift symbol mode, then you may use the Shift Symbol option.

The Shift Symbol list box lets you choose a character to mark case changing of letters in directory/file names while local-remote name converting. The default Shift Symbol is '!'. At beginning of name conversion, the case is considered as lower one.

NFS-Server uses the Shift Symbol as 'escape-symbol' when converting names. I.e., each case changing of letters in a remote name will be converted to a pair of 'escape-symbol and lower-case letter' in a related local name, and each such pair in a local name will change the case of the 'lower-case letter' in a related remote name.

Examples of converting remote (UNIX) names to local (MS Windows) names ('!' is used as Shift Symbol):filename <==> filename, FILENAME <==> !filename, FILEname <==> !file!name, fileNAME <==> file!name,aa <==> aa, AA <==> !aa, Aa <==> !a!a, AaA <==> !a!a!a, aA <==> a!a, aAa <==> a!a!a.

Use UTF8 Name Format

With this check box enabled, NFS-Server will support the Unicode/UTF8 format to represent names of your files and directories (on NFS Clients' requests).

The 8.3 filename format is used in non-Unicode mode for files with non-ANSI long file names.

Refresh frequency

Refresh frequency is used to specify cycle time for NFS-Server to update status information.

Enable logging

If checked, this check box enables storing the information (about the NFS-Server's start/finish and every mount/unmount command) in the nfslog.txt file in the home directory of the package.

OK

By clicking OK, any new settings you make to the NFS Server - Settings dialog box will be saved in the xwp.ini file (by default) and the dialog will be closed (making them active immediately).

Cancel

You can cancel any changes you have made to the dialog box and close it by pressing Cancel.

















14. Network File System Server (NFS-Server)

This chapter describes how to start and use the NFS-Server program supplied with XSecurePro.

NFS-Server is a network file server that supports the NFS protocol version 3 (see RFC1813. NFS version 3 protocol specification) and the NFS protocol version 2 (see RFC1094. NFS: Network file system protocol specification). It has a multi-threaded code developed for the Win32 environment and is designed to work with the built-in MS Windows TCP/IP-32 protocol stack.

The main feature of NFS-Server is to provide access to hard disk space and files residing on your PC to users working on other network nodes under different operating systems (with NFS client support and TCP/IP).

NFS-Server can be installed under one of the MS Windows (9x/ME/NT4/2K/2K3/XP/Vista) operating systems to share your local drives and folders with other networked users, no matter which operating system they are running on their workstations. Only an NFS client is required on that system for users to mount your disks as part of their system.

By using NFS-Server, you can:

● Add new directories to the Exported Directories Table or remove them from it

● Add new remote users to the NFS User Access Table or remove them from it for any selected exported path

● Change access rights for remote users defined in the NFS User Access Table (i.e. specify each user's read and write permission to your exported path)

● View status information on those directories of your PC that remote users are currently accessing (i.e. active NFS clients' connections)

● Suspend/resume current activity of NFS-Server.

NFS-Server provides German and/or French messages and text labels under the corresponding national version of MS Windows.

















7. Telnet_SSH < previous | content | next >

Starting and Terminating Telnet_SSH

You can start Telnet_SSH by double-clicking on the Telnet_SSH icon in the XSecurePro Programs' folder:

The Telnet Connect Host dialog box will appear on your display:

A session is a connection to a remote machine made with a number of connection-specific settings assigned to it. These settings are saved in an ini-file and profiles and allow you to have different preferences for different hosts (using different ini-files and profiles).

All Telnet session settings are stored in the [TELNET] section of the xwp.ini file.

All SSH1 session settings are stored in the [tSSHPro] section of the tsshpro.ini file.

All SSH2 session settings are stored in the [tSSH2Pro] section of the tsshpro.ini file.

Also you can specify some initial settings for the session with the Details button (that is described in section Details of a Session).

The first thing you should do to initiate a session is to establish a connection to a remote machine. In the dialog, you must specify the protocol you will be using, the hostname or IP address, and the port number of the service.

Pressing OK will store current settings (for the next session) and will establish a connection, using them.

You can cancel any changes you have made to the dialog box by clicking on Cancel. This will also close the dialog.


Telnet

This button specifies whether to use the standard TELNET protocol over an insecure channel to provide an interface for communications between clients and servers. In the Telnet mode, Telnet_SSH works as the Telnet client on your PC.

Note: a Telnet session is not encrypted; so it will transmit your user name, password and other sensitive or private information in an easily readable format.

SSH-1SSH-2

These buttons specify whether to use the SSH1 (or SSH2) protocol over an insecure channel to provide secure communications between clients and servers. In the SSH1/SSH2 modes, Telnet_SSH works as the SSH1/SSH2 client on your PC.

Note: SSH is a tool for secure remote login over insecure networks. It provides an encrypted terminal session with strong authentication of both the server and client, using public-key cryptography. An SSH session provides maximum security and privacy on the Internet and local networks. It encrypts all traffic (including passwords) to effectively eliminate eavesdropping, connection hijacking, and other network-level attacks.

SSH is an acronym for the Secure Shell protocol - a secure communications protocol used to encrypt network traffic between clients and servers that replaces existing TCP/IP protocols such as TELNET, RSH and RLOGIN. SSH must be supported by both the client and the server. SSH1 is the first version of the SSH protocol and SSH2 is the second one.

Host

This field specifies a hostname or IP address (network node specification) for the remote machine you want to connect to (and which provides the Telnet or SSH1/SSH2 service).

When you click on the scroll arrow beside the Host box, a drop-down box will display host definitions located in your hosts file. To select a host, click on an appropriate definition.

Port

This field specifies the port number of the Telnet or SSH1/SSH2 service on the remote machine you want to connect to.

For the Telnet mode, the default port number of the Telnet service is decimal 23.

For the SSH1/SSH2 mode, the default port number of the SSH1/SSH2 service is decimal 22.

Starting a Telnet Session

To establish Telnet connection, specify the Telnet mode, enter the network name or IP address for the host you want to connect to, then change the default Telnet port number if required, and press OK. Telnet_SSH connects and logs into the specified hostname.

Once you have connected to the host, the host name or IP address you specified appears at the top

of the Telnet window (with the terminal emulation mode), and the host login prompt appears in the window:

You must prove your identity to the remote machine using some authentication method (e.g., password authentication). Specify the login information required for your host system. You can then interact with the host by choosing commands from displayed menus, or by typing commands in the window and starting remote applications.

You can customize your Telnet session with the Settings and/or Keyboard Mapping items in the Options menu (described below).

The following sequence of commands can be used as an example of working in the Telnet session (depends on the remote shell used):

login: arsexam$ DISPLAY=xtp2:0; export DISPLAY;$ xterm&$ mwm&

To capture the screen output of Telnet commands to a file, Telnet_SSH writes the log to the telnet.out file in the home directory (in case of fatal errors or due to the 'trace' command line parameter).

Starting an SSH Session

The SSH1/SSH2 protocol mode provides secure communication over an insecure channel by encrypting the data channel with a cipher algorithm. The cipher selected for the session is used to encrypt network traffic between the local PC and the remote host, thus providing data privacy. Encryption is started before authentication, and no passwords or other information is transmitted in the clear.

The ciphers provided for use with the SSH1 protocol and supported by Telnet_SSH are DES, 3DES, RC4, and Blowfish. The ciphers provided for use with the SSH2 protocol and supported by Telnet_SSH are 3DES, Blowfish, CAST128, ARCFOUR, AES128, AES192, and AES256-cbc. The DES and 3DES (triple DES) ciphers are slow. The RC4 and Blowfish ciphers are considerably faster (less

CPU intensive) than 3DES. You can specify ciphers Telnet_SSH will try to use with the SSH1 protocol. Telnet_SSH will try 3DES as the first cipher (by default).

Telnet_SSH supports optional compression of all data with gzip (including forwarded X11 and TCP/IP port data), which may result in significant speedups on slow connections. You can specify the compression level from 1 to 9 (default). Level 1 gives you fastest performance (with lowest compression) and level 9 - slowest performance (with highest compression).

Note: to work in the SSH1 protocol mode, you need the SSH1 daemon, .sshd, being run on the remote machine you want to communicate with (the SSH2 daemon, .sshd2, for the SSH2 mode respectively).

To establish SSH1/SSH2 connection, specify the SSH1/SSH2 mode, enter the hostname or IP address for the host you want to connect to, then change the default SSH1/SSH2 port number if required, and press OK. Telnet_SSH connects and logs into the specified hostname.

You can customize your SSH1/SSH2 session with the Settings and/or Keyboard Mapping items in the Options menu.

See the Forwarding item of the Option menu on how to specify necessary port forwarding and X11 forwarding settings to customize your SSH1/SSH2 session.

Once you have connected to the host, the SSH Authentication window appears:

Authentication is the process of verifying that an individual truly is who he or she claims to be. You must prove your identity to the remote system, using one of the three methods of authentication that Telnet_SSH supports for connecting to SSH servers: password authentication, RSA authentication, or keyboard-interactive authentication (for the SSH2 protocol).

Password authentication transmits the user's password to the server to authenticate the connection. The transmitted password is protected from network eavesdropping due to the cipher encryption of the data channel.

Keyboard-interactive authentication is a flexible authentication method using an arbitrary sequence of requests and responses. It is not only useful for challenge/response mechanisms, but it can also be used for asking the user for a new password when the old one has expired (for example).

RSA authentication uses a public/private key pair to authenticate the connection.

The scheme is based on public-key cryptography: there are cryptosystems where encryption and decryption are done using separate keys, and it is not possible to derive the decryption key from the encryption key. RSA is one such system. The general mechanism behind RSA authentication is that each user creates a public/private key pair for authentication purposes. The SSH server knows the public key, and only the user knows the private key. The file $HOME/.ssh/authorized_keys lists the public keys that are permitted for logging in. When the user logs in, the client SSH program tells the SSH server which key pair it would like to use for authentication. The server checks if this key is permitted, and if so, sends the user (actually the client SSH program running on behalf of the user) a "challenge", a random number, encrypted by the user's public key stored on the server. The challenge can only be decrypted using the proper private key. The user's client then authenticates the connection by successfully decrypting the challenge using the user's private key, proving that he/she knows the private key but without disclosing it to the server.

SSH server implements the RSA authentication protocol automatically. Normally the user creates his/her RSA key pair by running the ssh-keygen utility on the remote host. This stores the private key in $HOME/.ssh/identity and the public key in $HOME/.ssh/identity.pub in the user's home directory. The user should then copy (or append) the identity.pub file to $HOME/.ssh/authorized_keys in his/her home directory on the remote system.

The private key is often stored encrypted at the client machine in an identity file. The user should specify the identity file to be used for RSA authentication.

Passphrase is a password used to protect a private key from unauthorized use. The passphrase is firstly used when generating the public/private key pair by the ssh-keygen utility to encrypt the private key (i.e. the identity file at the server machine). The user must supply the passphrase before the digital signature can be generated.

RSA authentication offers a higher level of authentication security than password authentication by requiring both the private key and the passphrase that protects the private key in order to complete authentication.

In the SSH Authentication dialog, you should specify necessary settings for authentication.

User name

This field specifies the username used to log on to the remote machine.

Passphrase

If password authentication is selected (with Use plain password to log in enabled), you can enter your password in this field.

If RSA authentication is selected (with Use RSA key to log in enabled), you can enter your passphrase here.

It is recommended that a passphrase be assigned to all private keys to prevent unauthorized use, especially in environments where multiple individuals have access to the machine on which the private key files are stored. When using public key authentication, a private key with an assigned

passphrase will not be available if the correct passphrase is not supplied during the authentication process.

Use plain password to log in

When enabled, this radio button specifies to use password authentication.

If password authentication is selected, you can enter your password in the Passphrase entry field. If a password is not entered here, you will be prompted to enter it during the connection process.

Use RSA key to log in

When enabled, this radio button specifies to use RSA authentication.

If RSA authentication is selected, you should enter your passphrase in the Passphrase entry field. Also you should specify a location of the identity file to be used for this process. You can enter the filename in the entry field or select it with the Private key file button.

Private key file

When you press on this button the standard Open File window will appear. You can select your identity file for RSA authentication. RSA authentication will only be attempted if the identity file exists.

In order to use your private key you must transfer the identity file created by the ssh-keygen utility on the SSH server machine to a secure location on your PC for this file such that you are the only individual with access to it.

One way to transfer the identity file from the remote machine to your PC is to use an FTP client (in ASCII mode). Another way is to copy the contents of the identity file to the clipboard using a remote text editor and then to paste the contents of the clipboard to a file you created using a local text editor (e.g., Notepad).

Also, prior to using RSA authentication, the public key must be made available to the SSH server.

Use Keyboard-Interactive Mode

When enabled, this radio button specifies to use keyboard-interactive authentication.

Disconnect

You can immediately close a communication connection with this button.

Specify the login information required for your host system. When your identity has been accepted by the SSH server, the server either executes the given command, or logs into the machine and gives you a normal shell on the remote machine. All communication with the remote command or shell will be automatically encrypted.

Example of Initiating a Telnet Session via SSH

First, make sure that:

● your PC is accessible from your remote host (e.g., by using Ping)● your remote host is accessible from your PC● sshd-daemon (or sshd2-daemon) is running on your remote host.

If OK, then you may initiate the Telnet session via SSH like the following steps:

1. Double-click on the Telnet_SSH icon from the XSecurePro Programs' folder to start Telnet_SSH (the Telnet Connect Host window should appear)

2. Choose SSH-1 (or SSH-2) in the Interface section

3. Enter the network name or IP address for the remote host you want to connect to

4. Change the default SSH port number if required

5. Click OK to establish connection with the remote host (the SSH Authentication window should appear)

6. Choose to Use plain password to log in

7. Specify the login information required for your host system: User name and Password in the Passphrase field

8. Click OK to log in to the remote host (the Telnet_SSH window should appear).

Terminating a Session

You can terminate a Telnet_SSH session by choosing the Close command on the Control Menu box, or by selecting Exit on the Telnet_SSH Commands menu.

If you select Exit while a connection to a remote system is still active, Telnet_SSH disconnects you from the remote system automatically (properly closing all applications used).

Telnet/SSH2 as SOCKS4 Proxy

Telnet/SSH2 provides the "Dynamic Forwarding" feature that allows FTP, XStartup, and XServer/LbxLoxy to access protected hosts via SSH2-connection. Really "Dynamic Forwarding" is a well-known standard SOCKS4 proxy server. This means that it can be used to access remote hosts by a "crooked" way.

A typical sample example

Suppose that:

● You work on HOST1 (say, in Australia) under MS Windows and can use Telnet/SSH2● You have an intermediate HOST2 (say, Labopt.com in USA) with the modern SSH2-daemon● You want to access (from HOST1 using MSIE, Netscape...) the "overparticular" site (say,

"http://www.sho.com/" in USA) on HOST3 accessible only from USA hosts.

You can do the following:

1. Connect from HOST1 to HOST2 via SSH2 using Telnet/SSH2.With command "netstat -na", check that there created the "16001" LISTEN port.

2. Tune MSIE on HOST1 so as it will use the SOCKS proxy on the local PC.3. Run MSIE on HOST1 and try to connect to site "http://www.sho.com/" on HOST3.

Some notes

● Why only now.

All described above was possible all the time, but old SSH2-daemons have a bug which we had to work around in FTP, XStartup, and XServer/LbxLoxy. We did this via additional delay after successful connection. It was our specific. We know that the bug still existed in SSH-daemon of Linux RH 7.1. Now we see that the Linux RH 9 does not have this bug.

● What is this - port 16001 (is it always 16001 ?). NO !

Each Telnet/SSH2 session automatically creates one "Dynamic Forwarding" (i.e., SOCKS4) port starting at number 16001. If 16001 is busy (say, you connected to HOSTxxx via Telnet/SSH2), then the 2nd Telnet/SSH2 session will create the 16002 port number, and so on. Closing a session makes the corresponding port free.

















Starting and Terminating NFS-Server

You can start NFS-Server by double-clicking on the NFS-Server icon in the XSecurePro Programs' folder:

The NFS-Server window will appear on your display with the message field showing those directories of your PC that are currently mounted by remote users. You can then specify the information required to give access to exported paths on your PC (i.e. determine the directory trees you wish to make available as exported file systems for remote NFS clients).


The following control items in the NFS-Server window are available.

Export

This button is used to change lists of exported directories and remote users (see section Configuring NFS-Server below).

Show Mounts

This button is used to show you current mounts and who are currently connected to NFS-Server (see section The Status Report Window below).

Close

This button is used to terminate NFS-Server.

About

This button is used to display the About NFS-Server dialog box.

Server State

The Suspend radio button allows you to suspend current NFS-Server's activity and the Resume radio button - to resume it respectively.

Show Icon on System Taskbar

If enabled, this check box lets you keep the NFS-Server's icon on the system tray. The Hide button removes the NFS-Server's icon from the system taskbar and the NFS-Server's window from the desktop as well.

Verbose

This check box controls the amount of information output in the message window.

Checking Access to Exported Directories

After start-up NFS-Server on your PC you can check access to your exported directories by the following way:

1. On your remote NFS client system, add your PC's IP address to its host table and give it a name (e.g., 'xtp3').

2. Make sure that there is proper connectivity to your PC. On a typical UNIX system, you can try the following command line:

showmount -e xtp3

You will see the list of exported directories for remote mounting.

3. The sample mounting command may have the following appearance:

mount xtp3:/g /mnt

















Changing the NFS-User Access Table

Each exported directory may have a list of users which are allowed to access to it. Access information is stored in the NFS User Access Table.

Adding a User

To add a user to the NFS User Access Table, on the NFS Server - Settings dialog box:

1. Select a directory in the Export Directories list box

2. Click on the Add User Access button.

The User Access window will appear on your display:

You should specify the following fields to map a remote user to the exported path:

● NFS Client Host● User ID● Group ID● R/W access (i.e., the Read only check box)

After clicking OK the specified values will appear on the NFS User Access list box. Clicking on Cancel will not change the current access list.


Note: if you specify the NFS Client Host by its IP address (not by a host name), then you can use the '*' sign (an asterisk) as a wildcard character for a number of hosts (e.g., 192.168.136.*).

Also you can use an asterisk as a wildcard character for UserID and GroupID.

With each UNIX user mapped to a MS Windows local account, only the person login the UNIX machine with the matching UID/GID can access files in that account. Here, 'local account' is the account on the MS Windows system that you want to share-out files to the UNIX users (i.e. an exported path). 'UID/GID' are the numbers that matches the user account on the UNIX machine. To get UID/GID numbers, login to the UNIX machine and type 'id' at the prompt.

Removing a User

To remove a user from the NFS User Access Table, on the NFS Server - Settings dialog box:

1. Select a directory in the Export Directories list box

2. Select a user in the NFS User Access list box

3. Click on the Remove button.

The Status Report Window

NFS-Server makes access control when remote users try to mount a directory. To view those directories of your PC that are being accessed by remote users, click on the Show Mounts button in the NFS-Server window. The Status Report window will appear on your display.

For each exported path, remote users are designated with HostName, UserID, and GroupID. The information in the dialog is dynamically updated (according to Refresh frequency).
















13. Startup < previous | content | next >

The "[Startup]" Section of the ini-file

The "[Startup]" section of the ini-file may have the following entry lines you can customize for particular needs and applications.

ExitAfterExecute=1PromptPassword=1

to specify the auto-execution mode of the default command line.


















Telnet_SSH Menu Options

The Telnet_SSH menu bar displays five items: Commands, Edit, Options, View, and Help. They are described below.

The Help Menu

The Help menu contains the following menu commands:

Contents

Displays the Telnet help file.

About

Displays copyright, version and program information about Telnet_SSH.

The Commands Menu

The Commands menu contains the following menu commands:

Connect

The Connect item displays the Telnet Connect Host dialog box so you can specify the remote system you want to communicate with. You can also connect to a port or service to use other than


the standard Telnet port. This is useful when the Telnet client is being used to access something other than a Telnet daemon.

This command is not available when you are already connected to a remote system.

Once you connect to the remote system, the title bar in the Telnet_SSH window shows the remote system name.

Disconnect

The Disconnect item ends the connection to a remote system so you can connect to another system or end your session. This command is not available when you are not connected to a remote system.

Interrupt Process

This command sends the Telnet Interrupt Process command (IP control function) to the remote host. This command (which suspends, interrupts, aborts, or terminates the operation of a user process) tells the host to stop the current process to which the terminal is connected. This function is frequently used when a user believes his process is in an unending loop, or when an unwanted process has been inadvertently activated.

Abort Output

This command sends the Telnet Abort Output command (AO control function) to the remote host. This command tells the host to run to completion the current process, which is generating output, but without sending the output to the user's terminal from the host. Further, this function typically clears any output already produced but not yet actually sent to the user's terminal.

Break

This command sends the Telnet Break command (BREAK control function) to the remote host. This command (intended to indicate that the Break Key or the Attention Key was hit) tells the host to stop what it is doing.

Are You There

This command sends the Telnet Are You There command (AYT control function) to the remote host. This command determines if the connection with the host is still up and the system is running. This command tells the host to send back to the user's terminal some visible evidence that the command was received. This function may be invoked by the user when the system is unexpectedly 'silent' for a long time, because of the unanticipated (by the user) length of a computation, an unusually heavy system load, etc.

Pause Output

This command pauses output (it sends Ctrl+S to the host). The Resume Output item then becomes active and can be selected.

Resume Output

This command resumes output (it sends Ctrl+Q to the host) after output has been paused.

Exit

The Exit item terminates the Telnet_SSH session.

The Edit Menu

The Edit menu displays two commands that allow you to edit the lines you type in a Telnet_SSH window: Erase Character and Erase Line. Also there are two standard commands, Copy and Paste, for text operations with the Microsoft Windows' clipboard.

Erase Character

The host should delete the last preceding undeleted character or print position from the data stream being supplied by the user. A print position may contain several characters that are the result of overstrikes, or of sequences such as <char1> BS <char2>...

Erase Line

The host should delete all the data in the current line of input, i.e. characters from the data stream back to, but not including, the last CR LF sequence sent over the TELNET connection.

Copy

To copy text onto the clipboard, leaving the original text intact and replacing the previous clipboard contents, select the text you want to copy, and choose Copy. This command is unavailable until you have selected text.

Paste

When there is text in the clipboard, you can use Paste to insert a copy of the clipboard contents at the insertion point to the Telnet_SSH window, or to another Microsoft Windows application. This command is not available if the clipboard is empty.

There are several ways in using Copy and Paste. The first example will be to show using your mouse.

1. In your Telnet window, scroll over with your mouse to the text you want to select.2. Then click your left mouse button and hold it down to select the text you want to copy.3. Once the text has been highlighted in a box frame, right click your mouse button to see the

Copy to clipboard option, and then click on this button.

4. Your text has now been copied to the Microsoft clipboard, and you can now choose where you want to paste it.

5. Click on where you want the text to be pasted, and then right click on the mouse and click on the Paste from clipboard button. The original text that you copied was now pasted into the area you selected.

The second example will be to show using Menus.

1. With the same text to copy, you can highlight the text again. You will see a solid clear box appear around the selected text.

2. Click on the "Edit Menu" and then click on "Copy". This has now copied the selected text to the clipboard.

3. Now click to where you want the copied text pasted to. Click on the "Edit Menu" again and then click "Paste". This will paste the text into your chosen location.

To Copy and Paste, you can also use key combinations, "Ctrl+C"/"Ctrl+V" or "Ctrl_L+Shift_L+C"/"Ctrl_L+Shift_L+V".For more information, see settings CtrlCVmode and QuickClipBoard.

See also settings SelectRect and FineSelectMode that you can use to specify different modes for text selection in your Telnet window.

Save ExtScreen

● To FileThis option lets you save the output buffer of your session into a file.

● To ClipboardThis option lets you send the output buffer of your session to Clipboard.

● To File and ViewThis option allows you to save the output buffer of your session into a file and then to invoke Notepad for you to view or edit the text.

For example, to save a Telnet screen that you want to be written to a file, do the following as you are working in your Telnet window:

1. Click on "EDIT", then click on "Save ExtScreen" and then click on "To File and View".2. Then choose which location you want to save the file to and also what name you want

to call the file.3. After entering the file name and location where you are saving the Telnet screen, press

the Save button. After this the screen shot has been saved. Then you will see a Notepad window with the screen content appear.

The View Menu

With options from this menu, you can navigate through the output buffer of your session. For additional information, refer to subsection Details of a Session in section Starting and Terminating Telnet_SSH.

The Actual Screen is the one that always displays the last line of the session's output. In this screen, you can only input your commands.

The First Extend Screen option displays lines for the first screen of the output buffer. The Prec Extend Screen option displays lines for the preceding screen (if any) from the current one. The Next Extend Screen option takes you to the next screen (if any) from the current one.

These options are only used for reviewing (not for entering) information and moving to screens. They suspend output into the output buffer and disable your input. To resume output and enable input, use the Actual Screen option.

To navigate through the output buffer, you can also use the Notepad-like view-key combinations.

The Find option lets you search text in the output buffer like you do that when using Notepad.

The Options Menu

Telnet_SSH allows you to personalize your settings and automatically use them every time you establish a connection to a remote computer. This is accomplished by storing your personalized settings in the corresponding ini-files. The Options menu displays items that you can choose to specify particular implementations of Telnet_SSH. Normally they do not have to be changed.

● The Settings Option● The Keyboard Mapping Option

















Restrictions

● The current version of NFS-Server can use read/write buffers of 1024, 2048, 4096 or 8192 byte size (for NFS protocol version 2) and up to 32K (for NFS protocol version 3) (see the 'mount' command parameters 'rsize', 'wsize').

● The current version of NFS-Server supports UNIX-like file names (directory and file names are case-sensitive and can have several extensions).

● The file name length can be up to 256 characters.

● The path length can be up to 512 characters.

● The directory listing length can have up to 26000 items.

● The maximum file size is defined by the NFS protocol version used for NFS connections and by the file system of exported directories on your PC.


















13. Startup

This chapter describes how to use the Startup application supplied with XSecurePro.

Startup is a program for automating host access with using the REXEC, RSH, RLOGIN, or Telnet protocol. REXEC and Telnet operations may be done either by direct access to a remote host or through one of the established SSH1/SSH2 protocol connections as well.

By using the Startup program, you can:

● Enter one or more commands in a single line and execute them on a host

● Run a local startup file (with a sequence of executable commands) on a host

● Enter a command line to run a local executable file (e.g., telnet, local X clients, etc) and execute it on your PC

● Create/save/select/remove/open/execute startup jobs.

Startup job is a task with a certain set of parameters (start method, login information, command line, settings). You can create a job (i.e. store current parameters under a certain name). A job may be launched by clicking on its icon.

In order to use Startup, your host system must support the REXEC, RSH, or RLOGIN protocol. Besides, you need to know the following about any host you want to connect to:

● For REXEC or RLOGIN method, your user ID name and password.

● For RSH method, your user ID name. Some hosts require your PC to be authorized before using RSH, as it does not require a password. On UNIX systems, you need to add your PC name to the /etc/hosts.equiv and $HOME/.rhosts files on your host.

● Either the network name or address of the host.


















Running Startup with Command Line Parameters

The 'xini' parameter

You can launch Startup with the 'xini' command line parameter:

PATH\xstartup.exe -xini <IniFilePath>

where <IniFilePath> specifies a full path to a specific ini-file and PATH indicates your XSecurePro home directory.

This feature allows you to run several Startup sessions each with its own ini-file (i.e. settings).

In order to do so, you can create a new Startup shortcut (e.g., in the XSecurePro Programs' folder) and fill in the Target field in Properties of it with the command. For example, the Target field in Properties of the Startup shortcut might contain the following line:

"PATH\xstartup.exe" -xini myxwp1.ini

By default, the field contains a call of Startup with no arguments, and the xwp.ini file will be used in this case.

To create your specific ini-file, you can copy the xwp.ini file and then change required parameters with the Startup utility by starting it with the command line parameter.

The 'lxdn' parameter

The "-lxdn [<DisplayNumber>]" command line parameter is used to set up the "$(DISPLAYNUMBER)" macros (for the DISPLAY session environment variable if a remote daemon supports it). This provides correct X11-forwarding (if set).

The "-lxdn" option means looking up running XServer (i.e., Startup understands the local XServer's "DynamicDisplayNumber" mode and correctly looks up running XServer). In this case, XServer must already have been started.

The 'mout' parameter

The "-mout [<outputfile>]" command line option is used to provide a "readable" text-tracing to the "outputfile" log-file for your session.


The 'log' parameter

The "-log <LogLevel>" option is used to set up the level of tracing (0..7).

Also, you can set up SSH-tracing by adding the "LogLevel=7" line in the "[tSSH2Pro]" section of the tsspro.ini file.

















The Settings Option

You can specify the terminal emulation settings for the current connection by choosing the Settings item on the Options menu from the main window.

Also, you can click the Settings button in the Telnet Connect Host dialog box where you can also make some initial settings for your session (that are described in subsection Details of a Session in section Starting and Terminating Telnet_SSH).

The Telnet Settings window presents you with a dialog of six tabs that allow you to view and modify the current terminal emulation settings:

● The Keys Tab● The Type Tab● The Text Tab● The Text Tab for the XTERM Type● The User Defined Tab● The Logging Tab● The ExtScreen Tab


















The Keyboard Mapping Option

By using the Keyboard Mapping Option (i.e. keymap editor invoking), you can load, change (re-define keys and create a new keyboard layout), and save any keyboard definition file.

Keyboard files are text files that define the X Protocol Key Symbols (Keysyms) which are mapped to keys on your keyboard. By default, they have the extension KMF, and are located in the home directory. You specify the KMF file to be used by all XSecurePro's programs in the XSettings window.

The keyboard mapping file format uses scancodes which allow the terminal to transmit make and break codes for each keystroke corresponding to the hardware scan codes used by PC keyboards (scan set 1). Make means when the key is pressed; break means when the key is released. The Keyboard Mapping File Format is described in Appendix A.

The Keyboard Mapping dialog box of the keymap editor allows you to map Keysyms, Characters, or Compose Key Sequences to existing keys on your keyboard.

Keysyms is the encoding of a symbol to a key that exists on a physical keyboard.

Compose Key Sequences are key combinations to produce special Keysyms such as accented characters. These Keysyms are generated by typing two keystrokes. The first key is known as a composing key. Each Compose Sequence consists of two key combinations which generate a new pseudo key.

Modifiers are keys that modify the action of other keys. They are not to be confused with a Keysym. In X Keys they include Shift, Lock, Control, and Mod1 through Mod5. Mod1 through Mod5 are the logical keynames for modifier keys that vary from workstation to workstation. Caution should be used when assigning modifiers to latching keys (NumLock, ScrollLock, or CapsLock). Modifiers mapped to these keys should not be used to modify keys in compose sequences.


The upper portion of the Keyboard Mapping dialog box contains a standard keyboard layout. The currently loaded keyboard mapping file name and the terminal emulation mode are displayed at the top of the window.

On the KeyPad group box, the KeyPad layout is shown according to the PC Layout and VT Layout radio buttons states. You can toggle between them to change the KeyPad layout.

NumLock

If you enable the NumLock check box, the numeric keypad keys will work as they normally do on your PC (local latched mode). If this option is not checked, the behavior of NumLock is determined by the remote host.

Load

When you press this button, the Open standard dialog box to open files appears, allowing you to select and load a keyboard mapping file for viewing and modifying.

Save As

When you press this button, the Save As standard dialog box to save files appears, which allows you to save your current keyboard mapping under a new filename.

Select Function type

On this list box, you can select one of the function types: XK_symbol, Character, or Composer to display all values available for it in the Function list box.

Function

On this list box, you can select a value for:

● Assigning it to a key with the Set button● Modifying it with the Edit function button.

If the Function type selected is XK_symbol, a list is displayed containing all of the XKeysyms available.

If the Function type selected is Character, a list is displayed containing all of the characters available (including accented characters) with its (decimal/hex) keycode pairs.

If the Function type selected is Composer, a list is displayed containing all of the Compose Key Sequences available.

Set

When you click a key on the keyboard layout, it appears in the Current Key group box with its current definitions:

● Normal (unshifted/unmodified)● Shifted● Modified (with the Alt GR key).

When you have a value highlighted on the Function list box (of type: XK_symbol, Character, or Composer) and a key selected on the keyboard layout, you can press the Set button to change current values assigned to the key and displayed on the Current Key group box to the new value (according to the radio buttons' states).

Undo

Use this button to immediately restore the previous key value every time you press the Set button.

List Assigned Functions

When you press this button, a dialog box appears that allows you to view a list of functions already assigned to functional keys (for the current terminal emulation mode). The list contains function names (X Keysyms), function values (code sequences), and comments on them.

Edit function

When you have a highlighted function of either the XK_symbol or Composer type, you can press the Edit function button to change the value to define a new key sequence for the function (and current terminal emulation mode). The New value dialog box will appear on your screen.

The Function group box shows the currently selected function.

Value

This edit field is used to enter a new string for the selected function. The string can include decimal codes (in the range of 0...255) separated with the comma character (as in the List Assigned Functions dialog box). The string should be in valid KMF format described in Appendix A.

Preview

This field displays a comment value for a selected function.

Comments

Use this field to enter a new comment for the function you define.

Set

This button stores new values you entered and exits the dialog.

Cancel

You can cancel any changes you made to the dialog box by clicking on this button.

















The Keys Tab

If Enter is pressed

Options in this group box define the end-of-line sequence sent when you press the Return or Enter key.

If Backspace is pressed

Options in this group box specify whether the Backspace key will be interpreted as Erase Character, Backspace, or Delete.

Add LF after CR received

This option allows you to modify (or not) the CR code received over the network.

Auto wraparound

If this check box is enabled, input text will be automatically wrapped on the next line when your


string is too long (i.e. any characters received when the cursor is at the right margin will be displayed on the next line).

Otherwise, input is stopped so you cannot enter more characters (i.e. any characters received when the cursor is at the right margin will be displayed just to the left of the right margin, replacing the current character displayed there).

Keyboard Layout

Options in this group box specify which keyboard layout will be used: PC layout or VT layout.

Local Echo

Some Telnet daemons may not support the standard Telnet protocol (and do not send a symbol of a pressed key). With the Use Local Echo check box enabled, you can display a key character regardless response from that Telnet daemon.

















The Type Tab

Terminal Refresh

This group box allows you to change values of parameters that control the screen buffer output and modify the characteristics of your keyboard.

The Time delay (msec) parameter sets the time interval (20...1000) that defines when to display lines with character(s) received.

The Screen Renovation Rate parameter sets the ratio (5%...100%) of screen changes (e.g. characters entered or modified) to full screen that defines when the screen area modified will be re-displayed.

Terminal Type

This option allows you to change emulation modes for the Telnet_SSH session by selecting one of the available modes from the Terminal Type list. The mode must correspond to that assigned in the TERM() command when logging in. Telnet_SSH adjusts your system so that your computer, keyboard, and terminal perform just as the specified terminal does. The modes are popular control


sets used in terminals originally manufactured by Digital Equipment Corporation (DEC). If you are not sure which terminal to select, select VT-100 (ANSI escape sequences).

















The Text Tab

You can specify the lines of text that you want to be retained in memory so that you can scroll through it in the window. Options in this group box let you specify the number of lines (24/36/48) and columns (80/132) that will appear in the Telnet_SSH window.

DRCS 8-bit

When this radio button is enabled, you define to work in the 8-bit environment and send the 8-bit control sequences and graphic characters (Multinational character transmission mode), including supplemental characters.

In this mode, you can download soft character sets from the host system into the terminal. The soft character set is also known as a dynamically redefinable character set (DRCS). This feature lets you design your own soft character sets for use with the terminal.

You can use the DECDLD control string command to down-line load one or more characters of a specified 94- or 96-character DRCS with a specified logical pixel pattern.

NRCS 7-bit


When this radio button is enabled, you choose to work in the 7-bit environment only. Select one of the 7-bit character sets from the National Replacement Character Sets (NRCS) pull-down list box to allow for country/region's replacement characters to be sent in the 7-bit escape/control sequences (National character transmission mode).

The following NRC sets are available:

● ASCII● DEC Special Graphics● DEC Supplemental● British● Dutch● Finnish● Norwegian/Danish● Swedish● French● French Canadian● German● Italian● Spanish● Swiss

In VT100 mode, VT52 mode, or when 7-bit NRCS characters is selected (through Set-Up or the DECNRCM command), only ASCII, NRC sets, and DEC Special Graphic characters are available.

Default Font

Characters in the Telnet_SSH window appear in the specified font, size, and colors. Options in this group box allow you to change font parameters used to display text in the Telnet_SSH window.

Browse

When you press this button, the Font standard dialog box appears. This dialog box changes the font name, style, and size of text displayed in the Telnet_SSH window. Also, you can choose a desired font script, color, and effects (strikeout and underline).

When you press the Background button, the Color standard dialog box appears. You can define your color for your background. The Colors tab allows you to customize the color of your screen by emulating the color of the host's attributes. The colors you set in this tab are not altered by the colors settings you make in the Windows Control Panel.

















The Text Tab for the XTERM Type

You use this tab to select font and specify screen size. Also, you can choose one of the three modes to define appearance of your font against window size (for the XTERM terminal type only).

The XTERM terminal emulation provides the 16-colors mode instead of B/W one.

Rows

This field lets you specify the number of rows that will appear in your emulation window.

Columns

This field lets you specify the number of columns that will appear in your emulation window.

The Set Window Size Box

In this box, you can select one of the three modes to define appearance of your font against window size.


● StandardThe row and column numbers define the size of your actual screen (see section The View Menu). The values are read in from the ini-file (first from the terminal definition file, Terminfo.ini).

In this mode, your initial window size will only be defined by the screen size and font size selected. The window displays scrollbars when its size is less than that of the screen.

The Wide screen check box toggles the number of columns between 80 and 132.

● Change WinSizeThe row and column numbers you specified define the size of actual screen (see section The View Menu). You may type in up to 1024 rows of 132 columns each. In this mode, font appearance will not be changed when you change your window size. The window displays scrollbars when its size is less than that of the screen.

With the Fit to screen check box selected, an application window is fully displayed on the PC's screen (i.e., it does not cross screen boundaries). If necessary, Scroll Bars are created.

With the Dynamic resize check box selected, the "no scrollbar" mode is provided. The actual Rows and Columns numbers are dynamically being changed while window resizing.

● Change Font SizeThe row and column numbers you specified define the size of actual screen (see section The View Menu). You may type in up to 1024 rows of 132 columns each. In this mode, font appearance will be changed according to your window size. The window displays the entire screen.

With the Proportional check box selected, the vertical dimension will only define font appearance. Otherwise, both dimensions of your window will define it.

















The User Defined Tab

This tab allows any functional key to be programmed with a user-defined sequence. User-defined keys (UDKs) are a subset of functional keys.

The UDK group box contains a list box with currently defined keys for a current emulation mode. This box allows you to map key symbols to the Unshifted, Shifted, Mode Switched, and Shift-Mode Switched states of the key. You can select a key symbol and then clear (with the Clear button), define or re-define its function value (in the Definition edit field).

You can use UDKs like a macro defined for a functional key: whenever you want to forward a user-defined control string to a host you press the key combination to activate the value. (Also see the List Assigned Functions dialog box in the Keyboard Mapping option below for already defined functional keys.)

Note: some function key combinations are reserved by MS Windows and cannot be redefined.

Upon terminating Telnet_SSH sessions or pressing OK, UDKs are stored in the terminfo.ini file (in the emulation mode section; see Appendix B for details), so they will be defaults for the next session when the file will be read in.


Lock against future definition

Use this check box to lock/unlock UDKs listed against future redefinition (from a remote host).

Definition

This edit field is used to enter new control string codes for UDKs. The string can include any combination of escape sequences, control sequences, or text (without any separating character). The string should be in valid format for the terminal emulation mode. You can scroll the field left or right as needed to allow longer strings to be entered.

Set

This button assigns the value entered in the Definition field to the UDK currently selected in the list box (for the current terminal emulation mode). This key combination will activate the value whenever it is pressed.

Clear

This button removes a value for a currently selected UDK.

Clear All

Click this button to delete the mapping for all UDKs listed.

OK

Pressing OK saves current UDK settings and quits the dialog box.

Cancel

You can cancel any changes you made to the dialog box by clicking on this button.

















The Logging Tab

The Session logging Box

These radio buttons control the amount of log output you store in a log file for your session.

Logging turned off

With this option on, no log file is used and no log output is stored.

Log printable output only

With this option on, only printable log output is stored in a log file you specified (i.e., without escape sequences).

Log all session output

With this option on, all log output is stored in a log file you specified (i.e., with escape sequences).


The Log file name Box

This is the actual setting if logging turned on.

In the entry field, you can enter a name for the log file to store data for the session.

The Browse button can help you locate and select a desired file.

The If log file already exists Box

These are the actual radio buttons if logging turned on.

Always overwrite it

With this option on, a new log file for your session will overwrite one that already exists.

Always append to the end of it

With this option on, a new log data will append to the end of the log file that already exists.

















The ExtScreen Tab

The Buffer Size Box

In this box, you specify the amount of memory that will be allocated and used for output.

Default size (4 x 1024 lines)

With this option on, the default size for the output buffer will be used.

Customer size

With this option on, you must specify a number of blocks (each of 1024 lines) for the size of the output buffer that will be used for your session.

Hot Key


With this check box selected, you can choose a hot key combination you will use to change to navigation mode to view the output buffer.

Warning mode

These radio buttons control the way the program will let you know that you change to the actual screen while navigating through output buffer.

Dialog Mode

With this option on, a dialog box will appear.

Bell

With this option on, a system bell will sound.

No External Signal

With this option on, the program will not warn you that you change to the actual screen while navigating through output buffer.

















Details of a Session

Clicking the Details button in the Telnet Connect Host dialog box will change it into the following form:

Clicking the Details button once more will change the dialog box into the short form.

Clicking the Settings button will display the Telnet Settings dialog box. (Refer to subsection The Settings Option in section The Options Menu.)

Pressing OK will store current settings (for the next session) and will establish a connection, using them.

You can cancel any changes you have made to the dialog box by clicking on Cancel. This will also close the dialog.

The Forwarding Box

If you select the Disable Forwarding check box then the direct access insecure mode will only be


used for Telnet operations (i.e., without forwarding).

If you want Telnet operations to be done in secure connection mode, clear the Disable Forwarding check box to use forwarding settings during your new SSH1/SSH2 session.

See subsection The Forwarding Option in section The Options Menu for details on how to specify local/remote host/port forwarding.

The Logging file Box

In the entry field, you can enter a name for the log file to store data for the session.

The Close Session on Exit Box

In this box, you choose a mode of closing your session.

Always

In this mode, the session will always be terminated on exit or on Disconnect.

Restart On Exit

In this mode, the session will be restart on exit (i.e., by displaying the Telnet Connect Host dialog box).

Exit on Disconnect

In this mode, the session will be closed on Disconnect.

The ProFiles Box

In this box, you can manipulate with profiles (i.e., saved session settings).

In the ProFiles list, names of available profiles are displayed. In the entry field above, the name of the last loaded (by Load) profile is displayed.

When you start up the program, the settings of the last run are loaded from the ".." profile and are made as current settings. On closing a session, its current settings are automatically stored in the ".." profile. You can Save, Load, and View this profile, but cannot Delete it. Note that Load will change its contents.

Save

In the entry field, you can type in a name for the profile you want to save. The Save button saves current settings in the profile specified and adds its name to the Profiles list.

Load

This button loads the profile you select from the Profiles list, makes its settings as current ones, and displays its name on the entry field.

Delete

This button will delete the profile selected from the Profiles list.

View

This button displays in Notepad the profile (i.e., its set of settings) you select from the Profiles list.

















The "[TELNET]" Section of the ini-file

The "[TELNET]" section of the ini-file may have the following entry lines you can customize for particular needs and applications.

ALTforEMACS=1

This setting allows the ALT key to be used in EMACS.

ExitOnDisconnect=N

This option is used to control the session's restart/completion mode, with N providing the following:

● ExitOnDisconnect=1suppresses starting the new Telnet session;

● ExitOnDisconnect=2suppresses issuing the "Connection lost" message (only writing it into the telnet_s.out file);

● ExitOnDisconnect=3suppresses issuing the "...open forwarded connections..." message (only writing it into the telnet_s.out file).

FineSelectMode=1

This setting is used to set up the Fine Selection mode. In this mode, all "touched" symbols are included in a selection area.

QuickClipBoard=1

This setting is used to set up the Quick Copy to Clipboard mode. In this mode, a selected area is copied to Clipboard immediately on release of the left mouse button.

SelectRect=0

This setting is used to set up the Selection-by-filling mode that provides text highlighting selection in traditional manner.

CtrlCVmode=N

With N=3, this option specifies to use the traditional key combinations, "Ctrl+C"/"Ctrl+V", for Copy/Paste operations in the session.Caution: in this mode, you cannot send another "traditional" key combination, "Ctrl+C" (i.e., Break


Event), to remote applications.

With N=5, this option specifies to use the default key combinations, "Ctrl_L+Shift_L+C"/"Ctrl_L+Shift_L+V", for Copy/Paste operations in the session.

















Running Telnet_SSH with Command Line Parameters

The 'host' parameter

You can launch Telnet_SSH with the 'host' command line parameter to avoid interactive input of it. 'Host' may be either a host name or IP address for the remote machine you want to connect to.

Examples:

PATH\Telnet_s.exe u2-1

PATH\Telnet_s.exe 192.168.136.223

where PATH indicates your XSecurePro home directory.


You can launch Telnet_SSH with the 'xini' command line parameter:

PATH\Telnet_s.exe -xini <IniFilePath>

where <IniFilePath> specifies a full path to a specific ini-file.

This feature allows you to run several Telnet_SSH sessions each with its own xwp.ini file (i.e. settings).

In order to do so, you can create a new Telnet_SSH shortcut (e.g., in the XSecurePro Programs' folder) and fill in the Target field in Properties of it with the command. For example, the Target field in Properties of the Telnet_SSH shortcut might contain the following line:

"PATH\Telnet_s.exe" -xini myxwp1.ini

By default, the field contains a call of Telnet_SSH with no arguments, and the xwp.ini file will be used in this case.

To create your specific ini-file, you can copy the xwp.ini file and then change required parameters with the Telnet_SSH utility by starting it with the command line parameter.

The 'trace' parameter


You can launch Telnet_SSH with the 'trace' command line parameter

PATH\Telnet_s.exe -trace

to collect debug information in the telnet_s.out file in the home directory.

The 'ssh1' and 'ssh2' parameters

You can launch Telnet_SSH with the 'ssh1' or 'ssh2' command line parameter

PATH\Telnet_s.exe –ssh1orPATH\Telnet_s.exe –ssh2

to run it using the SSH1 or SSH2 protocol mode respectively over an insecure channel to provide secure communications between your PC and the remote server.

The 'lxdn' parameter

The "-lxdn [<DisplayNumber>]" command line parameter is used to set up the DISPLAY session environment variable if a remote daemon supports it. This provides correct X11-forwarding (if set).

The "-lxdn" option means looking up running XServer (i.e., Telnet_SSH understands the local XServer's "DynamicDisplayNumber" mode and correctly looks up running XServer).

The 'mout' parameter

The "-mout [<outputfile>]" command line option is used to provide a "readable" text-tracing to the "outputfile" log-file for your session.

The 'log' parameter

The "-log <LogLevel>" option is used to set up the level of tracing (0..7).

Also, you can set up SSH-tracing by adding the "LogLevel=7" line in the "[tSSH2Pro]" section of the tsspro.ini file.

The 'prof' parameter

With the "-prof profilename" command line option, you can initialize a session that will first read in the profile specified and then use its data for the session.

















Terminal Emulation in Telnet_SSH

The Telnet_SSH program can emulate XTERM, AT386, ANSI, VT52, VT100, VT125, VT220 and VT240 terminals. The terminfo.ini file describes the capabilities of these terminals. This description contains control sequences for them and is very similar to the TERMINFO source code of the UNIX system. So users can edit the file to suit to the special environment.

By editing the terminfo.ini file, users can define the terminal type, the screen size (the number of lines and columns), the number of colors, the color palette (i.e. RGB values for each color number), sequences to be transferred to remote hosts for each user-defined key on the keyboard.

Appendix B contains detailed information on how to describe the terminal emulation capabilities.


















8. FTP/SFTP/NFSBrowser

This chapter describes how to start and use the FTP program supplied with XSecurePro.

The FTP program is a client implementation (i.e. a user interface) of standard File Transfer Protocol. FTP allows you to transfer both text and binary files and directories between your PC and remote computers running the server implementation of File Transfer Protocol (on multiple server platforms) over the Internet and intranets.

By using the FTP program, you can:

● Set up parameters and modes for operations

● Navigate through directory structures on your PC or remote FTP servers

● Make/Remove a local/remote directory

● Select directories and files in a local/remote directory

● Copy/Rename/Delete selected local/remote files and directories

● Transfer selected files and directories between two remote FTP servers

● View a local/remote file (in Notepad)

● Append a file from your PC to a file on a remote FTP server

● Execute FTP commands on a remote FTP server.

FTP operations may be done either by direct insecure access to a remote host or through one of the established SSH1/SSH2 protocol connections as well. You can access resources you need from behind your corporate firewalls. Also, FTP supports the SFTP mode.

While you are connected, you can perform a number of tasks (commands) on the remote computer (FTP server) by using its various options.

FTP must run on a machine that is configured for TCP/IP network communication or Internet access. Access can be gained through Winsock and the use of any dial-up provider, a Remote Access Server (RAS), or a direct connection via a local area network that supports TCP/IP. In order for FTP to communicate with a remote computer, that computer must have a server implementation of FTP (FTP server based on the TCP/IP transports).

You can be connected to only one or two remote computer at a time during a FTP session. However, you can run multiple FTP sessions (FTP clients) simultaneously in separate windows, with each session connected to a different host.


















The Forwarding Option

Port forwarding is the concept of connecting a logical port on a local machine to a port on a remote machine over a secure (encrypted) channel. All requests for services sent to the local port are then forwarded across the secure channel to the corresponding port on the remote machine.

Port forwarding of arbitrary TCP/IP connections over the secure channel can be used for secure connections to electronic purses or going through firewalls. Port forwarding is a powerful tool that allows you to secure TCP/IP traffic by using Telnet_SSH' SSH1/SSH2 protocol support. This means that you can encrypt application data for insecure network traffic using protocols like SMTP, POP, and IMAP.

Telnet_SSH supports X11 forwarding. This feature allows X Window traffic between the X server and X client (forwarding X Window packets through the SSH session) to be encrypted.

In general, with any port forwarded by Telnet_SSH for an application, the application needs to be configured to use 127.0.0.1 (otherwise known as "localhost" or "loopback") as its application server address. Hostname and port configuration needs to be done in both Telnet_SSH and the client application (e.g., e-mail). After connecting with this session, the client application traffic is encrypted to the SSH server as long as Telnet_SSH is running. If the connection to the SSH server is broken or closed, the forwarded ports will no longer be forwarded, and the client applications may receive an error when they try to connect to the local port.

It is important to understand that the client data is only encrypted between the machine that Telnet_SSH is running on and the SSH server that Telnet_SSH is connected to. Any data moving from the SSH server across the network to another server is not encrypted.

The Forwarding option presents you with the Forwarding Setup window (for the SSH1/SSH2 protocol mode):


The Port Forwarding Box

Add

This button allows you to add entries into the Port Forwarding list. When you press the button, the empty SSH Port Forwarding window will appear, and you can specify new port forwarding settings.

Edit

This button allows you to modify an entry selected on the Port Forwarding list. When you press the button, the SSH Port Forwarding window will appear, and you can modify current settings for the entry.

Remove

This button allows you to remove selected entries from the Port Forwarding list.

The X Forwarding Box

Display remote X applications on local X server

This check box specifies whether X11 connections will be automatically redirected over the secure channel. This feature allows X Window traffic between the X server and X client (forwarding X Window packets through the SSH session) to be encrypted.

X11 forwarding is the process of transporting X11 data over an encrypted channel from a remote machine to a local machine. In this mode, the SSH server automatically sets the DISPLAY environment variable on the server machine, and forwards any X11 connections over the secure

channel. Fake Xauthority information is automatically generated and forwarded to the remote machine (your PC); the local client automatically examines incoming X11 connections and replaces the fake authorization data with the real data (never telling the remote machine the real information).

Note: the X Forwarding option allows Telnet_SSH to accept X11 data from the remote machine and forward it to the X server running on the local machine. Telnet_SSH does not work as an X server. The local X server must be running before any X11 sessions can be displayed. If you are using Xhost authority access on the local X server, you will need to add address 127.0.0.1 (otherwise known as "localhost" or "loopback") to your server's Xhost list.

The DISPLAY variable indicates the location of the X11 server. It is automatically set by SSH to point to a value of the form "hostname:n" where hostname indicates the host where the shell runs (the server machine), and n is an integer greater than zero (a display number). This is normal, and happens because SSH creates a "proxy" X server on the server machine for forwarding the connections over the encrypted channel. The SSH server uses this special value to forward X11 connections over the secure channel. The user should normally not set DISPLAY explicitly, as that will render the X11 connection insecure (and will require the user to manually copy any required authorization cookies).

If the user is using X11 (the DISPLAY environment variable is set), the connection to the X11 display is automatically forwarded to the remote side in such a way that any X11 programs started from the shell (or command) will go through the encrypted channel, and the connection to the real X server will be made from the local machine.

When you press the Add or Edit buttons in the Forwarding Setup window the SSH Port Forwarding window will appear:

This dialog box lets you specify data for port forwarding. Ports may be defined either by their port number or by their service name.

Arbitrary TCP/IP ports can be redirected through the encrypted channel in both directions (e.g., for e-cash transactions).

Forward local port

Specifies that the given TCP/IP port on the local (client) machine be forwarded to the given host and

port on the remote side. This works by allocating a socket to be listened port on the local side, and whenever a connection is made to this port, the connection is forwarded over the secure channel and is made to host:hostport from the remote machine.

When enabled, this radio button allows you to enter the local port in the entry field or select its service name from the corresponding drop-down list box.

To remote machine

Enter the remote host name or IP address.

port

Enter the remote host port in the entry field or select its service name from the corresponding drop-down list box.

Forward remote server port

Specifies that the given TCP/IP port on the remote (server) host be forwarded to the given host and port on the local side. This works by allocating a socket to listen to port on the remote side, and whenever a connection is made to this port, the connection is forwarded over the secure channel, and is made to host:hostport from the local machine.

When enabled, this radio button allows you to enter the remote port in the entry field or select its service name from the corresponding drop-down list box.

To local machine

Enter the local machine name or IP address.

port

Enter the local machine port in the entry field or select its service name from the corresponding drop-down list box.

The Save FWD Settings Option

When you press this button (for SSH1/SSH2 protocol mode), the Forwarding settings you have made will be stored. They will take effect immediately for the current connection, otherwise - with the new session.
















8. FTP/SFTP/NFSBrowser < previous | content | next >

Starting and Terminating the FTP Program

You can start the FTP program by double-clicking on the FTP icon in the XSecurePro Programs' folder:

The main FTP window will appear on your display:


In order to terminate FTP, choose Exit from within the Server menu. It is not necessary to close a connection before terminating FTP; the system will shut everything down for you.

















The Main FTP Window

On the upper portion of the main window, there is a Toolbar displaying short-cut buttons that allow you to access commonly-used functions that appear on the FTP menus:

● Disconnect● ASCII type transfer● Binary type transfer● Copy selected file(s)● Copy file with another name● Append file to another● Reget or Reput selected file● Rename selected file● Delete selected file(s)● Save current settings● View selected file to Notepad● Update panels● Help contents

The left part of the FTP main window consists of two list boxes displaying a current local directory tree structure and a file list for the path above. You can select local files for operations here.

The right part of the FTP main window contains four tabs that house the various program options. These tabs are: Login as, Remote files, Settings and Quote.

The Login as tab is for making connection to a FTP server.

The Remote files tab displays the directory structure of the currently connected server. The window is blank unless FTP is connected to a server, or a server's cached directory information is displayed. Navigating through the server's various folders or directories is accomplished by clicking individual folders with the mouse. Here you can browse your active connection and select directories and files for operations.

When you press the right mouse button on the empty space inside the tab, the drop-down menu will appear:


You can use its available options as follows:

View

Allows viewing the contents of a current directory as a set of icons, as a list of icons, or as a list of files with its detailed information.

Arrange Icon

Allows you to sort icons in a current directory by name, type, size, or date.

Show hidden files

Allows viewing all kinds of files in a current directory.

New Folder

Creates a new directory in a current directory.

Update

Updates the listing of a current directory.

Change Directory

Changes directory to one you choose in a separate menu.

The Settings tab is used to configure transfer options.

The Quote tab allows you to control a FTP server by command lines.

You can resize file panels and sort files by clicking on the column name at the top of the file listing.

On the lower portion of the main FTP window, the message box displays a listing of all commands sent to the remote server and messages on how the FTP commands are executed. The log can be useful for debugging or troubleshooting purposes. You can scroll messages up and down, select them, and place the data in a log-file for future reference (by pressing the right mouse button and choosing the option). The Debug mode allows you to keep track the FTP session with more details.

The status line displays a current path (if exists) to remote files, the L/R character to indicate the (Local/Remote) active panel for operations, and descriptions of the program's activities during its connection or file transfer operations.

















The Server Menu

Disconnect

Closes an active connection with a FTP server (see Disconnecting From FTP server for details) displayed on the Remote files tab.

FXP/FTP Connect

Connects you with a FTP server using the Login as tab (see Connecting to the FTP Server) and then displays your home directory structure on the left panel of the main window. This mode lets you make directory/file operations on and between two remote FTP servers.

FXP Disconnect closes an active connection with a FTP server displayed on the left panel and takes you back to your local directory structure.

New Folder

Makes a directory on your PC or a FTP server (see Making Directory for details).

Remove Folder

Deletes a selected local/remote (empty) directory (see Removing Directory for details).

Copy Directory

Copies a selected directory to or from the host (see Copying Directory for details).


Update

Refreshes the contents of the list boxes. Use this option to reload the file listing of the current directory. This option is only available if a connection is active. You may also refresh the current directory listing by pressing the Update panels button on the tool bar.

Exit

Exits the FTP program.

File Functions

This sub-menu has the following items for file management operations:

Copy Copying selected files

Copy As Copying a file with changing its name

ReTransfer Re-getting or re-putting a file

Append Appending one file to another

Rename Renaming a selected file

Delete Deleting selected files

Preview Viewing a selected file

















The Options Menu

ASCII type

Toggles to the ASCII transfer type.

Binary type

Toggles to the Binary transfer type.

Enable Save Password

If enabled, password will be saved on exit.

Save Settings on Exit

If enabled, settings will be saved on exit.

Save Settings Now

Settings are saved immediately.


















Performing File Transfer

A file transfer downloads files from a remote machine to your local PC, or uploads files from your machine to a remote one. You can also delete and rename files on, and append files to, a remote machine.

Before any file transfers can take place between your machine and the desired server, the server's information must be entered. When connection is open, FTP allows you to perform directory and file management operations on the remote computer. FTP allows you to perform basic directory and file management operations on your PC as well. If no connection to a remote computer is open, FTP will then recognize local commands only.

While you are connected, you can perform a number of tasks on the FTP server, using various server options.

Next you can select files for transfer. Based on the files you have selected, you set up transfer options. Transfer options control the format of the file transfer, and whether you will be prompted before operations. With transfer options set, you can perform file management operations.

While transferring multiple files, each copy is given the same name as the original. Filenames are sent in lowercase.

When you are done, you can disconnect from the FTP server.


















Connecting to the FTP Server

To create connection between your PC and a remote computer, carry out the following on the Login as tab:

1. Select a FTP server (Host ID) in the list box of hosts (defined in your hosts file). Alternatively, you can enter the host address for the server (which can be either the DNS entry or its IP address) in the HostID edit field.

Note that a host name you specify here may not result in the same remote host name due to different name-address DNS translations in different LANs. You should specify the host name or IP address for a remote host in a LAN that are known inside that LAN for that host.

2. In the User Name edit field, enter your login name that is required by the selected server to access your FTP account.

If you do not have an account with the selected server, and it accepts anonymous FTP requests, enable the Anonymous check box.

3. In the Password edit field, enter the password that is required by the server to access your FTP account. The characters of the password will appear as asterisk (*) symbols for security purposes unless you chose the anonymous login option.

4. Specify your Account (if required).


If the Account field is specified, the account command will be relayed to the remote server after the login sequence is completed if the remote server did not require it for logging in.

5. In the Initial Directory field, enter the path on the server in which you want to begin. If this field does not contain a value, the root directory will be listed by default.

6. Select an operating system type of the remote computer from within the Server Type list box. The UNIX system type is used by default. (Currently supported types are: UNIX, DOS, VMS, MVS, OS/2, SI NT FTPD, IBM VM, AS/400).

7. Choose a protocol type for connection. - Select FTP to use the standard FTP protocol for connection with a remote FTP server. - Select SFTP mode to use the SFTP protocol for connection with a remote SFTP server. - Enable the FTP via XWP SOCKS4 check box if you want FTP operations to be done through one of secure connection channels. Otherwise, disable it if you want to use direct insecure access to remote hosts. See Notes below. - Select NFSbrowser to use the standard NFS protocol for connection with a remote NFS server.

8. Click the Connect button to establish the connection.

Alternatively, you can select a proper connection profile name (under which you may earlier have saved your connection settings, so you need not set up them each time you want to connect to the remote host) and press the Connect button (see the Profile section below).

As a result of successful connection with your FTP server, you will see your home directory structure on the Remote files tab.

In the FXP/FTP Connect mode, as a result of successful connection with your second FTP server, you will see your home directory structure on the left panel.

Notes:

The SSH File Transfer Protocol (SFTP) provides secure file transfer (and more generally file system access) functionality over any reliable data stream, such as a channel in the SSH2 protocol. It is the standard file transfer protocol for use with the SSH2 protocol.

This protocol assumes that it runs over a secure channel, and that the server has already authenticated the user at the client end, and that the identity of the client user is externally available to the server implementation.

With the FTP via XWP SOCKS4 check box enabled, the SSH Forwarding window will appear when you click the Connect button:

that contains a number of actual SSH1/SSH2 connections you have previously established (for example, by the SSH1 or SSH2 Client of the Telnet_SSH program). (See Starting an SSH Session in the Starting and Terminating Telnet_SSH section on how to establish secure connections). The Refresh button allows you to renovate the list. From within the list, select a desired remote host (active SSH server) for using SSH connection and press OK.

The "Dynamic Port Forwarding" feature of the Telnet_SSH/SSH1 or Telnet_SSH/SSH2 Client and FTP Client will automatically be used for both FTP control and FTP data connections, so you need not set up any port forwarding manually. In the message box, you can see what ports will be used for FTP control and FTP data connections in the current FTP session due to Dynamic Port Forwarding (e.g., 8009 and 8010 respectively). This gives you a local representation of your remote FTP connection.

In this case, the Passive Transfers mode will always be enabled since your FTP client will try to connect to the FTP server with using a locally created listening socket.

If the FTP server and SSH server you are using in a FTP session are on the same remote host then the HostID field can contain "localhost" or "127.0.0.1". This is more preferable than its actual IP address in most cases (but depends on how the host has been configured).

You can use the netstat utility to watch your network connections.

Example of initiating the FTP session via SSH


● your remote host is accessible from your PC● your remote host supports the FTP protocol for your PC● sshd-daemon (or sshd2-daemon) is running on your remote host● your PC is accessible from your remote host.

If OK, then you may initiate the FTP session via SSH like the following steps:

1. Initiating the Telnet_SSH session

● Start Telnet_SSH by double-clicking on the Telnet_SSH icon from the XSecurePro Programs' folder (the Telnet Connect Host window should appear)

● Choose SSH-1 (or SSH-2) in the Interface section

● Enter the network name or IP address for the remote host you want to connect to

● Change the default SSH port number if required

● Click OK to establish connection with the remote host (the SSH Authentication window should appear)

● Choose to Use plain password to log in

● Specify the login information required for your host system: User name and Password in the Passphrase field

● Click OK to log in to the remote host (the Telnet_SSH window should appear)

2. Initiating the FTP session

● Launch FTP by double-clicking on the FTP icon from the XSecurePro Programs' folder (the FTP window should appear)

● Enter localhost as the network name or 127.0.0.1 as the IP address in the Host ID field in the Login as tab

● Enter your User Name (e.g., John)

● Enter your Password required for your login to the remote system (e.g., Smith)

● Check the Use SSH Forwarding check box

● Specify other required settings and options

● Click the Connect button (The SSH Forwarding window should appear)

● Select the line with the SSH connection to your remote host from the list box under the Use SSH Forwarding check box

● Click OK.

The FTP session to the remote host will be opened through the encrypted connection. In the Remote files tab, the list of directories and files from your home directory on your remote host should be displayed.

















Disconnecting from the FTP Server

The Disconnect option is only available if a server is currently attached. Choosing this option will break the connection from the server. To close a connection to the current FTP server, you can choose Disconnect from within the Server menu. Alternatively, press the Disconnect button on the tool bar.


















Changing to a User Name

During a FTP session, you can change to another user name. This option is only available if a server connection is active. To change to another user name:

1. Select the Login as tab from the TabForm.

2. Enter a new user name in the corresponding edit field.

3. Specify a password (if required).

4. Press the Change User button to confirm your Login.

If there are problems with your Login, you will be returned to the Login dialog box and given another chance to Login. If your Login is successful, you will be returned to the FTP session.

Alternatively, you can select a proper profile name and press the Change User button (see the Profile section below).

To cancel changing user name, just select another tab from the TabForm.


















Profile

You can assign a name to the connection data set by entering it in the Profile edit field. This set includes: HostID, UserName, Password, Confirms.

The text displayed in this field can either be the profile name that is selected in the list, or it can be text that has just been entered. Click on an entry in the list to choose the profile and automatically display the related connection information for it. Any relevant data previously configured in the connection dialog for each server will be displayed after its selection from the list.

To edit an existing profile name, simply select the profile to edit from the list, then move the cursor to the point in the profile name that you wish to change, and make the desired changes.

To add a profile to the profile list, click on the Save button.

To remove a profile from the profile list, select it in the profile list box and press the Delete button.


















Transfer Options

Transfer options you may configure include the following:

● transfer mode● port number● transfer format type (ASCII, Binary)● E-mail address● confirms for Copy, Delete, Append and Overwrite operations● sound upon completing operations● security mode to login

To display current settings, select the Settings tab from the TabForm. This will bring up the tab with current options of your FTP session:

To save current settings, press the Save current settings button on the tool bar. You do not have to be connected to a server.

Setting Transfer Options

Transfer options will be in effect until you change them or close the server connection.


1. To set up transfer format type (ASCII, Binary), you can choose it from within the Options menu. Alternatively, press the suitable button on the toolbar.

If the ASCII option is selected, all transfers to or from a remote FTP server will be made in the ASCII format. This is necessary for ASCII text files on some FTP servers, but cannot be used for transfer of binary executable files, or files other than those composed strictly of ASCII text.

In ASCII mode, each LF code is changed to CRLF (when transferring from UNIX to MS Windows), and each CRLF code is changed to LF (when transferring from MS Windows to UNIX).

The Binary option makes FTP treat all transfers to and from a remote FTP server in a binary format, which is necessary for binary executable files, or very generally, for files that are not composed strictly of ASCII text.

In Binary mode, no code is changed when transferring to or from a remote FTP server (i.e., transferred "as is").

There is no special checking on the selections to determine if this is appropriate. For example, if you select a .exe file and select ASCII as the transfer type, you will not be notified.

2. To toggle the Sound upon completing operations option, press the Red Bell button on the Settings tab. This option will enable the system sound upon connect, and successful download or upload of a file or files.

3. To change the confirmation settings, check the Copy, Append, Delete or Overwrite check boxes if you want to be prompted to confirm whether to continue when you are performing the corresponding file operation.

4. To specify a port number, enter it in the edit field (if you wish to communicate via a specific port on the FTP server). Otherwise, leave this field's default as 21.

This port number will be used throughout the session. An optional port number may be supplied, in which case FTP will attempt to contact a FTP server at that port. Most servers accept FTP connection requests on port 21, but there are those that do not (for security or other reasons). Port number 21 is usually used for FTP clients.

5. When the Passive Transfers check box is disabled, then a remote FTP server will (normally) try to establish connection with your FTP client and perform operations.

When enabled, this mode makes a FTP server passive (with the PASV command) so your FTP client will try to connect to a FTP server. This mode is useful when your PC is behind a firewall or proxy server. (See section Connecting to the FTP server for more information on using standard FTP and SSH1/SSH2 connections.)

6. When enabled, the Use RSA key to login check box specifies whether to use RSA authentication. If RSA authentication is selected, you should specify a location of the identity file to be used for this process. You can enter the filename in the entry field or select it with the Private key file button.

When you press on the Private key file button, the standard Open File window will appear. You can select your identity file for RSA authentication. RSA authentication will only be attempted if the Private key file exists.

In order to use your private key, you must transfer the identity file created by the ssh-keygen utility on the SSH server machine to a secure location on your PC for this file such that you are the only individual with access to it.

Also, prior to using RSA authentication, the public key must be made available to the SSH server.

One way to transfer the identity file from the remote machine to your PC is to use FTP (in ASCII mode). Another way is to copy the contents of the identity file to the clipboard using a remote text editor and then to paste the contents of the clipboard to a file you created using a local text editor (e.g., Notepad).

















Operations with Files

Copying Files

Copying files duplicates selected files to another file system. You can copy local files to a remote system, or remote files to your PC. Copying can be carried out by using the Copy button, which assumes that you want to use the same file name, or the Copy As button, which will prompt you for a new name for the file.

Use Copy As to transfer UNIX files with a file name not conforming to DOS file naming conventions. When you have to operate with such 'specific' UNIX names, then choose NONE as the server type in the Server Type list box.

Note: Copy and Copy As can only be used with files, not directories.

To copy a file:

1. Connect to a server, using a valid server profile.

2. Navigate through either the local or remote directories to locate a file of your interest in the file list.

3. Select the file by clicking on it. A status bar letter will appear to indicate the currently active panel.

Note that Copy As can only be used with one file at a time.

If more than one file is to be selected, you can use standard Microsoft Windows' techniques to make multiple selections (with the Ctrl key for individual files, or with the Shift key for adjacent files).

4. Display a destination directory to place the files.

5. Verify that the transfer options be configured appropriately.

6. Choose the Copy selected file(s) or Copy file with another name button from the toolbar, or choose the Copy or Copy As item from within the Server/File Functions menu.

7. If the Copy confirmation is turned on, you will be prompted to confirm the operation.

If you are doing Copy As, you are always prompted for a new name and the Copy As dialog brings up.

8. If files exist with the same names as the selected source files in the destination directory and the Overwrite confirmation is on, the Overwrite dialog will bring up.

You can choose Yes to overwrite the file, or choose NO to skip copying the file.


You can choose Yes to All to overwrite the rest of selected files.

9. While the transfer is in progress, the transfer status is displayed.

If you press the Cancel button, the Copy operation will be cancelled, but any files that have already been copied will exist on the target file system.

You can Copy, not Copy As, by just dragging the selected files and dropping them onto the target panel to begin the operation.

Appending One File to Another

Appending a file concatenates it to another file. You may append a local file to a remote one.

Note: appending can only be used with files, not directories.

To append a file:

1. Navigate through your local directories tree and a file list to locate a file of your interest.

2. Select the local file by clicking on it.

3. Display a destination directory where to append the file.


5. Press the Append file to another button on the toolbar, or choose the Append item from within the Server/File Functions menu.

6. If the Append confirmation is turned on, you will be prompted to confirm the operation.

You can choose NO to skip appending a selected file.

The default is to use the same file name in the current directory on the remote file system (to which you are moving the file).

Note: if you press the Cancel button on the transfer progress dialog, your destination file will be invalid!

Renaming Files

Renaming a file changes the name of the file. Rename does not support simultaneous moving that file. You may rename both local and remote files. Rename will prompt for a new name for the highlighted file. The new name will replace the old one, providing your login grants you permission to rename files on the server to which FTP is attached.

Note: rename can only be used for files, not directories.

To rename a file:

1. Select a file of your interest in the local or remote file list. You may not select multiple files to be renamed.

2. Press the Rename selected file button on the toolbar, or choose the Rename item from within the Server/File Functions menu. The file name will turn into edit field with the file name highlighted.

3. Enter a new name for the file in the field, using standard Microsoft Windows' techniques.

4. Press the Enter key to complete renaming, or ESC to cancel it.

Deleting Files

Deleting a file removes it from its file system. You can delete local and remote files. This option will delete the currently highlighted remote files, provided that your account on the server to which the FTP program is connected permits deletion.

To delete files:

1. Navigate through either the local or remote directories to locate files of your interest in the file list.

2. Select one or several files.

If more than one file is to be selected, you can use standard Microsoft Windows' techniques to make multiple selections.

3. Press the Delete selected files button on the toolbar, or choose the Delete item from within the Server/File Functions menu. Alternatively, you can simply press the Delete key on your keyboard.

4. If the Delete confirmation is turned on, you will be asked to confirm the operation.

You can choose Yes to remove the current file.

You can choose No to skip removing the current file.

You can choose Yes to All to remove the rest of selected files.

If you press the Cancel button, the removal will be cancelled, but any files that have already been deleted cannot be restored.

Re-getting or Re-putting Files Transferred Partially

Retransfer acts like Copy except that if a selected file exists and is smaller than the file on another side, the file is presumed to be a partially transferred copy of the file from another side and the transfer is continued from the apparent point of failure. This option is useful when transferring very large files over networks that are prone to dropping connections.

To retransfer a file:

1. Select a file of your interest as for Copy. A status bar letter will indicate the currently active panel.

2. Choose the reTransfer item from within the Server/File Functions menu, or press the

Reget or Reput selected file button on the toolbar.

Previewing Files

FTP allows you to display a portion (up to the first 32Kb) of specified client or server files in the Preview window.

To preview a file, select it from a file list box and click the View selected file to Notepad button on the toolbar, or choose the Preview item from within the Server/File Functions menu.

If you are previewing a server file, FTP transfers data from the server file to a temporary file on your PC, cancels the transfer after receiving 32K bytes, and then calls the Notepad program to display the contents of the temporary file. When you close the window, temporary files are removed.

FTP always uses the ASCII file transfer method for previewing server files. Non-displayable characters in a binary file are changed to a period.

















Operations with Directories

Making Directories

You may create a directory on the FTP server or on one of your local drives. Use this option to create a new folder in the directory that is being displayed in the active panel. The remote option is only available if a server connection is active. Your user permissions must include the right to create directories.

To create a directory:

1. Navigate through either the local or remote directories to locate a directory of your interest where you wish to create a new one.

2. From within the Server menu, choose the New Folder item. The edit field will appear with the default folder name highlighted.

Also, you can create a remote directory by pressing the right mouse button on the empty space inside the Remote files tab and choose New Folder in the drop-down menu.

3. Enter a new name for the folder in the field, using standard Microsoft Windows' techniques.

Removing Directories

You may remove a directory on the FTP server or on one of your local drives. You can delete a file directory only if it is empty. Removing a directory on the FTP server is only available if a server connection is active. Your user permissions must include the right to remove directories.

To remove a directory:

1. Navigate through either the local or remote directories to locate a directory of your interest.

2. Select the directory or folder you wish to remove.

3. From within the Server menu, choose the Remove Folder item. The highlighted directory will be removed without any confirmation (if empty).

Copying Directories

You may copy a directory from your PC onto the FTP server, or from the FTP server to your local drives. The remote option is only available if a server connection is active. Your user permissions must include the right to create directories.


You can copy a full sub-tree structure (all files with all subdirectories) or the first-level files only.

To copy a directory:

1. Navigate through either the local or remote directories to locate a directory of your interest.


3. From within the Server menu, choose the Copy Directory item. A dialog box will appear on your screen prompting you to specify a destination directory and a mode of operation.

4. Specify the destination directory if it differs from the current one.

5. Check the Include Subdirectories check box if you need. If checked, this check box enables copying the selected directory sub-tree and all files from all subdirectories. Otherwise, only the selected directory and its files will be copied.

6. Click the Copy button to begin copying, or Cancel to cancel the operation.

















The Quote Tab

The Quote tab allows you to communicate with a FTP server in a command line mode while your connection to the server is active.

To dismiss the Quote dialog, just select another tab from the main TabForm.

Determining Commands the FTP Server Supports

Different FTP servers can support different subsets of available FTP commands. This may cause a server to be unable to execute certain commands.

To determine commands your FTP server supports:

1. Choose Show commands supported by the server.

2. Press Enter.

A list of commands supported by that server will be displayed in the Response field.


Getting Help on a Command

You can get help for any individual command.

To get help for a specific FTP command:

1. Choose Get help on command and enter the name for the command in the input field.

2. Press Enter.

The FTP server's help for that command will be displayed in the Response field.

Sending a String to the FTP Server

You can forward a command directly to the FTP server to execute it.

To send a string:

1. Make sure your current local/remote directories are as you need.

2. Enter a command with proper arguments in the input field.

3. Press Enter to execute the command

A response from the server will be displayed in the Response field.

Note: commands that require a data connection, such as STOR, NLST, and LIST, will not work with the current version of the FTP utility.

















Running FTP with Command Line Parameters


You can launch FTP with the 'xini' command line parameter:

PATH\ftp.exe -xini <IniFilePath>


This feature allows you to run several FTP sessions each with its own ini-file (i.e. settings).

In order to do so, you can create a new FTP shortcut (e.g., in the XSecurePro Programs' folder) and fill in the Target field in Properties of it with the command. For example, the Target field in Properties of the FTP shortcut might contain the following line:

"PATH\ftp.exe" -xini myxwp1.ini

By default, the field contains a call of FTP with no arguments, and the xwp.ini file will be used in this case.

To create your specific ini-file, you can copy the xwp.ini file and then change required parameters with the FTP utility by starting it with the command line parameter.


















The "[FTP]" Section of the ini-file

The "[FTP]" section of the ini-file may have the following entry lines you can customize for particular needs and applications.

HideDrives

You can use this setting to provide (in)visibility of your disk drives from outside. This allows you to provide policy like the Windows User Configuration -> Windows Components -> Windows Explorer Policy Settings in the Windows Server 2003.

Examples: - HideDrives= ADF - hides drives A:, D: and F: additionally (to possibly hidden ones); - HideDrives=0ADF - hides drives A:, D: and F: only. - HideDrives=0 - provides visibility of all disk drives (i.e. no hidden disk drives). This option lets you avoid influence of policy in the Windows Server 2003 to hide local hard disks for users of Terminal Services.


















9. TFTP

This chapter describes how to start and use the TFTP-client program supplied with XSecurePro.

The TFTP program is a client implementation (i.e. a user interface) of standard Trivial File Transfer Protocol. TFTP allows you to transfer both text and binary files between your PC and a remote computer running the server implementation of Trivial File Transfer Protocol.

In order for TFTP-client to communicate with a remote computer, that computer must also have a server implementation of TFTP.

You can run multiple TFTP sessions simultaneously in separate windows.

















9. TFTP < previous | content | next >

Starting and Terminating the TFTP Program

You can start the TFTP program by double-clicking on the TFTP icon in the XSecurePro Programs' folder:

Then the TFTP window appears on your display:

You can terminate TFTP by clicking Exit on the TFTP menu bar.


















TFTP Menu Options

The TFTP menu bar displays five items: Exit, Settings, PutFiles, GetFiles, and Help. The Exit item terminates the TFTP session, and the Help item displays help information available about the TFTP. The other three are described below.

The Settings Item

The Settings item allows you to specify parameters and modes of transfers. When you select this item, the TFTP Settings dialog box appears:

You can cancel any changes you make to the dialog box by clicking on Cancel. By clicking on OK, current settings are stored in the xwp.ini file and become the defaults for future TFTP sessions.

The following input fields and check boxes are available:

Host

This field is used to specify a network node name or IP address for the host that you wish to connect to. When you click on the scroll arrow beside the Host box, a drop-down box will display host definitions being in your hosts file. To select a host, click on an appropriate definition.

File(s)

This field is used to specify one or more names for files you are about to transfer. File names are


separated by a space.

Remote directory

This field is used to specify a file directory on the host.

Local directory

This field is used to specify a file directory on your PC.

Per-packet retransmission timeout (sec)

This field lets you set the per-packet retransmission timeout, in seconds. The default value is 5 sec.

Total retransmission timeout (sec)

This field lets you set the total retransmission timeout, in seconds. The default value is 25 sec.

Binary Mode

This check box is used to toggle between ASCII and binary modes for transfers. The default setting is disabled.

Trace

This check box allows you to toggle packet tracing. The default setting is disabled.

Verbose

This check box is used to toggle verbose mode of transfers. The default setting is disabled.

The PutFiles Item

The PutFiles item initiates putting one or more files to the remote directory, all specified in the TFTP Settings dialog box. The remote host is assumed to be a UNIX machine. Note that for every sent file, the UNIX-site file is to exist with the same name and the permission to write for all user categories.

The GetFiles Item

The GetFiles item initiates getting one or more files from the remote directory, all specified in the TFTP Settings dialog box. Note that every received file is to have the permission to read for all user categories.

















10. Ping

This chapter describes how to start and use the Ping utility supplied with XSecurePro.

You can test that the TCP/IP transport is installed and configured correctly by using the Ping utility. Ping can help you isolate network hardware problems and incompatible configurations by allowing you to verify a physical connection to a remote host.

While running, Ping sends a sequence of data packets to a remote host with the time interval specified. If connection between your PC and the host exists, Ping will receive a response after every packet sent. If Ping finds the host, it outputs the appropriate message.

Ping communicates with only one remote host at a time. However, you can run multiple Ping sessions simultaneously in separate windows with each session connected to a different host.

To ping remote hosts, you can select the standard MS Windows ICMP interface protocol or the TCP protocol.

You can choose the IPv4 mode or the IPv6 mode for pinging remote hosts (for both the ICMP and TCP protocols).

Ping can automatically choose the protocol (ICMP or TCP) and the mode (IPv4 or IPv6) for pinging remote hosts.

You can use the '*' wild card symbol in the IP address to scan up to 256 hosts in your LAN to see at once which hosts are alive.

















10. Ping < previous | content | next >

Starting and Terminating the Ping Utility

You can start the Ping utility by double-clicking on the Ping icon in the XSecurePro Programs' folder:

Then the Ping window appears on your display:

You can close the Ping window by clicking Exit on the Ping menu bar.


















Ping Menu Options

The Ping menu bar displays five items: Exit, Settings, Start, Stop and Help. The Exit item terminates the Ping session, and the Help item displays help information available about the Ping. The other three are described below.

The Settings Item

The Settings item allows you to specify parameters of the Ping session. When you select this item, the Ping Settings dialog box appears:

You can cancel any changes you make to the dialog box by clicking on Cancel. By clicking on OK, current settings are stored in the xwp.ini file and become the defaults for future Ping sessions.

The following input fields and check boxes are available:

Host IP

This field is used to specify a network node name or IP address for the remote host that you wish to verify a physical connection to. When you click on the scroll arrow beside the Host IP box, a drop-down box will display host definitions located in your hosts file. To select a host, click on an appropriate definition.

You can use the '*' wild card symbol in the IP address to scan up to 256 hosts in your LAN to see at once which hosts are alive (in both the IPv4 and/or IPv6 modes).

Examples of correct IP addresses:'192.168.0.*','fe80::250:baff:fef2:*42%4'.


Interval

This field lets you set a time interval between two neighboring data packets, in seconds.

TCP port

In this field, you can enter a desired TCP/IP port for TCP/IP protocol pinging. The default is standard TCP/IP echo port 7.

IP mode

You can choose the IPv4 mode for pinging, or the IPv6 mode (for both the ICMP and TCP protocols). The Auto option will automatically choose the IP mode for pinging remote hosts.

Protocol

You can select the standard MS Windows ICMP interface protocol (to allow non-admin users to ping remote hosts), or the TCP protocol. The Auto option will automatically choose the protocol to ping remote hosts.

Trace

This check box allows you to toggle packet tracing. The default setting is disabled.

The Start Item

The Start item initiates a Ping session with the host specified in the Ping Settings dialog box. Ping sends a sequence of data packets to the host with the time interval specified. If connection between your PC and the host exists, Ping will receive a response after every packet sent. If Ping finds the host, it outputs the message <host> (or IP address) is alive. If you get this message, then you know that the TCP/IP transport is set up correctly.

If there are any hardware problems, please check that your cable connection is good and check to see if the host can ping back to your PC.

The Stop Item

The Stop item terminates the Ping session with the remote host specified in the Ping Settings dialog box. Ping outputs summary information.

















11. LPR - Remote Printing Program

This chapter describes how to start and use the LPR program supplied with XSecurePro.

LPR is a client implementation program that allows you to access printers attached to remote computers on your TCP/IP-network. The computers must support the Berkeley Line Printer protocol.

You need to have access to the remote computer that will accept print jobs from you. Your PC name must be defined in the /etc/hosts.equiv or /etc/hosts.lpd file of the remote system.

While using LPR, you can:

● Enter data required to connect to a remote computer and to choose a target printer

● Specify print job options (a number of copies, titles and banner pages, a file type)

● Print one or more files from your PC on the remote printer

● View print jobs in the queue, remove jobs from the queue.

You can run multiple LPR sessions simultaneously in separate windows.

















11. LPR - Remote Printing Program < previous | content | next >

Starting and Terminating the LPR Program

You can start the LPR program by double-clicking on the LPR icon in the XSecurePro Programs' folder:

If there is no remote printer specified, then you are prompted to form the Network printer list. (See section Configuring a Network Printer below on how to control the Network printer list.)

If the Network printer list is not empty, then the Line Printer Requester window appears on your display:

You can then enter the information required to get access to a remote printer, specify job options, and print your files.

To terminate the LPR session, click on the Exit button. Current settings are stored in the xwp.ini file and become the defaults for future LPR sessions.


















Entering LPR Info

This section describes the items of the Line Printer Requester window you can use to prepare for printing your files on remote printers. The following items are available:

Printer

This field is used to specify a remote printer. A remote printer is identified by a server/printer combination. LPR stores all server/printer combinations you define in the Network printer list. (See section Configuring a Network Printer below on how to manage the Network printer list.)

When you click on the scroll arrow beside the list box, a drop-down box displays the Network printer list. To select a printer, click on an appropriate printer definition.

Person

This field is used to specify an owner of your print jobs. When your output is sent to the printer, the contents of the Person field identifies your print jobs in the Current Queue Information box. The person name must not contain any spaces. It defaults to your machine name unless set in the Person field.

Number of copies

This field is used to specify a number of copies you want to produce. The default number of copies is 1. Note that the remote computer you are sending your print files to may impose limits on how many copies you can produce.

Page width

This field is used to specify the page width. The default is 132 characters. The Page width setting must correspond to the remote printer.

Current Queue Information

Since several people may want to use the same printer at the same time, and each job may take a long time to print, a job that you send may not be printed immediately. Instead, it may have to wait in a queue until the printer is available. The Current Queue Information box lets you find out if your output has been printed. The remote computer will be queried every few seconds and the status of the jobs it is processing will be displayed in the box. The queue information includes your jobs as well as other people's jobs.

The Current Queue Information box is also used for selecting the print job you want to cancel (see section Canceling Output below).


Status

This box displays the current program status.

Options

The items of this box allow you to specify options for your print job.

Burst page

Print jobs are normally separated by a 'burst page' to identify the owner of the output. Printed on the burst page are the job classification and the job name. The Burst page check box is used to toggle the burst page. If you prevent the burst page from being printed, the Class name and Job name fields will become unavailable.

Class name

This field is used to specify the job classification printed on the burst page. The class name must not contain any spaces. It defaults to your machine name unless set in this field.

Job name

This field is used to specify the job name printed on the burst page. The job name must not contain any spaces. It defaults to the name of the file being printed unless set in the field.

File Type

This list box lets you choose the mode of file printing. The syntax of the text commands corresponding to these modes is described in the lpr.inf file (see section The lpr.inf File below). You can add, delete, or edit (legal) command lines in this file as you wish.

When you click on the scroll arrow beside the list box, a drop-down box displays the list of possible modes. To select a mode, click on an appropriate command line.

















Printing Files

To print one or more files, click on the Print File button. The File(s) to Print dialog box will appear on your display. Select files you want to print and click OK. The file(s) will be sent over the network to the remote printer and then printed according to current settings.

You need to have access to the remote computer that will accept print jobs from you. Your PC name must be defined in the /etc/hosts.equiv or /etc/hosts.lpd file of the remote system. The Page width setting must correspond to the remote printer.


















Configuring a Network Printer

To configure a printer available on your network, click on the Configure Printer button. The Configure Network Printer dialog box will appear on your display:

Then you can add a new printer to the Network printer list, or remove a printer from the list.

To close the box, click on the Close button.

Adding a Network Printer

Before you add a remote printer to the Network printer list, you must define a server/printer combination to identify the printer. LPR stores all server/printer combinations you define in the Network printer list.

You can use the following items:

Host

This field is used to specify a network name or IP address for the print server computer. When you click on the scroll arrow beside the Host box, a drop-down box will display host definitions stored in your hosts file. To select a host, click on the appropriate definition.

Printer name

This field is used to specify a name for the printer attached to the remote computer selected in the Host field.


Use as default printer

This check box allows you to define the printer you have just specified as the default LPR printer. It will be the current printer each time you start LPR.

Click on the Add button. The server/printer combination will be displayed in the Network printer list box to reflect the Host and Printer name fields you specified.

Make sure that your PC name is defined in the /etc/hosts.equiv file or the /etc/hosts.lpd file on the host UNIX system. If there is no entry in the /etc/hosts.equiv file or /etc/hosts.lpd file for the user and the user tries to print a file, LPR responds with the host error message that the user has no access to the line printer. Also, the Page width setting must correspond to the remote printer.

Deleting a Network Printer

To remove a remote printer definition from the Network printer list, select an appropriate server/printer combination from within the Network printer list box and then click on the Delete button. The definition selected will disappear and the printer will become unavailable for use with LPR.

You can select and delete more than one printer at once.

















Canceling Output

If you change your mind after sending a file for printing, but before it has actually been printed, you can cancel it. The status of the LPR jobs the current printer is processing is displayed in the Current Queue Information box. Locate and double-click your job that is awaiting print. A confirmation dialog box will then appear on your display. If you choose Yes, the selected job will be cancelled.

Note that you can only cancel your own jobs.


















The lpr.inf file

The lpr.inf file supplied with the package contains six commands (for more details see Request For Comments #1179):

f - Print formatted file

This command causes the data file to be printed as a plain text file, providing page breaks as necessary. Any ASCII control characters that are not in the following list are discarded: HT, CR, LF, FF, and BS.

l - Print file leaving control characters

This command causes the specified data file to be printed without filtering the control characters (as is done with the 'f' command).

o - Print PostScript output file

This command prints the data file to be printed, treating the data as standard PostScript input.

p - Print file with 'pr' format

This command causes the data file to be printed with a heading, page numbers, and pagination. The heading should include the date and time that printing was started, the title, and a page number identifier followed by the page number. The title is the file name as specified by the 'N' command, unless the 'T' command (title) has been given. After a page of text has been printed, a new page is started with a new page number. (There is no way to specify the length of the page.)

r - File to print with FORTRAN carriage control

This command causes the data file to be printed, interpreting the first column of each line as FORTRAN carriage control. The FORTRAN standard limits this to blank, "1", "0", and "+" carriage controls.

v - Raster file

This command causes the data file to be printed with no data conversion.


















12. LPD - Network Print Server

This chapter describes how to start and use the LPD (Line Printer Daemon) program supplied with XSecurePro.

LPD is a Network Print Server (daemon) that provides access to your local (attached to your PC) and Microsoft-network-accessible printers from remote computers across TCP/IP network. The remote computers must use the print program that supports the Berkeley Line Printer protocol (lpr client).

While using LPD, you can:

● Change the printer list and printer parameters (add/remove a network printer, edit settings of network printers)

● Enable or disable printing files from remote computers

● Specify the list of users who can print files on your networked printers.

(See Request For Comments #1179. This RFC describes an existing print server protocol widely used on the Internet for communicating between line printer daemons (both clients and servers).

The Berkeley versions of the UNIX operating system provide line printer spooling with a collection of programs: lpr (assign to queue), lpq (display the queue), lprm (remove from queue), and lpc (control the queue). These programs interact with an autonomous process named the line printer daemon.)

LPD provides German and/or French messages and text labels under the corresponding national version of MS Windows.

Note: the LPR printer driver for MS Windows NT4 is manually installed by running the self-extracting archive file, lprd.exe. This file can be found in the distributive directory with uncompressed package installation files.

















12. LPD - Network Print Server < previous | content | next >

Starting and Terminating the LPD Program

You can start the LPD program by double-clicking on the LPD icon in the XSecurePro Programs' folder:

The LPD program determines accessible local (System) and Microsoft-network (Network) printers and creates the Windows printers list. Then it creates the Available printers list and modifies it with the previous information from the ini-file and your directions, and then iconifies itself.

If the ini-file has no LPD settings information yet, then the LPD Settings dialog box will appear on your display prompting you to specify it. (See section Configuring the Network Print Server below.)

When you start the LPD program from the task bar, the main LPD window will appear on your display, showing all printers found (system, network, and TCP printers).

You can then enter information required to provide or change access to them.

Note: LPD is not a service. If you don't bring up the LPD application, any print job sent from remote clients will not be printed.

The following menu items in the LPD window are available:

Exit

Used to terminate the Network Print Server (LPD).

Status

Used to view the Available printers list with their states.


Settings

Used to change LPD settings (the printers list, queue directory and users' access).

Fonts

Used to change fonts for displaying the LPD window.

Help

Used to display the About LPD dialog box and this help text.

















Configuring the Network Print Server

To configure the Network Print Server (LPD), click on the Settings menu item. The LPD Settings dialog box will appear on your display.

In the Available Printers group box, you can add new TCP printers, change settings for TCP printers, and remove a TCP printer. The TCP printers list contains printers that the LPD program will control.

In the Queue Directory group box, you can specify a directory on your hard disk to be used for printer's data streams (i.e. a spool directory).

In the User Access group box, you can specify a list of users who can print files via the LPD program running on your PC.

Don't Filter Input Data

If this check box set on, then no data conversion will be applied to every incoming data file (see the


v type in section The lpr.inf file in Chapter LPR – Remote Printing).

Parse REMBAK jobs

If this check box set on, then the AIX "Rembak" print service will be enabled.

In this case, the /usr/lib/lpd/rembak binary file is skipped (i.e. it is not sent).

Convert Unix text To DOS

If this check box set on, then UNIX-to-DOS format conversion of text files will be enabled (i.e. adding LF after CR).

Enable Trace

If this check box is enabled, the trace information will be output to the lpdtrace.prt file.

To close the LPD Settings dialog box, click OK if you wish to save settings, otherwise click on the Cancel button.

To display the Help window with this text, click on the Help button.

The Available Printers Box

Every Windows printer found during searching can be included into the Available Printers list that the LPD program will control. Printers included must be given the TCP Printer Name - the name by which the LPD and LPR programs will identify the printer over the network.

use Windows network printers

If this check box is enabled, both local and network printers will be included into the Windows printers list (for Add and Edit). Otherwise, local printers will be used only.

Adding a New Network Printer

When you press on the Add button, the LPD - Add Printer dialog box will appear on your display.

The following items are available:

Windows Printers

This list box contains names of Windows printers not yet included into the Available Printers list. The Refresh button allows you to renovate the list.

TCP/IP Printer name

This edit field is used to specify a TCP/IP name for a new printer you want to add into the Available Printers list.

Enable Banner

If this check box is enabled, the printer will print the banner page for any job (i.e. all printed documents will come with a banner page specifying the user name, date, file name and host information).

Pause printing

If this check box is enabled, the LPD program will not allow jobs to be printed on the printer.

Enable form feed at print end

If this check box is enabled, the printer will begin every job with a new page.

Use Bypass

If this check box is enabled, then the LPD program will scan the data it receives, and if it finds the so-

called By-pass sequence in the data stream, it will convert the next two characters into a hexadecimal byte and send it to the printer.

For example, a user specified the By-pass sequence as ^^. If the data stream received is:

123^^1B45678^^2b90

the data output in HEX should be as follows:

31 32 33 1B 34 35 36 37 38 2B 39 30

Note: the hex characters after the By-pass sequence are case insensitive.

Bypass character/s:

This edit field is for specifying the By-pass sequence (one or more characters).

To add a new printer:

1. From within the Windows Printers list box, select a printer to be used as the TCP printer;

2. Specify the TCP/IP Printer name under which the printer will be known in the TCP/IP network (the full name of a network printer consists of the hostname of your PC and the TCP/IP name of a printer);

3. Check all check boxes as you wish;

4. Click OK if you wish to add the printer, otherwise click Cancel.

Note: to run the lpr utility, operating systems first register lpr-printer names. For example, you have to use the admintool utility of the SUN Solaris 2.x operating system to add/modify/remove lpr-printers. TCP/IP Printer name must be one of the registered lpr-printer names.

Changing Printer Settings

When you select a TCP Printer Name from within the Available Printers list box and then click on the Edit button, the LPD - Edit Printer dialog box will appear on your display.

Then you can change any settings for the selected TCP printer almost the same way as in the Add Printer dialog box.

To edit a TCP printer:

1. From within the Windows Printers list box, select a printer to be used as the TCP printer under the TCP/IP Printer Name shown below;

2. Check all check boxes as you wish;

3. Click OK if you wish to save settings for the printer, otherwise click Cancel.

Removing a Printer

In order to remove a TCP printer, choose an appropriate TCP Printer Name from within the Available Printers list box and then click on the Remove button.

The Queue Directory Box

This box specifies the directory path showing where to save control and data files to be printed on network printers (i.e. a spool directory to store print jobs). The subdirectories with TCP printers' names will be created in this directory.

You can specify a queue directory by typing its full path name in the Queue Directory edit field or selecting the name by browsing.

When you press the Browse button, the Select LPD queue directory dialog box will appear on your display.

The Current directory edit field lets you specify the queue directory path.

The Drives list box allows you to choose the drive for the directory.

The Directories list box lets you choose the queue directory in which subdirectories with TCP printers names will be created for queuing.

To close the dialog box, click OK if you wish to use the Current directory as the queue one, otherwise click on the Cancel button.

The User Access Box

You can support a list of users who are allowed to print files (with the LPR program) via the LPD program running on your PC. Also you can modify the User access list (add and remove user names).

If the Allow ALL users access check box is enabled, any user can use LPD on your PC. Otherwise, you can use the Settings button to specify user access settings.

When you click on the Settings button, the User Access dialog box will appear on your display.

The User access list shows those users who are currently allowed to print files on LPR-accessible printers via your LPD program.

To add a new user to the User access list, specify the user name in the New User edit field and then click on the Add button.

To remove a user from the User access list, select an appropriate name on it and click on the Remove button.

To close the dialog box, click OK if you wish to save the modified list, otherwise click on the Cancel button.

















The Printers Status

When you choose the Status menu item, the LPD - Printer Status dialog box will appear on your display.

You can view current states of all Available printers (pause, ready, print).


















The "[LPDAEMON]" Section of the ini-file

The "[LPDAEMON]" section of the ini-file may have the following entry lines you can customize for particular needs and applications. These settings are absent in the LPD Settings dialog box.

FontFace=<iniFontFace>

This line lets you specify the font face name you prefer to display messages in windows.

The <iniFontFace>, "Courier New", "Courier", <a font which MS Windows gives> font face priority is supported.

WaitPort=<port number>

This line lets you customize your LPD listening port number instead of the standard one (515).


















Starting and Terminating Startup

You can start the Startup program by double-clicking on the Startup icon in the XSecurePro Programs' folder:

The Startup window will appear on your display:


You can then enter information required to run remote commands into the window (see Entering Startup Info below).

Once you have done this, you can execute commands or run startup files on a host as it described in the next section.

In order to terminate the Startup program, click on the Exit button.

Running a Startup File

A startup file consists of one or more ASCII lines. Each line may contain one or more executable commands on the host. Use your text editor to create the file in the XSecurePro's home directory. All startup files have to have the .SU extension.

In order to execute instructions from any startup file, specify a name for the file you want to run and press the Execute button (see the Command Box section below).

Executing a Command/File

When you execute a command or startup file (remotely), the following takes place:

● The login information in the User ID, Host, and Password fields will be used to make a connection.

● The command in the Command field or in the startup file will be sent to the host with the name or IP address specified in the Host field. If the command starts a client, the client session will commence. The initial socket will be closed after the amount of time specified in the Exit after Timeout of field. Note that different lines of a startup file will spawn different processes.

● If Log File has been checked, host or command messages will be saved in a log file for the amount of time specified in the Exit after Timeout of field.

















Entering Startup Info

This section describes the Startup fields you can use to select or enter proper parameters to run remote commands.

The Start Method Box

The first thing you should select is the Start Method. Initially REXEC is selected.

RSH

For RSH method ("Remote Shell"), you should know your user ID name. If you click on RSH, the Password field will be grayed. Some hosts require your PC to be authorized before using RSH, as it does not require a password. On UNIX systems, you need to add your PC name to the /etc/hosts.equiv and $HOME/.rhosts files on your host.

REXEC

For REXEC (Remote Executable) method, you can choose either the direct access insecure execution mode or the secure (SSH) channel mode.

In the Start Method box of the Startup window, you can see a list of actual SSH1/SSH2 protocol connections you have previously established (for example, by the SSH1 or SSH2 Client of the Telnet_SSH program). (See Starting an SSH Session in the Starting and Terminating Telnet_SSH section on how to establish secure connections). The Refresh button allows you to renovate the list.

If you clear the Use SSH Forwarding check box then the direct access insecure mode will only be used for REXEC operations.

If you want REXEC operations to be done in secure connection mode, enable the Use SSH Forwarding check box and select a desired remote host (an active SSH server) from within the list.

In the SSH1/SSH2 mode, the "Dynamic Port Forwarding" feature of the Telnet_SSH/SSH1 or Telnet_SSH/SSH2 Client and Startup Client will automatically be used, so you need not set up any port forwarding manually.

SSH1/SSH2 daemons do not usually provide for port numbers less than 1024. This is why the "Dynamic Port Forwarding" feature does not work for RSH and RLOGIN methods.

If the REXEC server and SSH1/SSH2 server you are using in a Startup session are on the same remote host then the Host Name/IP Address field can contain "localhost" or "127.0.0.1". This is more preferable than its actual IP address in most cases (but depends on how the host has been


configured).


RLOGIN

For RLOGIN (Remote Login) method, you can use the following macros in a command or startup files (see section Command Box below):

● "$(DELAY)"● "$(CR)"● "$(LF)"● "$(CRLF)"● "$(SEND)"● "$(INPUTPASSWORD)"● "$(DISPLAYNUMBER)"

Note that the profile file is always executed on a remote host for this method when a user logs in.

Startup uses the randomized RLOGIN initial portnumber to avoid possible rejection of connection.

lShell (local Shell)

The lShell (i.e., local Shell) mode allows you to enter a command line to run a local executable file (on your PC) like you do that with the MS Start/Run box. For example, you may choose to run Telnet, Notepad, local X clients, etc.

For information about local X clients, please refer to Appendix F Local X and Motif Clients.

Telnet

The Telnet method is similar to other methods. You enter login information to establish Telnet connection with your remote host and specify a command line or file you want to execute on the host. When you press Execute, Startup will launch a non-interactive Telnet session (i.e., without the Telnet window).

In this mode, the direct access insecure mode will be used for Telnet operations (without SSH X11 forwarding).

Note that you must use the -display argument in the command line to invoke a remote X client (to communicate with XServer on your PC-host). In this case, the X client connects to your XServer and operates.

For example, you can execute the following command line to invoke the 'xterm' application on your PC-host:

path/xterm -display 192.168.36.41:0 &orpath/xterm -display $(LOCALIP):$(DISPLAYNUMBER) &

Telnet/SSH2 (SSH-2 Client)

The Telnet/SSH2 (SSH-2 Client) method is similar to other methods. You enter login information to establish Telnet_SSH connection with your remote host and specify a command line or file you want to execute on the host. When you press Execute, Startup will launch a non-interactive Telnet_SSH session (i.e., without the Telnet_SSH window).

It is not recommended to use the '&' sign because of unstable results. E.g., if you need to start 'xterm' on a remote host, then the "xterm" command line is preferable (and "xterm&" is not recommended).

In the Start Method box of the Startup window, you can see a list of actual SSH1/SSH2 protocol connections you have previously established by the Telnet_SSH/SSH1 or Telnet_SSH/SSH2 Client. The Refresh button allows you to renovate the list.

In the SSH1/SSH2 mode, the "Dynamic Port Forwarding" feature of the Telnet_SSH/SSH1 or Telnet_SSH/SSH2 Client and Startup Client will automatically be used, so you need not set up any port forwarding manually.

To use this method, you must prove your identity to the remote system using either password authentication or RSA/DSA authentication method. RSA/DSA authentication uses a public/private key pair to authenticate the connection. If RSA/DSA authentication is selected (by checking on the RSA/DSA Authentication check box), you should enter your passphrase in the Password entry field. Also you should specify a location of the identity file (in the Private Key File entry field) to be used for this process. If the RSA/DSA Authentication check box is disabled, then the password authentication method will be used.

For more information on how to establish secure connections, refer to Starting an SSH Session in the Starting and Terminating Telnet_SSH section in chapter Telnet_SSH.

Note that you need not use the -display argument in the command line to invoke remote X clients (to communicate with XServer on your PC). In this case, the X client you invoke connects to your XServer via the SSH channel of your choice and operates using standard SSH X11 forwarding (without establishing new connection between hosts).

For example, you can execute the following command line to invoke the 'xterm' application on your PC-host:

path/xterm;

Note that if you apply the -display argument in the command line to invoke a remote X client (to communicate with XServer on your PC), then the standard SSH X11 forwarding will not be used (and a new insecure Telnet connection will be established between the X client and your XServer according to the -display argument).


The Login Box

The Login box lets you enter information required to log onto a host. If your start method is set to RSH, the Password field is disabled.

Host Name/IP Address

This field defines a name for a remote host you want to connect to and execute commands. You can

enter either the network node name for the host or its network address. When you click on the scroll arrow beside the HostName field, a drop-down box will display host definitions being in your hosts file. To select a host, click on an appropriate definition.

Note that a host name you specify here may not result in the same remote host name due to different name-address DNS translations in different LANs. You should specify the host name or IP address for a remote host in a LAN that are known inside that LAN for that host.

User ID

This field is where you enter your User ID for the host you want to connect to.

Password

This field defines your password for the REXEC, RLOGIN, or Telnet method. When you enter your password, an asterisk will appear for each character you type in.

Enable Save Password

If this check box is disabled, then you will be prompted to enter a password each time when it is needed (e.g., when you Save Job As with the setting and then launch the job).

The Command Box

The Command box lets you enter information required to execute a command or to run a startup file on the specified host.

Command

This field is used to enter a command that will be sent to a host or to specify a startup file you want to run. The command you enter depends on your host system and how it is set up. In the lShell mode, you should enter a command to be run locally (on your PC). You can enter up to 255 characters in a command line.

UNIX C Shell Command

If you have defined all necessary environment variables in the C shell resource file (i.e. the .cshrc file), then you can simply enter a command. For example, to start xterm:

xterm &

UNIX Bourne Shell Command

Because the Bourne shell startup file (i.e. the .profile file) will not be invoked when the Startup program logs onto the host, it is recommended that you include the path and display variables on the command line. For example:

path/xterm -display mypcname:0 &

where path is the location of the xterm on the host, and mypcname is the network name or IP

address of your PC.

Note that you can use the following macros in a command or startup files:

● $(LOCALHOST) for the network name of your PC● $(LOCALIP) for the IP address of your PC● $(LOCALDISPLAY) for the display specification of your XServer● $(DISPLAYNUMBER) for the display number of your XServer

For example:

path/xterm -display $(LOCALHOST):0 &

path/xterm -display $(LOCALIP):0 &

path/xterm -display $(LOCALDISPLAY) &

path/xterm -display $(LOCALIP):$(DISPLAYNUMBER) &

Also, you can use macros $(INPUTLIP) to place any text into the command line before its executing. For example, 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 &

To execute a command entered in the field, click on the Execute button.

Command File

This field is used to specify a startup file you want to run on a host or edit it.

When you click on the scroll arrow beside the Command File field, a drop-down box will display all startup files stored in the XSecurePro's home directory.

In order to execute instructions in a startup file, select from the box or enter into the field a name for the file you want to run and press the Execute button. If the file exists, its first line appears in the Command field.

Another way of specifying a startup file is to enter into the Command field a file name preceded by the @ sign, for example @mystartup.su.

Edit

When you press on this button, the Microsoft Notepad is invoked and the startup file specified in the Command File field will be opened. This lets you view or modify the file before running it.

Log File

When you enable this option, whenever you execute a single command or a startup file, any startup or error message information that the host or client would normally display will be sent to a file. The log file resides in the XSecurePro's home directory. The file's name differs depending on how you execute commands.

● If you execute a single command entered into the Command field, all log information will be saved in a file called startup.log.

● If you run a startup file, the log file will be saved as filename.LOG, where filename is the name of the startup file.

Information will be sent to a log file for the amount of time specified in the Exit after Timeout of field, after which the socket will be closed.

Wait for RLogin Password

This option is used if you want to enter your password only when a prompt from the RLOGIN daemon appears.

Exit after Timeout of

This field defines the amount of time the socket will stay open after the host connection has been made. The default value is of ten seconds. If the connection gets established but the invoked program does not get time to start up, you can set this to a higher value.

empty Default UserID for Jobs

If selected, this check box suppresses using the MS Windows logon name as default in the Jobs' "Startup Login" dialogs.

Default

This button will initialize all parameters to their default values.

Status Messages

Whenever you execute a single command or a startup file, any startup or error message information that the host or client would normally display is sent to the box.

Example of Initiating the REXEC Session via SSH


● your remote host is accessible from your PC

● your remote host supports the REXEC protocol for your PC

● sshd-daemon (or sshd2-daemon) is running on your remote host

● your PC is accessible from your remote host.

If OK, then you may initiate the REXEC session via SSH like the following steps:

1) Initiating the Telnet_SSH session



● Enter the network name or IP address of the remote host you want to connect to






2) Initiating the Startup session

● Launch Startup by double-clicking on the Startup icon from the XSecurePro Programs' folder (the Startup window should appear)

● Choose REXEC in the Start Method section

● Enter localhost as the network name or 127.0.0.1 as the IP address in the Host Name/IP Address field in the Login section

● Enter your User Name in the User ID field (e.g., John)




● Specify other required settings

● In the Command field, enter the following line:

ls -l

● Click the Execute button

Startup will open the REXEC session to the remote host through the encrypted connection. In the Status Messages pane, the output of the command (i.e. the list of directories and files from your home directory on your host) should be displayed.

















Startup Jobs

A job is a named task with a certain set of parameters. Job's main parameters include: start method, login information, command lines, and settings.

The Startup Job Name list contains names of currently available jobs. You can create an icon for a job and choose a Program Group to contain these icons. By default, this is the StartIcons folder.

A job may be launched by double-clicking on its icon (in the StartIcons folder by default). You can have up to 512 jobs.

The Save Job As, Open Job and Remove Job buttons in the Startup window are for manipulating with Startup jobs.

The Save Job As button creates a job and adds its name to the list. The Open Job button opens a specified job for modifying. You may remove an opened job by pressing the Remove Job button.

Any changes of the Startup Job Name list are automatically displayed in the corresponding Program Group (StartIcons by default).

Saving a Job

When you click on the Save Job As button, it displays the following dialog box:


This dialog box allows you to create a job, i.e. to store current parameters under a certain name. If a job with the same name already exists, it will be overwritten; if it does not exist, the new job will be created and added to the Startup Job Name list. The default icon for the job may be changed with the Change Icon button.

Startup Job Name

This field defines a name for the job to be saved. In the drop-down box, you can view all available job names in the list.

Create Startup Icon

If this check box is checked, then a job will be displayed in the Program Group you will choose for your jobs (StartIcons by default) with an icon you will specify; otherwise the job will be only added to the Startup Job Name list.

Program Group

This field is used to specify a group to contain your job's icons (StartIcons by default). You can enter a name in the field or select a name from the Available Program Groups field. The Program Group will first be cleared and then all jobs from the Startup Job Name list (marked to Create Startup Icon) will be moved into it.

Available Program Groups

This box lets you select a group to contain your job's icons. The name will appear in the Program Group field.

Exit after Execute

If this check box is disabled, then the Startup dialog box will stay on after executing the job and you will be able to continue working on it.

Don't start XServer

If this check box is disabled, then XServer will be started up (if it is not running yet) when opening the job (or launching it by double-clicking on its icon) and before executing its commands.

Otherwise, you may open the job and execute commands which do not launch X clients and so do not require XServer (if it is not running yet).

Note that if you launch a job by double-clicking on its icon, then the job will execute in batch mode.

Change Icon

When you click on the button, it displays the following dialog box:

This box gives you a possibility to choose a suitable icon for the job to be saved. The File Name field displays a current file name and the corresponding Icon List. If you want to assign to your job an icon other than by Default, select the desired icon from the current Icon List. To change list of available icons, press the Browse button and choose a suitable icon from the Open window.

Opening a Job

When you click on the Open Job button, it displays the following dialog box:

This box allows you to view the Startup Job Name list and to select a certain job from it. After highlighting a job in the drop-down box or entering a job name into the edit field, press OK to open the job. Its parameters will be displayed in corresponding fields of the Startup window, so you can view or change them before running the job.

















Running NFS-Server with Command Line Parameters

The 'externalportmapper' parameter

You can launch NFS-Server with the command line parameter:

PATH\nfs_serv.exe -externalportmapper

with PATH indicating your XSecurePro home directory.

In this case, NFS-Server will be using the external portmapper that is running on your PC.

To display a list of all registered RPC services, you can execute the following command on a remote host:

rpcinfo -p host

with "host" being the name or IP address of your PC with NFS-Server.

The 'trace' parameter


PATH\nfs_serv.exe -trace

to collect access events in the trace file.

The 'RunOnTaskBar' parameter


PATH\nfs_serv.exe -RunOnTaskBar

to run NFS-Server as a "quasi"-service. The NFS-Server's icon will be hidden automatically on the system task bar after logon to the system (if you have the command line in the StartUp folder).


















The "[NFSSERVER]" Section of the ini-file

The "[NFSSERVER]" section of the ini-file may have the following entry lines you can customize for particular needs and applications.

Note that if you change parameter values in the [NFSSERVER] section of the xwp.ini file, you should restart NFS-Server for your new values to take effect.

COUNT_DUPES=1

Value 1 for this option specifies to enable counting of the same NFS clients.The default value is 0.

DisableReadCaching

The setting is used to provide concurrent intensive access to files directly and via NFS connections.

EmulateUnixDirTimeOnFATFS=N

The EmulateUnixDirTimeOnFATFS variable setting is for FATFS exports.

With N=0, this setting provides the mode when, on each changing in the directory, the "modified time" attribute of the ACCESS or GETATTR requests "runs forward" only once. But next requests will be answered with a "true" value for the directory "modified time". This is useful when only one NFS client operates with the exports (and NO aside changes), because the client sees the expected directory date/times.

EmulateUnixDirTimeOnFATFS=1 is the default setting. This provides the mode when the "modified time" attribute of the ACCESS or GETATTR requests "runs forward". This is useful to force any connected NFS client to re-read the directory listing. This is of great importance when a non-single mounting of the FATFS export is made.

EnableWriteCaching=N

This binary setting is used as equivalent to the UNIX "ASync" NFS-Server mode.When N=1 (default), write-file operations are performed no-cached.With N=0, write-file operations are performed using cache and so faster (i.e. asynchronously).

FL_CHRISLESLIE=N

With N=1, the FL_CHRISLESLIE binary setting enables caching upon NFS writing. This speeds up writing files on the NFS-Server box due to caching file handles. Normally, every NFS_WRITE command of the NFS protocol opens a file handle, sets an offset, writes some amount of bytes, etc.


This setting is especially useful for copying huge files.The default value is 0.

FL_DOUGLASCBEETHE=N

With N=1, the FL_DOUGLASCBEETHE binary setting enables setting up file size to 0 for read-only files. The default value is 0.

FL_MASK_HIDDEN_ATTRS=1

Value 0 for this option specifies to account for (i.e., not to suppress) the HIDDEN and ARCHIVE attributes for files.Value 1 for this option specifies to mask (suppress) the HIDDEN attributes for files.Value 2 for this option specifies to mask (suppress) the HIDDEN and ARCHIVE attributes for files.The default value is 2.

FL_MASK_SYSTEM_ATTRS=1

Value 0 for this option specifies to account for (i.e., not to suppress) the SYSTEM and ARCHIVE attributes for files.Value 1 for this option specifies to mask (suppress) the SYSTEM attributes for files.Value 2 for this option specifies to mask (suppress) the SYSTEM and ARCHIVE attributes for files.The default value is 2.

FL_MITXELENA=1

This line lets you avoid the directory permission problem for some NFS-Clients (e.g., that of SCO UNIX 5.0.5).This setting changes the default directory permission value from 755 to 777.The default value is 0.

FL_TZERAN=N

The FL_TZERAN setting allows you to change the time zone difference (e.g., FL_TZERAN=2 will add 2 hours to system time). Generally, the time zone setting uses the one from the operating system (i.e. the MS Windows' setting). The FL_TZERAN option allows you to adjust time zone in some cases when the time zone settings properties are differing on the PC box and UNIX box (e.g., different daylight saving settings, etc.).The default value of FL_TZERAN is 0 (hours).

FlushFRDC=1

This line provides for each transfer file operation to be performed without buffering, i.e. each read operation must follow the open-file operation and the close-file operation must follow each write operation. This mode may significantly decrease transferring (huge) files in performance.The default value is 0.

GracefulExit=0

You can use this line to avoid an error message issued at shutdown of a system with NFS-Server running.

NFS_PORT=N

This line specifies for NFS-Server to use port N.The default value is 2049.

NOCHECK_UID_ON_MNT=1

Value 1 for this option specifies to disable checking of UID during mounting.The default value is 0.

NOSubDirectory=0

Value 0 for this binary option specifies to disable mounting a subdirectory of a shared directory.The default value is 1 (i.e. to enable mounting a subdirectory of a shared directory).

umask=code

This setting is for control of file permissions (like the umask=code command in UNIX systems). Values of code are the same as those in UNIX. The default value is: umask=0022. Note: do not forget to type leading '0' (e.g. DO NOT use "umask=770"). The FL_MITXELENA setting is now obsolete (but still usable) as it is a subset of umask.

UseAttributesCache=0

Value 1 lets you change any once mounted removable drive (like CD or FDD).This decreases the NFS connection performance.The default value is 1.

















15. Network File System Client (NFS-Client)

This chapter describes how to configure and use the NFS-Client program supplied with XSecurePro.

NFS-Client is a program running under the MS Windows operating system in order to mount one or more shared network resources from one or more NFS servers and to share access to files and directories with other PCs and UNIX users across the network.

A shared network resource is any folder that the administrator makes available to be mounted and its subdirectories. The process of making such resources available is called exporting a shared network resource. On the NFS client side, a shared network resource is seen as a logical disk drive.

NFS-Client does not turn your PC into a fully qualified file server. Instead, it allows simple access to folders and files for a limited number of systems on the network.

NFS-Client has a multi-threaded code developed for the Win32 environment and is designed to work with the built-in MS Windows TCP/IP-32 protocol stack. NFS-Client can operate in multi-home environment (i.e. with non-single IP address) with no limitations.

NFS-Client can be installed under one of the MS Windows operating systems (9x/ME/NT4/2K/2K3/XP/Vista/XP-x64) to enable you to benefit from network NFS server services. With the help of NFS-Client you can mount disks and folders from network, no matter under which operating system they reside, and make them as part of your familiar local desktop environment.

NFS-Client for MS Windows NT4/2K/2K3/XP/Vista/XP-x64 can perform NFS operations either by direct insecure access to a remote host or through one of the established SSH2 protocol connections as well. You can access resources you need from behind your corporate firewalls.

The PingNFS and NFSprobe Utilities

The PingNFS and NFSprobe utilities are designed for getting some useful information about computers (running NFS servers) available across your TCP/IP-based network.

PingNFS allows you to check available connections to those computers and to view their exported resources. PingNFS is described in Appendix D.

NFSprobe allows you to check availability of exported resources on those systems you might mount to your PC. NFSprobe is described in Appendix E.

You can use PingNFS and NFSprobe to recognize your network environment for solving particular NFS tasks or network troubles.

















15. Network File System Client (NFS-Client) < previous | content | next >

NFS-Client Settings under MS Windows 9x/ME

All NFS-Client configuration parameters are set up by making selections in property pages. These property pages are accessed through the Network shortcut in Control Panel.

To make the NFS-Client settings:

1. On the DESKTOP, choose My Computer, then Control Panel, and then open Network

2. Select XWPNFS32 Client for NFS Networks from within the list of network components installed, and click Properties.

The XWPNFS32 Client for NFS Networks Properties dialog box will appear with the following five tabs: Authentication, FileNames, Network, Servers, and About.


Removing NFS-Client

To remove NFS-Client from MS Windows, select XWPNFS32 Client for NFS Networks from within the list of network components installed, and click Remove.

The Authentication Tab

Query the (PC)NFS authentication server

If this check box is disabled, then this box allows you to specify UserID and GroupID for mounting to UNIX systems. If the user exists in several groups, they can be specified in the Other Group ID field with the space or comma characters as separators.

If this check box is enabled, the NFS Client Logon dialog box will appear at start of MS Windows.

When you enter your User Name and Password, and the authentication server entered in the Server field successfully authenticates you, then it gives you your UserID and GroupID that you must use in the Unix Authentication group box for the MS Windows session (after pressing OK). If authentication failed (the server does not respond, permission is denied, or you pressed Cancel), then this dialog box will appear later when you want to access your network resources (for mounting).

Save Logon Password

If you enable this check box, then you will not be prompted to specify the password next time you will connect to the NFS server specified.

Browsing Network for NFS Servers

Network Neighbourhood is used to browse your network for NFS file servers and to check for the available resources on these servers. Every time you access an NFS server, either to browse its exported resources or to mount a shared network folder, the server requires you to authenticate yourself so that it can verify your identity.

In an NFS network, once the user is authenticated, that user's access to network file resources is further defined by the permissions granted for certain files and folders. When browsing you will be able to see all the exported folders, however, viewing the contents of the folders as well as opening and editing files will depend on whether you have the correct permissions. (See section Mounting an NFS File System under MS Windows 9x/ME below.)

The FileNames Tab

When you click on the Default settings button, these parameters will be initialised to their default values.

Unix-to-Windows File Name Converting

The Unix => Win95 File Name Convert Mode group box allows you to specify file name conversion rules from the UNIX format to the MS Windows format.

Use suffix for equal file names

If you enable this check box, then the UNIX file names that only differ by cases will be concatenated with a two-character suffix. The second character will be changed by incrementing its code by 1. You can specify an initial value for the suffix in the Suffix for equal file names field.

Show files with '.' at 1st position of name

If you disable this check box, then you can see all file names but those beginning with a period. For the file names beginning with a period, it is desirable to substitute the first period character in the file name with another character. You can specify the character in the Use this symbol instead of '.' at 1st position of name field.

Windows-to-Unix File Name Converting

The New Win95 Name => Unix Name Convert Mode group box allows you to specify file name conversion rules from the MS Windows format to the UNIX format.

New names for files and directories created or renamed under MS Windows on NFS servers will be converted to upper/lower case or unchanged depending on the mode you choose: Convert to upper

case, Convert to lower case, or Preserve the case of name symbols.

The Network Tab

Ignore File Lock/Unlock Requests

If you enable this check box, then NFS-Client will be able to correctly use locked files (e.g., running executables or opened files).

Default settings

When you click on this button, these parameters will be initialised to their default values.

The Network Settings Box

The Network Settings group box allows you to specify:

● Broadcast Timeout - when watching network for hosts supporting the NFS and MOUNT protocols, specifies the number of seconds that NFS-Client will wait before re-transmitting a request.

● Retry Count - when sending requests to a server, is a number of times not replying during the timeout specified before a timeout error occurs due to no response from the server.

● Timeout Period - when sending requests of the MOUNT and NFS protocols, is the absolute time in milliseconds that NFS-Client will wait for the server's response before returning a timeout error.

These parameters may need to be fine tuned to ensure that your NFS-Client is not sending requests faster than the server is able to reply resulting in further unnecessary network traffic.

The Cache Settings Box

The Cache Settings group box allows you to specify the following 'Life Time' values for time-driven renovating of file/directory attributes stored in the NFS-Client's internal cache:

● Folder Attributes Life Time● File Attributes Life Time● Read Cache Life Time

NFS-Client will preserve the original attributes for existing folders and files and will create new folders and files with the default attribute values. These are the standard UNIX file attributes.

The Servers Tab

This tab allows you to choose a mode for requesting NFS servers. You can also manage an NFS Server List for specific hosts.

Use Broadcast Requests

If the Use Broadcast Requests check box is enabled, then, to locate all available remote NFS servers in LAN, broadcast messages will be sent (in LAN only).

Use NFS Server List

If the Use NFS Server List check box is enabled, then remote NFS servers specified in the list will only be requested (no matter in LAN or WAN).

You can enter an IP address or a host name for the NFS server you want to request into the edit field, and then Add the server to the current list. To remove an NFS server from the list, highlight it and use the Delete button.

If both the check boxes are disabled, then, when you want to mount an exported file system, the prompt dialog will appear for you to enter the IP address or host name to check accessibility of the NFS server (that will become the first item in the list).

If both the check boxes are enabled, then broadcast requests are first sent, followed by the NFS Server List requests (resulting in Network Neighbourhood items).

Show only IP addresses of NFS servers

If this check box is disabled, then IP addresses of NFS servers are displayed with corresponding host names. This feature helps prevent you from timeouts because of possible DNS accessibility problems.

The About Tab

This tab contains reference information about the NFS-Client release, protocols and versions supported.

At present, NFS-Client supports the following protocols:

● NFS protocol, version 2● MOUNT protocol, version 1● PORTMAP protocol, version 2● TCP/IP (as well as UDP) protocol at the transport level.

















Mounting an NFS File System under MS Windows 9x/ME

Before you can mount an NFS exported file system as a network drive:

● your host name must be defined in the hosts database on the NFS server from which you want to mount a file system

● the file system that you are trying to mount must be an exported directory on the remote system

● you require the appropriate permission to mount and access the particular file system.

NFS-Client can mount drives from Microsoft Explorer or through the Network Neighbourhood application.

Mounting in Network Neighbourhood

To mount an exported file system as a network drive in Network Neighbourhood:

1. Point the cursor to the exported network folder that you wish to mount and right click the mouse button

2. Select the Map Network Drive command

3. From the Drive: pull down list box, select the drive letter you wish to associate with the new file system.

Disconnecting a Currently Mounted NFS

To disconnect a mounted file system, you can highlight the drive that you wish to disconnect and right click the mouse button to choose the Disconnect command.


















NFS-Client Settings under MS Windows NT4/2000/XP

To make the NFS-Client settings, you can double-click on the NFS Client Settings icon in the NFS Client Programs' folder:

This presents you with a dialog of several tab windows that allow you to view and modify the NFS-Client settings. They are described below.

When you click on the Default button in the dialog box, all parameters will be initialised to their default values.

The Save as button allows you to save the current settings from the box to a file with the standard Save As window. The Open button allows you to choose the settings file and load it in the box with the standard Open window.

By clicking Apply, the current settings in the dialog box will take effect immediately.

You can cancel any changes you have made to the dialog box and close it by pressing Cancel.

The NFS Servers Tab


This tab allows you to choose a mode for requesting NFS servers. You can also manage an NFS Server List for specific hosts.

Use Broadcast Requests

If this check box is enabled, then, to locate all available remote NFS servers in LAN, broadcast messages will be sent (in LAN only).

Use NFS Server List

If this check box is enabled, then remote NFS servers specified in the list will only be requested (no matter in LAN or WAN).

If both the check boxes are disabled, then, when you want to mount an exported file system, the prompt dialog will appear for you to enter the IP address or host name to check accessibility of the NFS server (that will become the first item in the list).

If both the check boxes are enabled, then broadcast requests are first sent, followed by the NFS Server List requests (resulting in My Network Places items).

Details

Use this button to change the tab into its editing form (see the next section). This form allows you to

insert a new NFS server into the Remote NFS Server list. Or you can select an NFS server on the list and then edit its parameters displayed.

Show only IP addresses of NFS servers

If this check box is disabled, then IP addresses of NFS servers are displayed with corresponding host names. This feature helps prevent you from timeouts because of possible DNS accessibility problems.

Transport

The Use UDP and Use TCP check boxes in the Transport group box let you enable the transport protocols NFS-Client will use. Auto Select will try to use TCP first, and then UDP (if an NFS server fails to support TCP).

NFS Protocol

The Use NFS2 and Use NFS3 check boxes in the NFS Protocol group box let you enable the NFS protocols NFS-Client will use. Auto Select will try to use NFS3 first, and then NFS2 (if an NFS server fails to support NFS3).

WebNFS

The Use WebNFS check box enabled allows NFS-Client to use the WEBNFS protocol for mounting a remote NFS. In the Web NFS alias entry field, you specify a name for a shared directory mounted with the WEBNFS protocol. Using the WEBNFS protocol, you can mount a shared directory directly (i.e., not using protocols PORTMAP and MOUNT).

Editing Remote NFS Server Parameters

To remove an NFS server from the list, highlight it and press the Remove button.

You can press Add to add an NFS server (with parameters specified) to the current list.

Pressing Set sets up new values of parameters specified for the current NFS server.

Pressing Details closes the Details group box with no changes and returns you to the main form of the tab.

Server Name

In this edit field, you can enter an IP address or a host name for the NFS server you want to request.

Use SSH-2

If this check box is disabled, then you will perform NFS operations through direct insecure connection to the NFS server you select when mounting shared NFS resources.

If this check box is enabled, then you will be prompted to choose one of secure connection channels (using the SSH2 protocol) previously established between your PC and a remote SSH server. In this mode, NFS server must be in the NFS Server list and be accessible from the SSH server.

Use PortMapper

If this check box is enabled, then the NFS server specified will define ports for you to use.

If this check box is disabled, then you are prompted to define the following data that the NFS server specified will use:

● Port numbers (for protocols Mount, NFS, NLM),

● Transport type (use TCP, use UDP),

● NFS protocol version (Ver.2, Ver.3).

Every NFS server in the list is shown with those values that you assigned to it.

The Authentication Tab

The Authentication Type Box

You can choose one of the following authentication methods that NFS-Client will use under your MS Windows system:

● Use UID/GID Setting● Use (PC)NFSd Server● Use LDAP v3 Server

Use UID/GID Setting

This method allows you to directly specify the UserID and GroupID values that will be used for mounting to UNIX systems (without using PCNFSd). If the user exists in several groups, they can be specified in the Other Group ID field with the space or comma characters as separators.

Select the Ask Uid/Gid for each connecting attempt check box if you want to enter UID/GID for each new connection. Then you will be prompted to specify new UserID, GroupID, and Other Group ID values that will be used for mounting to UNIX systems.

You must enter proper UserID and GroupID values for mounting an exported resource, or you will be prompted to specify them (e.g., if access denied).

Use (PC)NFSd Server

If you choose this method, then User Name and Password first entered when logging in will be used to authenticate the user (and to obtain the UserID and GroupID values).

When the authentication server entered in the PCNFSd Authentication Server field successfully authenticates you, then it will allow you to access exported resources, and your UserID and GroupID values (obtained by PCNFSd) will be used for mounting.

If authentication failed (the server does not respond, permission is denied, etc), then the default UserID and GroupID values displayed will be used to access your network resources.

If you want to be asked for authentication immediately after the user logs in, enable the Use NFS

Authentication during MS Windows Login check box.

Select the Ask Authentication for each connecting attempt check box if you want to enter your authentication data for each new connection.

In the dialog box that comes up, you can use the Anonymous button that corresponds to UID=-2 and GID=-2 for Unix authentication.

Use LDAP v3 Server

NFS-Client incorporates support for accessing LDAP-based directories, getting information from LDAP servers about the services provided, and using corresponding services as needed. It is based on Lightweight Directory Access Protocol (LDAP).

The LDAP Authentication mode was implemented to access LDAP Active Directory Servers of MS Windows 2003 R2 Standard Edition and Enterprise Edition.

LDAP Active Directory of MS Windows 2003 R2 Standard Edition and Enterprise Edition have different Schemas and so require additional data for NFS-Client to authenticate you.

For LDAP Authentication, you need to fill in the following fields in the LDAP tab that comes up: - Authentication Server - UserName Attribute Name - Uid Attribute Name - Gid Attribute Name

If LDAP Server is Server2003 R2 Standard Edition (Win2K3 AD Enterprise): - UserName Attribute Name = "uid" - Uid Attribute Name = "uidNumber" - Gid Attribute Name = "gidNumber"

If LDAP Server is Server2003 R2 Enterprise Edition (Win2K3 AD Standard): - UserName Attribute Name = msSFU30Name - Uid Attribute Name = msSFU30UidNumber - Gid Attribute Name = msSFU30GidNumber

When the LDAP evaluation time is over or the xwpldap.dll file is absent, the corresponding LDAP tab is invisible.

Select the Use MS Login Name/Password for NFS Authentication check box if you want NFS-Client to use the Microsoft Login User Name and Password for NFS authentication by LDAP.

UID/GID Used for Mounting

You can find out UID/GID used for mounting. To do so, select a file or a directory on the mounted drive and right-click on it. In the pop-up menu, choose Properties, and then click the XWPNFS Attributes tab. For example,

In the Unix Attributes group box, you can see the owner (UID and GID) and permissions of the file. In the User group box, you can see the UID and GID used for mounting the file.

Browsing Network for NFS Servers

My Network Places/Entire Network/XwpNTrdr/Remote NFS Servers is used to browse your network for NFS file servers and to check for the available resources on these servers. Every time you access an NFS server, either to browse its exported resources or to mount a shared network folder, the server requires you to authenticate yourself so that it can verify your identity.

In an NFS network, once the user is authenticated, that user's access to network file resources is further defined by the permissions granted for certain files and folders. When browsing you will be able to see all the exported folders, however, viewing the contents of the folders as well as opening and editing files will depend on whether you have the correct permissions. (See section Mounting an NFS File System under MS Windows NT4/2000/XP below.)

Using the NET USE Utility

To mount an exported file system, you can also use the NET USE utility of MS Windows (from the

Start/Run dialog or from the command line in the MSDOS-shell). If you use the PCNFSd server for authentication, then you can specify a user name and a password as arguments. For example, the following command

NET USE Q: \\192.168.0.38\testnfs nnm111 /USER:nnm

will mount drive Q on shared directory testnfs of node 192.168.0.38 for user nnm with password nnm111. If you use directly UID/GID for authentication, then you can specify UID instead of user name and GID instead of password as arguments. For example, the following command

NET USE Q: \\192.168.0.38\testnfs 100 /USER:117

will do the same but for UID=117 with GID=100.

The following command line is an example of mounting a network node with the WEBNFS protocol:

NET USE Q: \\192.168.0.41\WebNFS

Some software tools are able to directly open files from the WebNFS-mounted directory. For example:

NotePad -> Open -> \\192.168.0.41\readme.txt

The Permissions Tab

The Unix access permissions for new objects Box

The Unix access permissions for new objects box contains a set of check boxes that allow you to specify access permissions for different users and new files and/or new directories NFS-Client will create and operate on a remote NFS system.

Remember ROFS (Read Only File System) Reply

This check box must be enabled to block Write(), MKDIR(), CreateFile(), Rename(), SetFileAttributes() operation on NFS Servers and to return STATUS_ACCESS_DENIED. This is useful for ReadOnly exported resources, because it decreases the quantity of fault NFS-protocol requests.

Use NULL Secure DACL

This check box must be enabled for NFS-Client to specify NULL DACL (Directory Access Control List) as a parameter in any file operations (to follow security policy of modern MS Windows versions).

The Network Tab

The Network Settings Box

The Network Settings group box allows you to specify:

● Broadcast Timeout - when watching network for hosts supporting the NFS and MOUNT protocols, specifies the number of seconds that NFS-Client will wait before re-transmitting a request.

● Retry Count - when sending requests to a server, is a number of times not replying during the timeout specified before a timeout error occurs due to no response from the server.

● Timeout Period - when sending requests of the MOUNT and NFS protocols, is the absolute time in seconds that NFS-Client will wait for the server's response before returning a timeout error.

● Network Buffer Size - the size of network packets. You can choose the size from 1K, 2K, 4K 8K.

These parameters may need to be fine tuned to ensure that your NFS-Client is not sending requests faster than the server is able to reply resulting in further unnecessary network traffic.

The Network Caching Box

The Network Caching group box allows you to specify the following 'Life Time' values for time-driven renovating of file/directory attributes stored in the NFS-Client's internal cache:

● Folder Attributes Life Time● File Attributes Life Time● Read Cache Life Time

NFS-Client will preserve the original attributes for existing folders and files and will create new folders and files with the default attribute values. These are the standard UNIX file attributes.

Provider Order

In this group box, you can select a provider name from within the provider list box and then change its place in the list with the Client Up and Client Down buttons.

The Name Converting Tab

Unix-to-Windows File Name Converting

The Unix => Windows File Name Convert Mode group box allows you to specify file name conversion rules from the UNIX format to the MS Windows format.

Use suffix for equal file names

If you enable this check box, then the UNIX file names that only differ by cases will be concatenated with a two-character suffix. The second character will be changed by incrementing its code by 1. You can specify an initial value for the suffix in the Suffix for equal file names field. Default is "-0".

Show files with '.' at 1st position of name

If you disable this check box, then NFS-Client will display all file names but those beginning with a period. For the file names beginning with a period, it is desirable to substitute the first period character in the file name with another character. You can specify the character in the Use this symbol instead of '.' at 1st position of name field. Default is "_".

Show files with illegal symbols

If you enable this check box, then NFS-Client will display files with illegal symbols in filename and files with names reserved in MS Windows.

In the Use this symbol instead of illegal symbols field, you can specify a value to be used instead of illegal symbols in filenames. Default is "~".

In the Use this symbol as prefix for reserved Windows names field, you can specify a value to be used as prefix to mark the reserved file names such as AUX, CON, NUL, etc. Default is "^".

Windows-to-Unix File Name Converting

The New Windows Name => Unix Name Convert Mode group box allows you to specify file name conversion rules from the MS Windows format to the UNIX format.

New names for files and directories created or renamed under MS Windows on NFS servers will be converted to upper/lower case or unchanged depending on the mode you choose: Convert to upper case, Convert to lower case, or Preserve the case of name symbols.

Use UTF8 Name format

If you select this check box, then NFS-Client will attempt to display file and directory names using Unicode/UTF8 format. The mounting exports must still be in ANSI only.

Remember Long Name Alias

Select this check box if you want NFS-Client to preserve long file names of files that MS Windows renamed or deleted during the first 15 seconds.

When an application creates a file or directory that has a long file name, the system automatically generates a corresponding short file name (alias) for that file or directory, using the standard 8.3 format. If the long file name follows the standard 8.3 format, the alias has the same name except that all lowercase letters are converted to uppercase.

If the long file name does not follow the standard 8.3 format, the system automatically generates an alias, using a numbering scheme to ensure that the alias has a unique name. Applications can

override the default alias numbering scheme when creating a file or a directory. In a given directory, the long file name and its alias must uniquely identify a file.

If a file with a long file name is copied or edited, the alias for the resulting file may be different from the original alias. The system always generates new aliases during these operations and always chooses aliases that do not conflict with existing file names.

Applications can open, read, and write from a file using the alias without affecting the long file name. However, some operations on the alias, such as copy, move, backup, and restore, may result in the original long file name being destroyed. The system attempts to preserve a long file name, even when the file associated with it is edited by an application that is not aware of long file names.

When an application makes a system call to delete or rename an alias, the system first gathers and saves a packet of information about the file and then performs the delete or rename operation. The information saved includes the long file name as well as the creation date and time, the last modification date and time, and the last access date of the original file. After the system performs the delete or rename operation, the system watches for a short period of time (the default is 15 seconds) to see if a call is made to create or rename a file with the same name. If the system detects a create or rename operation of a recently deleted alias, it applies the packet of information that it had saved to the new file, thus preserving the long file name. (For more details, see the MSDN Library "File Name Aliases" article.)

The Advanced Tab

In this tab, you can choose the mode NFS-Client will treat UNIX links.

Do not show links

In this mode, NFS-Client will not support and display links.

Show all links as ReadOnly files

NFS-Client will display every link as a regular file with the Read-Only attribute.

Show links according to final objects (file or directory)

For every link, NFS-Client will search for its real object. If the end object exists and is accessible, NFS-Client will display the link as the object found with its attributes. If the end object does not exist or it is not accessible, NFS-Client will not display that link.

Show links with 'Hidden' attribute

With this check box enabled, NFS-Client will also display links with the 'Hidden' attribute as regular files but with another color. Otherwise, such links will not be displayed.

Use Network Lock Manager

This check box enabled allows you to control multiple access to shared files and records on NFS servers with the Network Lock Manager protocol (versions 3 and 4, using Non-monitored Lock requests). Otherwise, Network Lock Manager will not be used.

Inode number limit

This edit field lets you specify the maximal number of directories and files in an exported directory (in the range of 4000 : 128000) that will be displayed. The default value is 65000.

Enable mounting of subdirectories

With this check box selected, you can mount a subdirectory of a shared directory (if the remote NFS-Server allows that).

NFS3 write synchronization mode

You can choose Async for Asynchronous Write mode or Sync for Synchronous Write mode (for NFS-3 protocol version) that NFS-Client will use. This choice has critical influence on performance of write operations.

The About Tab

This tab contains reference information about the NFS-Client release, protocols and versions supported.

At present, NFS-Client supports the following protocols:

● NFS protocol, versions 2 and 3● MOUNT protocol, version 1 and 3● PORTMAP protocol, version 2● NLM protocol, versions 3 and 4● TCP/IP (as well as UDP) protocol at the transport level.

















Mounting an NFS File System under MS Windows NT4/2000/XP

Mounting a network drive (NFS File System)

To mount an exported file system as a network drive, you can perform the following:

1. Double-click on My Network Places and then Entire Network.

You should find the XwpNTrdr icon. (May be, you will have to select Entire contents of the network.)

2. Double-click on the XwpNTrdr and then Remote NFS Servers icons.

Another way is to run NFS Map Drive Tool from the NFS-Client's program folder. In the Map NFS Network Drive dialog box that appears, press Browse.

As a result, a list of nodes of your local network with available NFS servers (according to the settings you have made in the NFS Server tab) will be displayed in the Browse for NFS Servers dialog box.


3. Select a node you want to connect to by double-clicking on its icon.

Note: with the Use SSH-2 check box in the NFS Servers tab enabled, the Connect Remote Portmapper dialog box will appear that contains a number of actual SSH2 connections you have previously established by the SSH2 Client of the Telnet_SSH program (see Starting an SSH Session in the Starting and Terminating Telnet_SSH section on how to establish secure connections). The Refresh button allows you to renovate the list.

The "Dynamic Port Forwarding" feature of the Telnet_SSH/SSH2 Client and NFS-Client will automatically be used for connections, so you need not set up any port forwarding manually.

In the Connect Remote Portmapper dialog box, Cancel means not to use any secure connection channel available. OK with a SSH server highlighted and the Use SSH Forwarding check box enabled means to communicate with the NFS server through the secure channel established.

As a result of NFS connection to the node (through either direct insecure or secure SSH channel), you can see icons with names of exported directories (if there are any shared NFS

resources on that node).

4. Select an exported directory and press the right mouse button.

5. Select Map Network Drive in the pop-up menu. The Map NFS Network Drive dialog box will appear:

6. Select a drive letter to mount the folder and press Map Drive.

As a result, you can see the contents of the mounted directory in a separate window on your desktop (according to your Unix access permissions).

7. Then you can do the following operations with the remote NFS resource mapped to your local drive (according to your Unix access permissions):

- Creating new files and directories- Deleting files and directories- Renaming files and directories- Copying files from remote to local machine and vice versa- Viewing and editing the contents of files by WordPad, and so on.

Notes

If you use the WEBNFS protocol for mounting a shared directory, the following examples show alternative ways for mounting a network node with the WEBNFS protocol:

1. NET USE Q: \\192.168.0.41\WebNFS

2. My Computer -> Tools -> Map Network Drive -> Folder=\\192.168.0.41\WebNFS

NFS-Client can use the WEBNFS protocol if NFS servers support the WEBNFS protocol. When exporting a shared directory on a NFS server, you should specify the NFS security argument as 'none:sys'. The following is a command line example for OS SUN Solaris 8 :

share -F nfs -o public,sec=none:sys /export/home/nnmdir

Dismounting a network drive (NFS File System)

To dismount an exported file system, you can perform the following:

1. Select My Computer.

2. Select a mounted drive you want to dismount and press the right mouse button.

3. In the pop-up menu, select Dismount Network Drive.

Also, you can run the NET USE utility (e.g., for MOUNT and/or MAP). NET USE connects a computer to a shared resource or disconnects a computer from a shared resource. When used without options, it lists the computer's connections.

If you enable the Reconnect at logon check box in the Map Network Drive dialog box on the Tools menu of My Computer or Explorer, then mounting shared resources and mapping drive letters you specify will be made every time you log on (i.e. the auto-mounting mode). Mapped drives are available only when the host computer is also available.

















Installing NFS-Client under MS Windows NT4/2000/XP

Installing NFS-Client

You can install NFS-Client for MS Window NT4/2000/XP by choosing it in the Custom Setup Type (see section Running Setup in chapter Installing XSecurePro).

The Win2K NFS-Client's package for MS Windows NT4/2000/XP consists of the following files:

1. XWPFSW2K.SYS - a network file system driver (WIN2K/XP redirector)

or

2. XWPFSNT4.SYS - a network file system driver (WINNT4 redirector)

3. XWNTSERV.EXE - an executable (service) file

4. XWNTFS32.DLL - a network provider DLL

5. XWPSHELL.DLL - a property sheet DLL

6. NFSCLPAR EXE - a settings viewer/editor

7. NFSSETUP.EXE - an installing utility

8. NFSUNINS.EXE - an un-installing utility

9. NFSTRACE.EXE - a tracing utility

If installation is successful, then the following files should be seen in the MS Windows' system directory (after system restart):

● \SYSTEM32\DRIVERS\XWPFSW2K.SYS

or

● \SYSTEM32\DRIVERS\XWPFSNT4.SYS

● \SYSTEM32\XWNTSERV.EXE

● \SYSTEM32\XWNTFS32.DLL

● \SYSTEM32\XWPSHELL.DLL

The NFSCLPAR.EXE and NFSUNINS.EXE files will be placed into the home directory of the XSecurePro


package. These utilities are also accessible from the MS Windows' Start menu:

● Start->Programs->NFS Client->Settings

● Start->Programs->NFS Client->Uninstall

You can check out the registration of NFS-Client with the regedt32 system utility. Look for the following keys:

● HKEY_LOCAL_MACHINE->Software->Lab-NC->XWPNFS32

● HKEY_LOCAL_MACHINE->System->CurrentControlSet->Control->NetworkProvider->Order

● HKEY_LOCAL_MACHINE->System->CurrentControlSet->Services->XWNTSERV

● HKEY_LOCAL_MACHINE->System->CurrentControlSet->Services->XwpNTrdr

To load the NFS driver and make it active after the NFS-Client installation, you must restart your system.

Removing NFS-Client

To remove NFS-Client from your system, you should run Start->Programs->NFS Client->Uninstall. Then you must restart your system.

You can check out the result of removing with the regedt32 system utility as described above.

















Starting XServer

You can start XServer by double-clicking on the XSession icon from the XSecurePro Programs' folder.

XServer will be started in a default window mode (according to settings stored in the ini-file used). When XServer is running, you can change the current window mode by selecting an appropriate item from the XServer's Control menu or by launching the XSettings utility. (See section Using XSettings in Chapter Configuring XSecurePro.)

You can launch XSettings either from the XSecurePro Programs' folder or from the XServer's Run menu. If you save new settings from XSettings in the ini-file, then you must restart XServer to re-read the file and to take them effect.

Also, see section Using ComSetup in Chapter Configuring XSecurePro on how to make communication settings relating to the networking aspects of XSecurePro that operate with the TCP/IP transport interface.

There are some additional settings you can specify to customize your X-sessions. They are described in section The "[XSETUP]" Section of the ini-file below.


















Initiating Remote Login Sessions

Working with XServer typically includes the following steps:

1. Initiating a remote login session;

2. Starting a session manager. The first client run in a login session acts as the session manager. A useful session manager is 'xterm' or a window manager, both of which allow other clients to be run;

3. Running clients;

4. Completing the session with the session manager.

First of all a user should initiate a login session by using Telnet, XDMCP, or Startup (REXEC, RSH, RLOGIN) methods.

Note, a special case of working with clients is their starting from other X terminals without initiating remote login session on your PC. Clients have to be started with the option -display that defines your PC as a display.

The XDMCP Method

To use XDMCP, you have to run XSettings and preset the Use XDMCP check box to the enable state. You can use the XDMCP method only if you are sure that the host you want to connect to supports XDMCP and settings for XDMCP are correct there. (See section XDMCP Settings in Chapter Configuring XSecurePro.)

If you select the Broadcast XDMCP mode in the XDMCP Settings of XSettings, then the Select XDMCP Host window will appear after loading XServer. In this window, you will see the XDMCP hosts running on your network, and you can select one of them to start an X-session.


If you want to use the Query or Indirect XDMCP mode, you should specify the network node name or IP address for the host you want to connect to in the Connect Host field in the XDMCP Settings of XSettings.

After establishing the X connection, XDMCP contacts a 'xdm' process running on a host system. Then 'xdm' initiates login session as follows:

1. An optional authentication procedure takes place in which 'xdm' proves to the terminal that it is authorized to manage that display.

2. A session key is generated to be used for subsequent client authorization.

3. A username/password is requested to authenticate the user.

4. A session manager is run, typically /usr/lib/X11/xdm/Xsession, which is typically a shell script that ends up executing the required session manager such as 'xterm'.

When the session manager terminates, all other clients have their windows destroyed and should then terminate themselves. A new session is then initiated by 'xdm'.

Many XDMCP parameters may be redefined if required in /usr/lib/X11/xdm/xdm-config and /usr/lib/X11/xdm/Xresources. See manual xdm(1) for details. In particular, sites may find it useful to tailor the login window greeting in Xresources to identify the host system:

xlogin*Login*namePrompt: CLIENTHOST login:

CLIENTHOST is replaced by the host name of the system running 'xdm'.

Note: You cannot use XDMCP through SSH because SSH provides tunnelling only TCP packets (it does not provide tunnelling UDP packets).

The Telnet Method

Although XDMCP is recommended for convenience, it may sometimes be necessary to start clients without it, such as when the host system software does not support XDMCP or does not have it configured correctly. In these cases, you can run clients by typing shell commands in the normal manner. To gain access to a shell, you must first log in to the host system, for example on a dumb terminal such as the system console. For convenience, XSecurePro has the Telnet virtual terminal network interface. Start the Telnet_SSH program, connect to a host and enter commands to start clients. (See Chapter Telnet_SSH.)

Note: the Telnet_SSH and XServer programs use the same Keyboard Definition file you specified.

REXEC, RSH and RLOGIN Methods

The REXEC, RSH and RLOGIN methods can be used for automating host access and X client startup with using the REXEC, RSH and RLOGIN protocols respectively. You can use the Startup program to enter a single command line and execute one on a host, or run a local startup file that will automatically start one or more X clients. If XServer has not been running, it will start.

In order to run Startup, your host system must support the REXEC, RSH or RLOGIN protocol. REXEC operations may be done either by direct access to a remote host or through one of the established SSH1/SSH2 connections. (See Chapter Startup.)

Note: if you use Startup to start your XServer, and XDMCP is enabled, the program will switch off the XDMCP startup method. This will be done because the host XDM script will most likely run before your command or file.

The REXEC, RSH and RLOGIN session dialogs are quite similar. Each of them asks for a host name, user ID name, and command. In addition, REXEC needs to know a user password.

For RSH method, some hosts require your PC to be authorized before using RSH, as it does not require a password. On UNIX systems, you need to add your PC name to the /etc/hosts.equiv and $HOME/.rhosts files on your host.

Also, check the /etc/inetd.conf and /etc/services files on the host. The services file is a local source of information regarding each service available through the Internet. The services file must contain an entry for each service. The inetd.conf file contains a list of servers that 'inetd' invokes when it receives an Internet request over a socket.

















Terminating XServer

To terminate XServer, click on the XSession icon or a box at the top left corner of the X-session window and select the Close command from the Control Menu. Then all X client sessions will be terminated. To terminate individual X clients, use the client's standard terminate program command.

Note, XServer is also terminated by terminating Microsoft Windows.


















A Note on Copy and Paste

A number of copy and paste commands described in this chapter resemble an X Selection. In the X environment, the X Selection is a buffer with a specific name and properties that stores data you select in an X client's window.

The X Selection also serves as the source for certain XSecurePro copy commands and the target for certain paste commands.

X Selections are the mechanisms you can use to copy data from X to Windows or vice versa.

The name of the X Selection a client uses and how it is used (for text or image) depends on the client. Most use the PRIMARY X Selection, but other selections like SECONDARY and CUT_BUFFER0 through CUT_BUFFER7 are also defined. Some clients can make use of more than one X Selection.

If you find that data is not being copied or pasted, XSecurePro provides the X Selection item on the Options menu. This item lets you define which X Selection to use (see The Options Menu below).

The Auto Clipboard Copy&Paste check box (in the XSettings window) controls the mode of connection between the MS Windows Clipboard and the current X Selection. When enabled, then changing of the MS Windows Clipboard contents will force the same change in the current X Selection. Also, changing of the contents of the current X Selection (from the active application window) will automatically cause copying it into the MS Windows Clipboard (so you are ready to paste).

Also, you can control the mode of connection between MS Windows Clipboard and a current X Selection by specifying the ConnectXWClipboards setting described in section The "[XSETUP]" Section of the ini-file below.

Also, see Appendix C Troubleshooting for examples.


















Single Window Mode

This mode presents all X clients in a single X-session window. Within the window, the window management and all other functions are typically controlled by an X Window System manager you start on a host (e.g., olwm, CDE, twm, mwm, etc.).

If you want to use a remote window manager, you should use the XDMCP method or start a remote window manager from the UNIX host (e.g., start xterm and then start the required window manager from the xterm window).

The X-session window itself can be sized and moved like any Microsoft Windows window. You can use scroll bars to display all parts of the virtual screen. Pressing a scroll arrow will move the window a pixel at a time. Dragging the scroll elevator or clicking on either side of the elevator will move the window more rapidly.

Note: the local mwm program (based on OpenMotif 2.0) may be useful in this mode to provide windows managing functions (moving, resizing, etc.). This allows not using a remote window manager. You can launch the local mwm program from the X-session's Run menu.

Functions that affect XServer as a whole can be selected from the X-session's Control Menu. This menu will be presented when you click on a box at the top left corner of the X-session window.

The Edit menu gives you access to all XSecurePro Copy & Paste commands. A number of these commands specify the current X Selection as the source or target of the command (see A Note on Copy and Paste earlier in this chapter).


Example of Initiating a Login Session by Using REXEC to Start xterm

First, make sure that your remote host is accessible from your PC (e.g., with the Ping utility) and supports the REXEC protocol. Also, make sure that your PC is accessible from your remote host. If OK, then you may initiate a login session by using REXEC like the following steps:

1) Specifying required settings

● Start XSettings by double-clicking on the XSettings icon from the XSecurePro Programs' folder (the XSettings window should appear)

● Select Single from the Window Mode List

● Disable the Use XDMCP check box from the XDMCP section


● Click OK to save your settings and exit XSettings

2) Initiating X-session

● Start XServer by double-clicking on the XSession icon from the XSecurePro Programs' folder (the empty X-session window should appear)


● Start Startup by double-clicking on the Startup icon from the XSecurePro Programs' folder (or from the Run menu of XServer); the Startup window should appear


● Enter the network name or IP address for the remote host you want to connect to in the Host Name/IP Address field in the Login section

● Enter your User Name in the User ID field

● Enter your Password required for your login to the remote system

● In the Command field, enter the following line

/usr/X11R6/bin/xterm -display $(LOCALIP):0



Note: The path to xterm depends on the operating system's configuration used on the host (e.g., the path may be /usr/bin/X11/xterm).

The xterm window should appear on your display. You can then interact with the host by typing commands in the window and starting remote applications (e.g., xclock).

















Full Screen Mode

This mode presents all X clients in a single root window taking up full the screen outside the Microsoft Windows graphical environment. The window management and all other functions are typically controlled by an X Window System window manager you start on a host.

For transition from the X Window System graphical environment into the Microsoft Windows graphical environment, the ScrollLock key is used. In the MS Windows environment, the Full Screen mode displays the XSession icon at the bottom of your display. Functions that affect XServer as a whole are controlled by clicking this icon.

For transition from the Microsoft Windows graphical environment into the X Window System graphical environment, the Alt+Esc or Alt+Tab keys are used.

If you used the Virtual Root box (described in section Using XSettings in Chapter Configuring XSecurePro) to define a virtual screen larger than your display, you can display all parts of the virtual screen by moving a cursor to borders of PC's physical screen. Trying to move the cursor beyond a physical screen border results in the virtual screen moving in an opposite direction.

Example of Initiating a Login Session by Using XDMCP

First, make sure that xdm-daemon is running on your remote host and check the XDMCP configuration. Make sure that your remote host is accessible from your PC (e.g., with the Ping utility). Also, make sure that your PC is accessible from your remote host. If OK, then you may initiate a login session by using XDMCP like the following steps:




● Select Full Screen from the Window Mode List

● Enable the Use XDMCP check box and click Settings from the XDMCP section (the XDMCP Settings window should appear)

● Enter the IP address or the network name for the remote host you want to connect to in the Connect Host field

● Choose Query in the XDMCP mode section to specify requesting to the host

● Specify other required XDMCP settings

● Click OK to save your settings and exit XDMCP Settings




● Start XServer by double-clicking on the XSession icon from the XSecurePro Programs' folder (the X-session window should appear with the Login window of XDMCP)

















Multiple Window Mode

This mode provides the most integrated way to run Microsoft Windows and X on the same computer. When an X client starts, it appears in a window like any other displayed by MS Windows. Each client you start creates its own window on your display. You can have up to 2048 different top-level windows.

The client window's controls (i.e. its borders, the Control Menu box, move window functions, etc.) are all handled by Microsoft Windows on your PC. This makes for an integrated environment where you can manipulate X client windows in the same way as windows displayed by Explorer or any other MS Windows' program.

In the Multiple window mode, Microsoft Windows works as a local window manager for your X clients. Since window management functions do not have to be provided from a remote host, this mode speeds up window management functions and reduces network traffic. In this mode, XServer can work on multi-monitors PCs.

Functions that affect XServer as a whole are controlled by clicking the X-session icon.

Note: the XSession icon cannot be changed into a window in the Multiple window mode, as its only purpose is to control the overall settings for X clients that appear in their own windows.

Note: the MS Windows window manager is locally used in the Multiple window mode and any other window manager is blocked. Some remote windows managers close the X-session if they detect any other running window manager (e.g., the XDMCP method can fail because of this). In this case, you cannot use the Multiple window mode. You can use it if you do not want to use a remote window manager.

Example of Initiating a Login Session by Using Telnet to Start xterm

First, make sure that your remote host is accessible from your PC (e.g., with the Ping utility). Also, make sure that your PC is accessible from your remote host. If OK, then you may initiate a login session by using Telnet like the following steps:



● Select Multiple from the Window Mode List







3) Initiating the Telnet session

● Start Telnet_SSH by double-clicking on the Telnet_SSH icon from the XSecurePro Programs' folder (or from the Run menu of XServer); the Telnet Connect Host window should appear

● Choose Telnet in the Interface section

● Enter the network name or IP address for the remote host you want to connect to

● Change the default Telnet port number if required

● Click OK to start the Telnet session with the remote host (the Telnet window should appear)

● Specify the login information required for your host system (e.g., User Name and Password)

4) Starting the xterm program from the Telnet window

● Run the following command line:

e.g.,

/usr/bin/X11/xterm -display IP_address_of_your_PC:0&

or

/usr/bin/X11/xterm -display Name_of_your_PC:0&

(in the latter case, you should have Name_of_your_PC and IP_address_of_your_PC in the /etc/hosts file on your UNIX host).

The xterm window should appear on your display. You can then interact with the host by choosing commands from displayed menus, or by typing commands in the window and starting remote applications (e.g., xclock).

Note: The path to xterm depends on the operating system's configuration used on the host (e.g., the path may be /usr/X11R6/bin/xterm).

Note: You should not start a remote window manager after that.

The X Client's Menu

On the X client window's Control Menu, you can use both MS Windows commands and menu items added by XSecurePro.

Restore, Move, Size, Minimize, Maximize and Close all function as with any MS Windows application.

The Edit menu gives you access to all XSecurePro Copy & Paste commands. A number of these commands specify the current X Selection as the source or target of the command (see A Note on Copy and Paste earlier in this chapter).

The Edit menu presents the same set of commands displayed from the server's Control Menu in the Single window mode (see section The Edit Menu of XServer Commands below), but the Copy Rectangle, Print Rectangle, and Copy All commands affect only the current client's window.














This page is a part of XSecurePro online Help Manual. X-SecurePro is X-Server for windows by Labtam bringing your PC to Unix and X-Windows. Seamless Secure integration from PC

to Unix and X-Window System. Bringing Maximum Security while still finding all of the standard access of X11, TCP/IP, FTP, TFTP, LPR, TELNET, NFS and SSH. Visit Home of X Server for windows for more information.


Multiple+RemoteWM Mode

This mode is the above Multiple mode, but the local MS Windows window manager does not control windows of X clients and a user has to run any suitable remote window manager. The mode is very convenient when users use CDE-like interface where a remote window manager provides its own tool/task bar. In this mode, XServer can work on multi-monitors PCs.

Note that the Restore/Minimize items on the XServer menu provide "visibility" of XServer background in an additional small window. This "x-root window" may be used to control functions of the remote window manager used (usually by pressing mouse buttons).

Example of Initiating the REXEC Session to Start xterm via SSH



● your remote host supports the REXEC protocol for your PC



If OK, then you may initiate the REXEC session via SSH like the following steps:











● Run the following command lines:

echo $DISPLAYecho $XAUTHORITY

Note: You must use the results in the command line you will execute with Startup below. The DisplayNumber in the first result is greater than zero.



● Select Multiple+RemoteWM from the Window Mode List







● Launch Startup by double-clicking on the Startup icon from the XSecurePro Programs' folder (or from the Run menu of XServer); the Startup window should appear


● Enter localhost as the network name or 127.0.0.1 as the IP address in the Host Name/IP Address field in the Login section

● Enter your User Name in the User ID field (e.g., John)





● In the Command field, enter the following line (depends on the remote shell used):

export DISPLAY=Your_echo_DISPLAY; export XAUTHORITY=Your_echo_XAUTHORITY; /usr/bin/X11/xterm&

Note: You must use the same values for Your_echo_DISPLAY and Your_echo_XAUTHORITY that the echo $DISPLAY and echo $XAUTHORITY commands show you in the Telnet_SSH window above (not 127.0.0.1:0).


Startup will open REXEC to the remote host through the encrypted connection. The xterm window should appear on your display. You can then interact with the host by typing commands in the window and starting remote applications (e.g., xclock).

Note: The path to xterm depends on the operating system's configuration used on the host (e.g., the path may be /usr/X11R6/bin/xterm).

Example of Initiating a Login Session by Using Telnet to Start xterm via SSH





If OK, then you may initiate a login session by using Telnet_SSH via SSH like the following steps:



● Select Multiple+RemoteWM from the Window Mode List















● Run the following command line:

xterm&

The xterm window should appear on your display. You can then interact with the host by typing commands in the window and starting remote X applications (e.g., xclock). XServer will work with the remote host through the encrypted connection.

















XServer Commands

In the Multiple and Full Screen modes, XServer commands are displayed by clicking on the X-session icon.

In the Single mode, XServer commands can be accessed by clicking on the Control Menu box at the top left corner of the X-session window.

The top of the Control Menu presents the standard MS Windows commands (Restore, Move, Size, Minimize, Maximize, and Close).

The bottom of the menu presents XServer commands. They are described below.

The Edit Menu

When you select Edit, the Edit Menu commands are displayed:

All available Edit commands are described below.

The first item shows you the current X Selection.

Note: Whenever X Selection is the source or target of a copy or paste command, you can define the X Selection being used with the Options-X Selection menu item. This item is described in A Note on Copy and Paste and The Options Menu sections in this chapter.

Copy Rectangle

This command is available in the Single mode only. It copies a rectilinear area you select on any visible part of the X-session window (i.e. a pixel image) to the MS Windows Clipboard (regardless of the ConnectXWClipboards setting). When you choose this item, a camera icon is displayed. Click


(and hold down) the left mouse button at the rectangle's origin and drag the mouse to define the rectangle. As you drag the mouse, lines will delineate the rectangle to be copied. When you release the left mouse button, the selected rectangle will be copied to the MS Windows Clipboard. You can then save and paste this image from the MS Windows Clipboard into programs running under MS Windows that support bitmap paste.

Print Rectangle

This command is available in the Single mode only. It prints a rectilinear area you select on any visible part of the X-session window (i.e. a pixel image). When you choose this item, a camera icon is displayed. Click (and hold down) the left mouse button at the rectangle's origin and drag the mouse to define the rectangle. As you drag the mouse, lines will delineate the rectangle to be printed. When you release the left mouse button, the selected rectangle will be printed (after you will select your target printer).

Copy All

This command is available in the Single mode only. It copies all visible parts of the X-session window (i.e. a pixel image) to the MS Windows Clipboard (regardless of the ConnectXWClipboards setting). You can then save and paste this image from the MS Windows Clipboard into programs running under MS Windows that support bitmap paste.

Copy X Selection

This command copies text and graphics from the current X Selection to the MS Windows Clipboard (regardless of the ConnectXWClipboards setting). You can use an X client's selection procedure to select the data you want to copy. Once data is in the Clipboard, you can use the Clipboard to save data or paste it into any MS Windows application that supports copy and paste.

Paste to X Selection

When you choose this command, text or graphics that is in the Microsoft Windows Clipboard is pasted to the current X Selection (regardless of the ConnectXWClipboards setting). You can then use an X client's paste procedure to paste the data into an X client.

This function works for both text and graphics, although many clients do not support graphics.

Copy X Selection to File

This item lets you save any text that is in the current X Selection to a file on your PC. You can use an X client's selection procedure to select the data you want to copy. When you select the item, you will be prompted for the name of the file you want to save the data to. When you click OK, the current X Selection will be copied to the specified file.

Paste File to X Selection

This item lets you paste any text file that is on your PC to the current X Selection. When you select the item, you will be prompted for the name of the file you want to paste. When you click OK, the

specified file will be pasted to the current X Selection. You can then use an X client's paste procedure to paste the X Selection into an X client.

Clear X Selection

This item will be grayed unless XServer has control of the X Selection.

Whenever you choose the Paste to X Selection or Paste File to X Selection commands, XServer takes control of the X Selection. You can use the Clear X Selection function to clear the buffer and free the memory required to maintain it.

Note: This function can also be performed by making another selection in an X client application.

The Options Menu

The Options menu controls options that affect the operation of XServer as a whole. When you select Options, the Options Menu commands are displayed:

All available Options commands are described below.

X Selection

This option determines an X Selection that will be used by the XServer's Copy X Selection, Paste to X Selection, Copy X Selection to File, Paste File to X Selection and Clear X Selection commands of the Edit menu.

Whenever you select this option, a dialog box appears on your display prompting you to specify which X Selection you want to used. The current choice will appear at the top of the Edit menu. Use the mouse to select the choice you want from the list box and then click OK.

Most X applications use PRIMARY. For X clients that support SECONDARY, CLIPBOARD, or CUT_BUFFER0 through CUT_BUFFER7, you can change the current X Selection by selecting it from the list.

Note: you can also use the edit field at the top of the dialog box to enter a name for a custom X Selection. This is only useful if the name is defined by an X client. If you do this, the name will be saved and will appear in the dialog box whenever you select this option.

Minimize on Activity Losing

This option is only available in the Full Screen mode. If you select this option, the XServer's window will be iconified each time the focus changes to another window. Otherwise, it can be obscured by other windows.

Enable Animation

The Enable Animation mode provides careful operations with colors while drawing. Note that this mode decreases performance of XServer.

Local NumLock Processing

If this option is enabled, then XServer will process numeric keypad keys, depending on the (local) NumLock key state, and results will be sent to X clients. Otherwise, X clients process the keys (remotely).

Unlock NumLock

This option corresponds to the Unlatched NumLock check box in the XSettings window. If this option is enabled, XServer will consider the NumLock key as a normal key (non-toggling). The NumLock key is unlocked by default. This option was implemented to suppress the NumLock state's influence on some X-window managers and programs.

If Colormap Changed

The If Colormap Changed menu lets you specify XServer response to the hardware colormap (Windows system palette) changes. An X client can require installing its own colormap into the hardware colormap when the user indicates that the application should be active. When this occurs, all other applications can appear in false colors. As soon as you change input focus to another X

client, you expect to see right colors displayed in its windows as well as windows using the same colormap as the X client.

XServer regenerates colors of windows using a policy specified by one of the following options:

Redraw

This option causes redrawing the active X client windows as well as windows using the same colormap as the X client.

Update Colors

If you choose this option, XServer will directly update the colors in all the X client windows when you activate an application that requires changing the hardware colormap. The option provides a reasonable compromise between performance and color accuracy.

Note that this option is not supported by some video drivers.

If you do not check any of these options, XServer will do nothing to regenerate colors of windows when changing the hardware colormap. The colors displayed in all the X client windows will potentially be incorrect until the windows update their display. You can redraw all X client windows by choosing the Refresh or Local Refresh item from the XServer's Control Menu.

Move Window to (0,0)

Implemented in the XServer/Multiple Control menu, this option allows users to move any window to the upper left corner of the Windows screen. This feature is useful to view an invisible window when it is out of the visible screen.

Connect LbxLoxy Server

The LbxLoxy Server is a Low BandWidth X proxy derived from sources of the lbxproxy (included in XFree 4.10). In addition to its original capabilities, LbxLoxy can wait for connection to a remote X server instead of initiating the connection itself. Thus, when external connections to XServer are prohibited (e.g. by a firewalling proxy) XServer can initiate a connection to a listening socket for LbxLoxy.

Connection to the running remote LbxLoxy Server may be done through either the direct access insecure channel mode or the secure (SSH) channel mode. See section Using LBX below on how to use Low Bandwidth X (LBX) network-transparent protocol for running X Window System applications.

When you click the Connect LbxLoxy Server item, the Connect Remote LbxLoxy dialog box will appear.

You can see a list of actual SSH1/SSH2 connections you have previously established (for example, by the SSH1 or SSH2 Client of the Telnet_SSH program). (See Starting an SSH Session in section Starting and Terminating Telnet_SSH on how to establish secure connections). The Refresh button allows you to renovate the list.

If you want LBX operations to be done in secure connection mode, select a desired remote host (an active SSH server) from within the list and enable the Use SSH Forwarding check box. In the SSH1/SSH2 mode, the "Dynamic Port Forwarding" feature of the Telnet_SSH/SSH1 or Telnet_SSH/SSH2 Client and XServer will automatically be used, so you need not set up any port forwarding manually.

If you disable the Use SSH Forwarding check box then the direct access insecure mode will only be used for LBX operations.

If the LBX server and SSH server you are using in the X-session are on the same remote host then the Host field can contain "localhost" or "127.0.0.1". This is more preferable than its actual IP address in most cases (but depends on how the host has been configured).

In the Port field, you specify a port number that will be listening for connection from XServer (default is 6163).

Open a login session on a remote host.

Run lbxloxy on the remote host with option '-waitXServer[:port]' where port is a port number that will be listening for connection from XServer (default is 6163):

$ ./lbxloxy -waitXServer:6163 &

or (default)

$ ./lbxloxy -waitXServer &

When connection is established, lbxloxy will open a display port for listening (default is 6163). For convenience, you may set the DISPLAY environment variable:

$ export DISPLAY=:63.0

After that, you are able to run your remote X application(s).

The Macros Menu

This menu lets you create macro-files to remember sequences of your keystrokes. A sequence of remembered keystrokes is called a keystroke macro. Then, whenever you want, you can play back these keystroke macros in a target application window by choosing an appropriate macro-file. Keystrokes are remembered in macro-files as ASCII strings in a special syntax, so you can use text editors (e.g., Notepad) to edit the files. By default, macro-files have the .mac extension and reside in the package's home directory.

Record Macro

When you click on this item the standard Save As dialog box named as File for Macro Recording appears. You can specify a macro-file name you want to record macro to. Pressing Save opens the specified file for writing and turns on the record macro mode. Then, in the target application window (e.g., Terminal), you perform the keyboard actions you want remembered. The mode is effective until you click on the Stop Macro item on the Macros menu or in the Macro recording is running information box, which indicates that the mode is on. Before using the Record Macro option get your target application to the point where you are ready to type the first keystroke of the macro.

Play Macro

This option lets you select a macro-file you want to play back. When you select a file from the macro-file list it is played back immediately in the active X client's window (with actions depending on the application type, e.g., Terminal or Text Editor). If a macro was created for a particular application, you can play it back whenever you are working in that application. Before using the Play Macro option get your target application to the point where you want to play back the macro.

Stop Macro

You use this option when you have finished the last keystroke of the action you want to record. This option turns off the record macro mode and closes the current macro-file. Now you can play back the macro-file just created or any other available one.

Edit Macro

When you click on this item the standard Open dialog box named as Macro File to Edit appears. You can choose a macro-file you want to edit. Pressing Open invokes Notepad for you to edit the file specified.

Notes

1. It is not recommended to edit macro-files with Notepad.

2. Nested macro-files are not allowed.

3. One way you can take advantage of macro-files is substituting a keysym for a key (defined in a keyboard definition file) with a keystroke sequence (defined in a macro-file). Appendix A, Keyboard Mapping File Format, describes normal keysym statement syntax. The extension to this is that a keysym can have the form of prefix MAC_ followed by a macro-file name. For example, the keysym statement in a kmf-file (with onF11 referencing to macro-file onF11.mac) may appear as

KEY87 = MAC_onF11, 0xffc8; (XK_F11,XK_F11)

The Run Menu

This menu lets you launch a number of XSecurePro's programs listed below. To run one of these programs, click its name on the Run menu of XServer or from the X-clients Program Folder of the package (when XServer is running). (In these cases, the programs are called with parameters specified by XServer.)

XServer Settings

The XSettings utility changes information stored in the ini-file, including settings used by XServer.

Note that you have to restart XServer after having changed any settings made by XSettings (in the ini-file).

Font Manager

The Font Manager allows you to view fonts accessible for X clients in the current X-session and change font settings.

Telnet

The Telnet_SSH utility starts terminal emulation with a remote system running the Telnet or SSH1/SSH2 service.

XStartup

The Startup utility uses the REXEC, RSH, RLOGIN, or Telnet protocols to access hosts and then execute commands (e.g., to launch X clients).

LPR

The LPR utility prints files on printers attached to remote hosts on your network.

LPD

The LPD utility allows you to control access to your local (attached to your PC) and Microsoft-network-accessible printers for LPR-tasks from remote computers across your TCP/IP network.

FTP

The FTP utility transfers files to and from a remote computer running the FTP server.

ComSetup

The ComSetup utility makes communication settings relating to the TCP/IP transport interface.

Local X Clients

The XSecurePro package includes the following local X and Motif clients:

● mwm (based on OpenMotif 2.0)● glxinfo (the GLX extension local X Client)● glxgears (the GLX extension local X Client)● xclock● xev● xfd● xfontsel● xkill● xlsfonts● xmodmap● xprop● xrdb● xset● xshowcmap● xwininfo

They have the same functionality and command line syntax as related remote (UNIX) ones, but were developed to be run under MS Windows, so you can use them the same way.

To run one of these programs, click its name on the Run menu of XServer or from the X-clients Program Folder of the package (when XServer is running). (In these cases, the clients are called with parameters specified by XServer.)

You can take advantage of the local X clients when remote (UNIX) ones are inaccessible or inconvenient to run.

For more information about these programs, please refer to Appendix F Local X and Motif Clients.

Other Commands on the X Client's Menu

The Refresh Item

This option is only available in the Multiple window mode. This option causes all X clients to re-display their windows.

The Local Refresh Item

This option lets you re-display all X clients' windows locally (by XServer, not X clients).

The Restart XServer Item

This option lets you restart XServer with closing all X clients and re-reading the ini-file used for the current X-session (that stores all XSecurePro's settings). The default ini-file is xwp.ini.

The Messages Item

This item displays server related information and error messages.

The About Item

This item displays information about your XSecurePro package.

The Help Item

This item displays the on-line help text of this chapter.

The Local Window Manager Item

This run-time setting is used in the Multiple window mode to switch on the local Window manager (for example, after XDM/CDE starts with faults).

The Readme & Ordering Info Item

This item uses Notepad to display the readme file.

















Running XServer with Command Line Parameters


You can launch XServer (and begin your X-session) with the 'xini' command line parameter:

PATH\xserver.exe -xini <IniFilePath>


This feature allows you to run several X-sessions each with its own ini-file (i.e. settings).

In order to do so, you can create a new X-session shortcut (e.g., in the XSecurePro Programs' folder) and fill in the Target field in Properties of it with the command. For example, the Target field in Properties of the X-session shortcut might contain the following line:

"PATH\xserver.exe" -xini myxwp1.ini

By default, the field contains a call of XServer with no arguments, and the xwp.ini file will be used in this case.

To create your specific ini-file, you can copy the xwp.ini file and then change required parameters with the XSettings utility by starting it with the same command line parameter (see section Running XSettings with Command Line Parameters in Chapter Configuring XSecurePro).

Note: when launched from the XServer/Run menu, ComSetup, XSettings, Startup, Telnet_SSH and FTP use the same ini-file as XServer does.


















Running Several X-sessions

Different X-sessions running simultaneously on your PC must use different Display Numbers. So you have to launch each X-session with a proper ini-file specified in a command line when invoking XServer. These ini-files must differ at least by Display Numbers. You may specify other settings of the ini-files as different as you need for particular X-sessions.

Example

1. Create two copies of your current ini-file, xwp.ini, with names session0.ini and session1.ini

2. Create two copies of the XSettings shortcut with names XSettings0 and XSettings1 and specify the ini-files for them respectively

3. Launch XSettings with XSettings0, specify 0 for Display Number, and exit


5. Create two copies of the XSession shortcut with names XSession0 and XSession1 and specify the ini-files for them respectively.

Another way (without creating two XSettings shortcuts) is as follows:

1. Create two copies of your current ini-file, xwp.ini, with names session0.ini and session1.ini

2. Create two copies of the XSession shortcut with names XSession0 and XSession1 and specify the ini-files for them respectively

3. Launch X-session with XSession0, launch XSettings from the XServer/Run menu, specify 0 for Display Number, and exit from both programs

4. Launch X-session with XSession1, launch XSettings from the XServer/Run menu, specify 1 for Display Number, and exit from both programs

Now you can run these two XSessions at the same time - XSession0 with Display Number 0 and XSession1 with Display Number 1 (both for your display).

If you want three XSessions to run simultaneously, then, in addition to above:

1. Create a copy of one of your ini-files and give it a name session2.ini

2. Create a copy of the XSettings shortcut with a name XSettings2 and specify the ini-file for it


4. Create a copy of the XSession shortcut with a name XSession2 and specify the ini-files for it.


Then you may run these three XSessions at the same time - XSession0 with Display Number 0, XSession1 with Display Number 1 and XSession2 with Display Number 2 (all for your display).

To specify an ini-file in these shortcuts, see section Running XServer with Command Line Parameters in this chapter.

Another way to launch several X-sessions simultaneously is to use the DynamicDisplayNumber, XTcpPort, and XsessionTitle settings described in section The "[XSETUP]" Section of the ini-file below.
















18. X Development Kit < previous | content | next >

Introducing the XSecurePro X Development Kit

The XSecurePro X Development Kit (XDK) is a software development package designed to allow software developers to design and port existing X Window applications from UNIX, Linux or VMS systems to the Microsoft Windows PC platform.

The XSecurePro XDK is the X Development Kit, i.e. it is the software development environment to create X applications (or X clients). The XSecurePro XDK provides possibility to compile and link X clients by using Microsoft Visual C++ Studio (Version 6.0). A ported X application is a Win32 executable. You can run it under MS Windows (within the run-time X environment, which is another part of the XSecurePro XDK).

Local X support provided permits X clients to be started and/or displayed locally or remotely on available X servers in the network. A ported X application uses an X server on an MS Windows machine just like any other UNIX X client communicates with an X server for displaying the windows.

In order to develop X clients, you must have programming knowledge of Microsoft Windows 9x/ME/NT4/2000/XP and the X Window System. This chapter assumes that you have the necessary programming expertise.

About the XSecurePro XDK

The XSecurePro XDK is a set of various .DLLs, include-files, and libraries (i.e., all the X Window System standard libraries and toolkits) that you can use to develop GUI or console X client applications that run on your PC under MS Windows instead of a UNIX or Linux host. You can develop a local X client from scratch using the XDK, or you can port the code of an existing UNIX or Linux X application and rebuild the project so that the application runs locally (i.e. on a PC under MS Windows).

The XSecurePro XDK also includes Motif libraries and include-files for developing local Motif clients. Local Motif clients are clients that use the current implementation of the OSF/Motif Widget set and are built to run on your PC under MS Windows instead of a UNIX host.

The current version of the XSecurePro XDK supports X11R6.6 and Motif 2.2.2.

The XSecurePro XDK provides support for X-Clients that use the GLX extension. The corresponding ".h" and ".lib" files are added to the XDK file set. The XSecurePro XDK also includes four sample GLX X-Clients (as MS VS 6.0 projects with sources).

To create a local X client application, you can use the contents of the XSecurePro XDK in conjunction with the Microsoft Visual Studio 6.0 application development tool.

Installing the XSecurePro XDK


You can install the XSecurePro XDK by choosing its item in the Custom Setup Type (see section Running Setup in chapter Installing XSecurePro). As a result, the directory and file structures described below will get created.

















What is in the XSecurePro XDK

The XSecurePro XDK supplies the following directory and file sets:

● DLL files● LIB files● Resource files● Template project files● Sample project files● X11 locale files● X11 header files

The directory structure after installation of the XSecurePro XDK is as follows:

home - the directory in which the XSecurePro package is installed.

The home directory includes:

● local X and Motif clients executables● DLL files used as parts of the run-time X environment● resource files .Xdefaults, .motifbind, and .mwmrc

home\x11\app-defaults - the directory to store resource files for newly developed X applications

home\x11\locale – the directory that contains files to support all major European languages, as well as Japanese, Chinese, Korean, and Hebrew

home\XDK\AppWizard - the directory with a standard project template for MS Visual Studio 6.0, XwpXDK

home\XDK\Include - the directory with X11 header files

home\XDK\Lib - the directory with LIB files

home\XDK\projects\Sample20 - a sample project based on Motif

home\XDK\projects\Xclock - a sample project based on Xaw

These file sets are described in detail below.

DLL Files


The XSecurePro XDK contains the following DLL files resided in the home directory of the XSecurePro package:

● glx_mesa.dll● libGL.dll● libGLU.dll● libGLUT.dll● libice.dll● libsm.dll● libxi.dll● libxp.dll● xlib.dll● xwpmrm.dll● xwpxaw.dll● xwpxm.dll● xwpxmu.dll● xwpxt.dll

These DLL files are used as parts of the run-time X environment (i.e. where an X client executable should be when it will be running).

LIB Files

The XSecurePro XDK contains the following LIB files placed in the home\XDK\Lib directory:

● libGL.lib● libGLU.lib● libGLUT.lib● libGLw.lib● libICE.lib● libMrm.lib● libSM.lib● libXI.lib● libXmu.lib● libXp.lib● libXpm.lib● Xaw.lib● Xlib.lib● Xm.lib● Xt.lib

These LIB files are used as parts of the development-time X environment (i.e. while developing an X application). With MS Visual Studio 6.0, you can automatically create LIB files when you are creating corresponding DLL files.

These libraries are typically located (on UNIX) in the /usr/X11R6/lib directory while the corresponding header files are located in the /usr/X11R6/include directory.

Resource Files

Resource files for X applications are binary or text files written in the standard format to describe application options. Some of resource files (e.g., .Xdefaults, .motifbind, and .mwmrc) are placed in the home directory.

We recommend you to keep resource files for newly developed X applications in the home\x11\app-defaults directory (where the resource file for the xfb application is already placed).

Project Template

The XSecurePro XDK contains a standard project template for MS Visual Studio 6.0, XwpXDK. This project is automatically included into the MS Visual Studio environment (i.e. in its template library set) when you install the XDK package.

You should have MS Visual Studio already installed before installing XDK. You can open and use the standard project as a template project for developing your own X application (e.g., from the XDK/Projects Program Folder of XSecurePro).

The template operates within the user interface of MS Visual C++ Studio 6.0. You can use it to create an empty X project that has the proper include paths, preprocessor definitions, and link libraries.

Sample Projects

The XSecurePro XDK supplies source codes for a number of X clients placed in the home\XDK\projects directory of the XSecurePro package.

Xclock is a sample project based on Xaw. Sample20 is a sample project based on Motif. Atlantis, GLw, glxinfo, and glxgears are sample projects based on GLX extension and Graphics Library Utilities Toolkit (GLUT). Source codes for the projects are taken from the open Xfree Toolkit.

You can compile and link them to build corresponding executable modules (in the MS Visual Studio 6.0 development-time environment). Then you can run the executables in the run-time environment (by placing them in the home directory or specifying it as the working directory in MS Visual Studio).

You can study and use these source codes (as well as many others from the open Xfree resources) as template source codes and good examples of X clients modified to run locally for writing your own X application code.

X11 Locale Files (International Support)

The XSecurePro XDK includes extensions that support user input of the Euro and Latin-9 currency symbols.

The XSecurePro XDK provides support for developing and running X applications using all major European languages, as well as Japanese, Chinese, Korean, and Hebrew. The corresponding files are placed in the home\x11\locale directory of the XSecurePro package.

Locale aliases are supported. You can specify your locale alias in the locale.alias file in the home\x11\locale directory.

Local X and Motif Clients

XSecurePro includes the following local X and Motif clients all of which were developed (to be run under MS Windows) with the X Development Kit supplied with the package.

● mwm (based on OpenMotif 2.0)● glxinfo (the GLX extension local X Client)● glxgears (the GLX extension local X Client)● xclock● xev● xfd● xfontsel● xkill● xlsfonts● xmodmap● xprop● xrdb● xset

● xshowcmap● xwininfo


For more information about these programs, please refer to Appendix F Local X and Motif Clients.

















Developing Local X Client Applications

You can use the XSecurePro XDK to develop local X clients. Local X clients are X client applications built to run on a PC (under MS Windows) instead of a UNIX host.

Local X support permits X clients to be started and/or displayed locally or remotely on other X servers in the network. Local X support also permits local X clients to run on stand-alone PCs without network support.

To create a local X client, you can use the contents of the XSecurePro XDK in conjunction with the MS Visual Studio 6.0 application development tool.

The XSecurePro XDK lets you create two types of local X client applications:

● GUI application (Win32) - Makes use of the Local X Console application to display output.

● Console application - Runs in a DOS shell. These X applications use STDIN for console input and STDOUT and STDERR for console output.

You can create a local X client of either type with one of two methods: you can write your own code from scratch, or you can port an existing X client from the UNIX or Linux host to your PC and rebuild it. For both methods, your X client code must reflect the differences between the X Window System (as described in the MIT documentation) and the XSecurePro XDK.

X Window Application Development Overview

This section describes XSecurePro XDK particulars that you need to understand in order to develop a local X client application program.

Overview of X Window System

The X Window System, typically referred to as X (or X11), is a network transparent windowing system based on the client-server model. X is a combination of:

● The X Display Server● X Clients● The X Protocol● Xlib

The X Display server (or X server) is the process executing on a workstation and managing the graphics output and input from the workstation display (i.e., its monitor(s), keyboard, and mouse).

X Clients are applications that use the workstation display. The X clients, whether running locally or


on a remote computer, send request to the X server using a communication channel. The X client application and the X server can run on the same machine.

X Clients communicate with X servers (usually through a network) using the X Protocol. In the X Protocol, data is exchanged in an asynchronous manner over a two-way communication channel that enables transmission of a stream of 8-bit bytes.

All X needs is a reliable data path between X clients and the X server. As long as there is a common networking protocol (e.g., TCP/IP) available for data transfer, the X server can display output from any X client regardless of the operating system under which the client executes.

Xlib is a library of more than 300 utility routines that programmers use to access the X protocol. The Xlib functions are used to accomplish the major tasks in an X application.

With X running on a workstation, the X server is listening to the network connections at a specific port and acting on the X protocol requests sent by X clients. The X server manages regions of the screen known as windows, where the output from an X client is displayed. When X applications are running, everything on the screen appears in windows and each window is associated with a specific X client.

Creating a window is one of the basic X protocol requests that an X server handles. The X server considers anything you do with the keyboard and mouse as events to be reported to the X clients. When you press and release a mouse button, the X server sends these input events to the X client that created the window containing the mouse pointer. The X server also sends another kind of events to X clients. These events inform an X client if anything happens to its window.

It is very difficult to build a large application with Xlib. X Toolkits, another set of routines to implement commonly created window objects, such as pushbuttons, lists, and menus, can be used to build a graphical user interface (GUI). The X Window System comes with the X Toolkit (Xt) intrinsics that use an object-oriented approach to implement basic building blocks called widgets. Other toolkits, such as the Motif toolkit (Xm) from the Open Software Foundation (OSF), use a higher level of abstraction.

X applications primarily call routines from a toolkit. The toolkit may call routines from Xt, which in turn call Xlib. An X application might also make some direct calls to some Xlib routines for generating text and graphics output in a window.

The current version of X Window specification is 11 and hence the name "X11" is used. There are different revisions in version 11. The revisions currently in use are R5 and R6.

Structure of a Typical X Application Program

A typical X application program has three major sections:

● Initialization● Event Loop● Clean-Up

The initialization section sets up the window system for user interaction. In this system, it invokes the routines provided in X11, Xt, and Xm libraries to draw the various windows and graphics. The call XtAppInitialize() provided by the X11 library creates a top-level window for the application. All the other windows are created as children of this top-level window.

After initialization, the program enters a loop in which it repeatedly tries to get events from the

window system and processes them. The call XtAppMainLoop() provided by the X11 library is for entering the event loop.

Finally, before exiting, the program performs any necessary cleanups. Usually the exit code is in a program that is called when the user clicks on the Exit button provided by the application (or on the Close button on the window frame on the right top of the window).

Specifying Resources

All X Window programs have associated resource files where options for colors, fonts, etc in the application can be specified. To take advantage of this capability, programs should be written such that hard coding of resources is avoided, so that resources specified in the configuration files are used.

The resource configuration file for an X application will have the same name as the application specified in the call to XtAppInitialize(). It can be located in the directory where the application is launched, or else X will search for this file in the directory specified by the variable XAPPLRESDIR.

We recommend you to keep your resource files for newly developed X applications in the home\x11\app-defaults directory of XSecurePro (where the resource file for the xfb application is already placed).

Building an X Window Application

An application code is written in C or C++ and compiled using any of the available C/C++ compilers in the system. All source code must be compliant with X11 standards.

An X application needs to be linked to the X libraries, X11 (for Xlib), Xt (for Xt), and/or Xm (for the Motif toolkit).

To build your application (i.e. to create an executable), you can use either GUI (e.g., the Build menu item in Microsoft Visual Studio 6.0) or the command line mode (i.e. by using Makefile).

To create the X application executable (the .exe file), you compile and link your application as a Microsoft Windows 9x/ME/NT4/2000/XP application.

When creating a GUI application, you also need the standard files required for compiling and linking a Microsoft Windows 9x/ME/NT4/2000/XP application (for example, an .rc resource file).

Preparing Your Code

You need to prepare the source code for your X client for MS Visual C++ development in the following way:

1. Make the following changes to the source code:

a) If you are creating a GUI application X client, change all instances of the fprintf function to STDERR or STDOUT to calls to printf, lprintf, or some other means of displaying output.

b) Change memory allocation and de-allocation routines to their Xlib counterparts.

2. Check for any incompatibilities between MS Windows 9x/ME/NT4/2000/XP and UNIX, including

the following:

a) Ensure that there is no UNIX-dependent code that is incompatible with MS Windows 9x/ME/NT4/2000/XP. For example, you must rewrite code that uses such items as timers, mailboxes, and STDIN (for GUI applications).

b) Ensure that the code does not use any keywords reserved for the MS Windows 9x/ME/NT4/2000/XP C compiler as variables, labels, or application-defined function names.

3. Ensure that all functions are properly prototyped.

4. Ensure that the compiler and linker options are correct. You can find the correct options in the sample make files in the source directory.

Building an X Application in MS Visual Studio

To create and build your X application (i.e. to create an executable) in MS Visual Studio 6.0, you can use the following procedure:

1. Create an empty MS Visual C project:

a) On the File menu of MS Visual Studio C++, click New and then click the Projects tab.

b) In the main window of this tab, select either Win32 Application (for a GUI application) or Win32 Console Application (for a console application).

c) Specify a location for the project. You can browse for a location or type one directly into the field.

d) Specify a project name and click OK.

e) In the resulting dialog box, choose to create an empty project and click Finish. Scan the resulting new project information to make sure it is correct and click OK.

2. Customize the project to work with the XSecurePro XDK:

a) On the Project menu, click Settings and then click the C/C++ tab. In the upper left of the tab, from the Settings For drop-down list, select All Configurations. (All of the subsequent settings described in this procedure, regardless of the tab on which they are located, should be for All Configurations).

b) Also on the C/C++ tab, from the Category drop-down list, select Code Generation. From the Use run-time library drop-down list, select Multithreaded DLL.

c) Still on the C/C++ tab, from the Category drop-down list, select Preprocessor. In the Additional include directories field, type the XSecurePro XDK include path (the location at which you have installed the XSecurePro XDK include files).

d) Click the Link tab of the Settings dialog box. From the Category drop-down list, select Input. In the Additional library path field, type the XSecurePro XDK lib path (the location at which you have installed the XSecurePro XDK lib files).

e) When finished, click OK to save the settings and close the dialog box.

3. On the Project menu, click Add To Project and then Files. Add all source files to your project.

4. On the Project menu, click Settings and then click the Link tab. From the Category drop-down list, select Input. In the Object/library modules field, type the names of the necessary libraries for your X client.

When finished, click OK to save the settings and close the dialog box.

5. On the Build menu, click Build ProjectName (where ProjectName is the name for your project that MS Visual Studio automatically inserts into the menu item).

6. On the Build menu, click Execute ProjectName (where ProjectName is the name of your project that MS Visual Studio automatically inserts into the menu item).

Using Imakefile and xmkmf

Normally, you should have or create a Makefile and run it in the command line mode (within some development-time environment) to build your application.

Typically a Makefile is created for compiling and building an X application as it involves references to many X11, Xt and Xm library paths, include paths, etc. X Window system developers typically use a utility called 'xmkmf' to generate the Makefiles for building X applications (with the 'make' UNIX system command).

Imakefile is the input to xmkmf, and provides the necessary information specifically required for building an X application, such as the file names, installation directory, library names, paths, include paths, etc.

System-related information, such as specific compiler flags required and basic include and library files and paths, are stored in various system configuration files. These system configuration files are used by xmkmf along with Imakefile to generate the Makefile for an application.

You can write your Makefile from scratch but this way is rather tedious. Or, as a source template, you can use a Makefile from MS Windows SDK (in this case, you may have to make minimal edits in the make file) or UNIX SDK (in this case, you must make some edits in it).

Building an X Client Using a Makefile

You can build an X client using a Microsoft Visual C++ Makefile. To build an X client using a Makefile:

1. Locate the source files for your X application (either files you have written from scratch or ones you have copied from the UNIX host to your PC).

2. Create a Makefile that contains the proper XSecurePro XDK include and library paths.

3. Build your X application.

Running an X Window Application on Microsoft Windows

To run an X application (on MS Windows or any other operating system) one needs an X server. The X server is available on all UNIX machines, typically supplied by the operating system vendor.

The X servers running on MS Windows (e.g., XServer of XSecurePro) can be considered as X Window emulators on MS Windows. They work in two modes: Single Window mode or Multiple Window mode.

In the Single Window mode, all X applications run within one single window. The advantage of this mode is that users get access to a complete X desktop, which gives access to various X applications.

In the Multiple Window mode, each X application runs within a separate window. In this mode, the X Window resource usage on the X server is lower compared to the Single window mode.

For more information, refer to sections Single Window Mode and Multiple Window Mode in chapter Using XServer.)

Setting the DISPLAY Variable

Any X application uses the variable DISPLAY to determine where the X server is located. Therefore, you must set the DISPLAY explicitly even when the application is running on XSecurePro (even though you might expect the application to use the X server on the local machine).

If you run an X client from XServer of XSecurePro, DISPLAY is set to 127.0.0.1 (i.e. to localhost). If you try to run the X application directly (say by double-clicking the application icon in Explorer) then the value for DISPLAY should be set in the MS Windows environment or passed directly to the X application via the command line in the shortcut. In XSecurePro, if you do not specify the command line parameter for DISPLAY, the default value will be 127.0.0.1 (i.e. localhost).

Using Multiple Screens for Local X Clients

The XSecurePro XDK lets you use different screens with your local X clients. If the display name is specified as :0.S (where S is the screen number), Xlib assumes that the local client is to be displayed locally to LOCALPC:0.S.

Re-directing Standard Output

Typically, X Window applications are started on UNIX from a terminal. All the standard output calls direct the output to this UNIX terminal. If the application is not started from a terminal, the output goes to /dev/null.

In MS Windows, when an X client application is launched by double-clicking the application icon in Explorer, a command window is started and all the standard output is re-directed to it.

Font Usage

Some X applications might use fonts specifically provided by an X server on the existing system (on UNIX), which need not be provided by the X server running on your PC. If this is the case, then the program might not display the fonts properly or even crash during run-time giving error messages.

The solution to this problem is to replace such fonts with the fonts available in XServer of XSecurePro. (Refer to chapter Font Control.)

















Porting X Window Applications to XSecurePro

When porting any application to XSecurePro, the first step is to ensure that the build environment is fully set up on XSecurePro.

Quite often, codes for X applications are generated using specific tools. If your code is created using a code generator and the code generator is not available on XSecurePro, you must take the code that was generated using the code generator to XSecurePro and port it.

The next step is to compile the source code and resolve issues as they appear. Typical issues are related to path differences, potentially non-existent device files, environment differences, etc. You might need to modify the paths for including the X11 and/or Motif include files and libraries.

There could be differences in the header files and in specific APIs, or there may be missing header files and APIs. The differences can be resolved by writing XSecurePro implementations for the APIs and header files.

If your applications include scripts, such as Perl scripts, these will have to be modified to account for the platform differences.

If you are porting a GUI application client receiving input via STDIN, use an alternate method of receiving input, such as a Windows dialog box.

Memory Management

Xlib contains its own memory management routines, including Xfree, Xmalloc, and Xcalloc. In order to maintain compatibility with future versions of the XSecurePro XDK, use these routines instead of Microsoft WIN32 memory management routines.

Memory allocated by these Xlib routines should be freed using Xlib routines. Similarly, memory that is freed using Xlib routines should be allocated by Xlib routines.

The gethostname Function

Xlib.dll exports the gethostname function. A function by this name is also exported by the Windows Sockets DLL.

We do not recommend that you use the Xlib.dll version of this function; it is provided by Xlib only for backwards compatibility. In order to ensure that you are using the Windows Sockets version of this function, and not the Xlib.dll version, your link statement must include WSOCK32.lib before Xlib.lib.


Setting the Locale for an X Client

The default value for the run-time control variable XLOCALEDIR is home\x11\locale. The locale.dir file is in the home\x11\locale directory.

Locale aliases are supported. You can specify your locale alias in the locale.alias file in the home\x11\locale directory.

Accepting Localized Input

X11R6 XIM support is included on the X server side. This support lets local X clients accept localized input when displaying to an X server that supports X11R6 XIM (such as XServer in XSecurePro).

Restrictions on Developing X Applications with XDK

There are some restrictions on developing an X application code with the XSecurePro XDK:

● You cannot directly use WinSock API

● As sockets interface, the BSD sockets interface is implemented in XDK

● There are no equivalent substitutes for some UNIX system calls/requests (e.g., fork, signal, pipe, etc.)

● The source errno.h file for an X application may require some changes in the application source code; in some cases, you can also use the xeerrno.h file in the home\XDK\Include\Sys directory of the XSecurePro package

● Some other restrictions.

















Appendix A Keyboard Mapping File Format

Keyboard Mapping File Format

The Keyboard Mapping file has two sections, [KEYS] and [COMPOSERS_XKK], each consisting of keysym statements and possible comments. Text entered after a ';' sign is ignored and will be treated as a comment.

A keysym specification uses a set of standard X numbers to describe a symbol. For example, a lowercase 'a' has a special number code.

The KEYS Section

In the [KEYS] section, each keysym statement associates a set of one to four keysyms with a physical key.

Synopsis of a statement is:

KEYnn = keysym1 [, keysym2 [, keysym3 [, keysym4]]]

'nn' is the identifying number of a PC's key. Every PC's key has an entry in the section. The entry name is the text KEY followed by the decimal ScanCode number (key_number) and followed by the letter 'E' if the key has the extended flag set.

keysym1 is the keysym associated with the key in a non-shifted state (Normal). This is the only parameter that must be entered.

keysym2 is the keysym associated with the key when the key is Shifted.

keysym3 is the keysym associated with the key when a Mode-Shift key is pressed (Alt-Gr).

keysym4 is the keysym associated with the Shift + Mode-Shift sequence (Shift + Alt-Gr).

A Mode-Shift is a physical key which has a keysym value of 0xFF7E, (predefined as the ModeSwitch symbol), and which is assigned to one of the modifiers MOD1 to MOD5.

A full keysym specification consists of four numbers, each of which is in the range of 0 through 255 decimal (or 0x00 through 0xFF hex). The standard predefined X keysyms use only the third and fourth numbers. The first two numbers are assumed to be zero.

XSecurePro accepts keysyms in the following three formats:


1. In the dotted notation, where up to four numeric components are separated by periods '.'. Each numeric component represents one of the four numbers that define a keysym. If a component is omitted, it is assumed to be zero in the left-most position. If two components are omitted, the two left-most components are assumed to be zero, etc. For example, if you enter the numbers

32.255

two of the four possible components are omitted. The keysym will be interpreted as

0.0.32.255

In the dotted notation, the two lines below both represent the same keysym:

255.0xFE

0.0.255.0xFE

2. A single numeric value containing up to four bytes specifications. Unspecified numbers are assumed to be zeroes in the left-most position. For example:

0xFF20

represents the values 0xFF and 0x20. The keysym is interpreted as follows:

0.0.0xFF.0x20

Predefined symbols can be used instead of the keysym formats described above. The following three symbols are predefined:

ModeSwitch0xFF7E

VoidSymbol0xFFFFFF

NoSymbol0

You can get a full list of X-keys via the xmodmap utility of UNIX by using the -pm and/or -pk options.

The values of keysyms for keys may be obtained via the /usr/openwin/demo/xev X-Window's UNIX utility.

3. A keysym value can be of a composer type, i.e. the COMPxx entry exists in the [COMPOSERS_XKK] section with the keysym value 'xx'. See the [COMPOSER_XKK] section below for details of how composers work.

Examples:

[KEYS]KEY30 = 97, 65; LATIN LETTER a / A; KEY30 = 0x61, 0x41; (XK_a, XK_A); just the same as the previous lineKEY80E= 255.84, 255.84; cursor DOWN / cursor DOWN

; KEY80E=0xff54, 0xff54; (XK_Down, XK_Down); just the same

Examples of re-mapping

Suppose that you selected to use the us.kmf file (with XSettings) and you want to change the keyboard mapping for Up(8) and Down(2) keys of the additional keyboard and for the F1 key. You can find the following lines in the us.kmf file for them:

KEY59 = 0xffbe, 0xffbe ; (XK_F1,XK_F1)..........KEY72E = 0xff52, 0xff52 ; (XK_Up,XK_Up)KEY80E = 0xff54, 0xff54 ; (XK_Down,XK_Down)

By using the xev or xmodmap -pk commands on the SUN host, you can get keysyms for all keys. For example, you choose:

Help=0xff6a;Paste=0xffcf;Copy=0xffcd;

If you modify the lines of the us.kmf file as follows:

KEY59 = 0xff6a, 0xff6a ; (Help,Help)..........KEY72E = 0xffcf, 0xffcf ; (Paste,Paste)KEY80E = 0xffcd, 0xffcd ; (Copy,Copy)

you will emulate the "Help" (F1), "Copy" ("Down") and "Paste" ("Up") functions of the SUN keyboard.

Another example of keyboard mapping

Suppose that you use the us.kmf file and you want some keys of your keyboard to map to the SUN one. You can find the following lines in the us.kmf file:

KEY59 = 0xffbe, 0xffbe ; (XK_F1,XK_F1)KEY60 = 0xffbf, 0xffbf ; (XK_F2,XK_F2)KEY61 = 0xffc0, 0xffc0 ; (XK_F3,XK_F3)KEY62 = 0xffc1, 0xffc1 ; (XK_F4,XK_F4)KEY63 = 0xffc2, 0xffc2 ; (XK_F5,XK_F5)KEY64 = 0xffc3, 0xffc3 ; (XK_F6,XK_F6)KEY65 = 0xffc4, 0xffc4 ; (XK_F7,XK_F7)KEY66 = 0xffc5, 0xffc5 ; (XK_F8,XK_F8)KEY67 = 0xffc6, 0xffc6 ; (XK_F9,XK_F9)KEY68 = 0xffc7, 0xffc7 ; (XK_F10,XK_F10)

If you change them to:

KEY59 = 0xffc8, 0xffc8, 0xffbe ; (XK_F11,XK_F11,XK_F1)KEY60 = 0xffc9, 0xffc9, 0xffbf ; (XK_F12,XK_F12,XK_F2)KEY61 = 0xffca, 0xffca, 0xffc0 ; (XK_F13,XK_F13,XK_F3)KEY62 = 0xffcb, 0xffcb, 0xffc1 ; (XK_F14,XK_F14,XK_F4)KEY63 = 0xffcc, 0xffcc, 0xffc2 ; (XK_F15,XK_F15,XK_F5)

KEY64 = 0xffcd, 0xffcd, 0xffc3 ; (XK_F16,XK_F16,XK_F6)KEY65 = 0xffce, 0xffce, 0xffc4 ; (XK_F17,XK_F17,XK_F7)KEY66 = 0xffcf, 0xffcf, 0xffc5 ; (XK_F18,XK_F18,XK_F8)KEY67 = 0xffd0, 0xffd0, 0xffc6 ; (XK_F19,XK_F19,XK_F9)KEY68 = 0xffd1, 0xffd1, 0xffc7 ; (XK_F20,XK_F20,XK_F10)

then the following keys of your keyboard will map to keys of the SUN keyboard:

F1 => F11/StopF2 => F12/AgainF3 => F13/PropsF4 => F14/UndoF5 => F15/FontF6 => F16/CopyF7 => F17/OpenF8 => F18/PasteF9 => F19/FindF10 => F20/Cut

To get codes of F1 - F10 keys, you should press them together with the Alt-Gr key.

The COMPOSERS_XKK Section

In many European languages (especially in France, Belgium and Holland), users need to enter some special characters by combining a Diacritic (or composer) character and a normal letter. For example, the user enters first the '^' sign and then the 'a' character, then this should result in the 'b' keysym.

The [KEYS] section does not determine composer characters. The Composers are only defined in the [COMPOSERS_XKK] section.

In the [COMPOSERS_XKK] section, each composer statement associates a set of key_ number map pairings with a keysym value.

Synopsis of the composer statement is:

COMPxx = key_number > key_number[S] [, key_number > key_number[S] ... ]

In the composer entry, COMP is the entry name and 'xx' is a decimal keysym value for a composer key (in the range of character codes). The '>' sign defines single code mapping (from the left to the right), while a comma separates possible map pairings. The 'S' character, if exists, allows both cases for a key_number mapping pair, otherwise lower case only.

If for a keysym value 'xx' of a key (say, KEYcc), a composer entry COMPxx exists in the [COMPOSERS_XKK] section (i.e. XServer can find it there), then the 'cc' value will not be sent to the X Client (otherwise, it will).

In the composer case, XServer will save the keysym value 'xx' until the user presses the next key. If the next key (say, KEYyy) is in the COMPxx entry (like 'yy > zz' in a pair), then XServer will send the value 'zz' from the pair to the X Client. If 'yy' is not found in the COMPxx entry, then XServer will send the composer's key_number 'cc' and the second key_number 'yy'.

Note that the values 'yy' and 'zz' are in the range of character codes.

Note that if Composer is pressed twice, then XServer will send the single value 'cc' to the X Client.

Example:

[KEYS]KEY18 = 0x65, 0x45; (XK_e, XK_E)KEY22 = 0x75, 0x55; (XK_u, XK_U)KEY23 = 0x69, 0x49; (XK_i, XK_I)KEY24 = 0x6f, 0x4f; (XK_o, XK_O)KEY30 = 0x61, 0x41; (XK_a, XK_A)KEY41 = 94, 176; Circumflex Accent (^) / DEGREE SIGN, RING ABOVE; KEY41 = 0x5e, 0xb0; (XK_asciicircum, XK_degree)KEY162 = 0xe2, 0xc2; (XK_acircumflex, XK_Acircumflex)KEY170 = 0xea, 0xca; (XK_ecircumflex, XK_Ecircumflex)KEY174 = 0xee, 0xce; (XK_icircumflex, XK_Icircumflex)KEY180 = 0xf4, 0xd4; (XK_ocircumflex, XK_Ocircumflex)KEY187 = 0xfb, 0xdb; (XK_ucircumflex, XK_Ucircumflex)

[COMPOSERS_XKK]; Definition of Circumflex Accent as a composerCOMP94=30>162S,18>170S,23>174S,24>180S,22>187S

In this example, if the user presses (normally) the key 41 which is the circumflex accent (on German keyboard), XServer will check if the keysym value 94 is found in the [COMPOSERS_XKK] section (the COMP94 entry), and if yes, then XServer will wait until the user enters the next character. If the next character is in the COMP94 entry (in our case 30), then XServer will send 162 to the X Client (both cases are allowed). If the second key_number is not found in the COMP94 entry, then XServer will send the composer's key_number (in our case 41) and the second key_number.

Two examples of the Scroll_Lock key implementation

The "Scroll_Lock" key is used to minimize the XServer window running in the FullScreen mode (if the Local ScrollLock key check box on the XSettings window is on). But some of keyboards do not have certain keys (e.g., Scroll_Lock). By the example of two files, us_ps.kmf and us_ps2.kmf, two possible solutions are considered below to implement the "Scroll_Lock" key code generation.

Note that both the files were produced from our standard us.kmf file. You can compare them to view the changes made. Of course, these are only EXAMPLES. The similar changes (of KEY60) may be made with ANY existing keyboard key.

● The us_ps.kmf file defines the "Escape" key as the COMPOSER key. So, the "Esc"+"i" key sequence will generate the Scroll_Lock key code. In this case, to generate the "simple Escape" key code, you must press the "Esc" key twice.

● The us_ps2.kmf file gives another solution - the "Shift"+"F2" key sequence will generate the Scroll_Lock key code.

Available Keyboard Mapping Files

Keyboard Filename

Keyboard

belgian.kmf Belgian Keyboard (for 102 Keyboard)

croatian.kmf Croatian Keyboard (for 102 Keyboard)

danish.kmf Danish Keyboard (for 102 Keyboard)

decemfr.kmf DEC style Keyboard Mapping for a French Keyboard

decemfrc.kmf DEC style Keyboard Mapping for a French Canadian Keyboard

decemgr.kmf DEC style Keyboard Mapping for a German Keyboard

decemuk.kmf DEC style Keyboard Mapping for a U.K. 102 English Keyboard

decemus.kmf DEC style Keyboard Mapping for a U.S. Keyboard

dutch.kmf Dutch Keyboard (for 102 Keyboard)

dvorak.kmf Dvorak Keyboard (for 102 Keyboard)

finnish.kmf Finnish Keyboard (for 102 Keyboard)

frencan.kmf French Canadian Keyboard

french.kmf French Keyboard

german.kmf German Keyboard

hungarn.kmf Hungarian Keyboard

italian.kmf Italian Keyboard

jpn106.kmf Japanese 106 Keyboard

latinam.kmf Latin American Keyboard

msus.kmf Microsoft U.S. English Keyboard

norwegia.kmf Norwegian Keyboard

polish.kmf Polish Keyboard (for 102 Keyboard)

portugue.kmf Portuguese Keyboard

portbraz.kmf Portuguese (Brazilian) Keyboard

rus.kmf Russian Keyboard (for 102 Keyboard)

rusalt.kmf Russian Alternative Keyboard (for 102 Keyboard)

slovenia.kmf Slovenian Keyboard (for 102 Keyboard)

spanish.kmf Spanish Keyboard

swedish.kmf Swedish Keyboard

swissfre.kmf Swiss French Keyboard

swissger.kmf Swiss German Keyboard

uk101.kmf U.K. 101 English Keyboard

uk102.kmf U.K. 102 English Keyboard

uk102m.kmf U.K. 102 English Keyboard (for SWISSGER 102 Keyboard)

us.kmf U.S. English Keyboard

userkbd.kmf User-defined keyboard mapping

















Appendix B Description of Terminal Capabilities

Description of Terminal Capabilities

terminfo.ini is the ASCII file that describes the emulation capabilities of terminals. The description is very similar to the TERMINFO source code of UNIX system.

The file consists of terminal sections. Each section begins with a header string - a logical terminal name enclosed in brackets. The name is used to select the terminal type in the Telnet_SSH Options/Settings/Type tab.

The section header is followed by a set of entry records that describes the emulation capabilities of the terminal. Each record consists of a capability keyword, a '=' separator, and one or more capability values separated by a ',' delimiter. White spaces are ignored after the ',' separator as well as after the last value.

Any line may contain a comment. A comment begins with a ';' character on a line and lasts to the end of the current line.

Normally there may be several groups of records in each terminal section:

● A group of terminal capability definitions (e.g., Lines, Columns, Colors, UseCRT, MG0, MG1, RGB, UseCSI, Use2W, Use2HW, Tab8, TabSet).

● A group of X-keys definitions (for non-standard keys of keyboards, e.g., auxiliary keypads or function keys). An X-keysym name followed by a '=' separator begins the record. X-keys definitions may have a single value for the PC-layout mode, or a single value for the VT-layout mode, or both. A '/' sign must precede the VT-layout mode value. In case of both modes, the first value is for the PC-layout mode. A value is a code sequence of one or more key codes (separated by a ',' delimiter) to be transmitted when you use the X-key defined. A code is a decimal number (to represent valid escape or control sequences for the terminal).

Examples for VT240:

XK_Home=155,72 / 155,50,126 ; CSI H / CSI 2 ~

XK_KP_Home=155,72/143,119 ; CSI H / SS3 w

XK_KP_Space=/143,117 ; / SS3 u

● A group of user defined keys (UDK) definitions. You can reprogram them in the Telnet_SSH Options/Settings/User Defined tab. A UDK's name followed by a '=' separator begins the record. A value may be a sequence of one or more characters and/or hex codes (without any separator) to be transmitted when you use the UDK defined.


Examples:

Alt-F10=PRINT ; five characters

Shift-F1=0x1bOp ; one hex code 0x1b with two characters O and p

Terminal Parameter Settings

You can set up terminal capabilities by records with the following keywords and values:

Lines=number

The record specifies a number of lines on a screen of a terminal.

(Example: Lines=24)

Columns=number

The record specifies a number of characters in a line.

(Example: Columns=80)

Colors=number

The record specifies the maximum number of colors on the screen.

(Example: Colors=16)

RGB=R.G.B, ...

The record specifies the palette description for colors to be used for color terminals instead of default colors of MS Windows. Each color number (beginning at 0 to Colors-1) is represented by R, G and B - the relative intensities for red, green, and blue primaries (each in the range of 0...255 decimal) to be used for a certain color. The RGB values indicate normal locations in color space. The primaries in a triple are '.' separated while triples are separated by a ',' delimiter.

UseCSI=1

The terminal can (UseCSI=1) or cannot (UseCSI=0) use 8-bit control sequences.

UseCRT=1

The record defines to use the terminal or application mode for arrows keys instead of ANSI mode (as default).

Use2W=1

The terminal can (Use2W=1) or cannot (Use2W=0) use characters with double width. (See the

control sequence Esc#6 for DEC terminals.)

Use2HW=1

The terminal can (Use2HW=1) or cannot (Use2HW=0) use characters with double height and width. (See control sequences Esc#3 and Esc#4 for DEC terminals.)

Tab8=1

The terminal can use the 8-space default tab stops (in case the TabSet record below does not exist).

TabSet=n1,n2,...

The record defines the horizontal tabulation stop set that will be used as the default tabulation set for the terminal. Decimal numbers separated by a ',' delimiter (n1,n2,...) are column numbers for horizontal tab stops. No values means the tabulation set is empty.

MG0i=inp.out,...MG1i=inp.out,...

The records define re-mapping tables for the main character set (MG0) and for the alternate character set (MG1). Each table consists of code pairs separated by a ',' delimiter. A code pair has an input code (to be remapped), a '.' sign, and an output code from the character set used to display characters. The codes must be a hex number. Tables may continue onto multiple lines. The 'i' suffix in the keywords (MG0i or MG1i) shows the value for 'line number - 1'.

● Example for AT386 (9 pairs for MG0 on 2 lines):

MG00=0x90.0xC9,0x91.0xBB,0x92.0xBC,0x93.0xC8,0x94.0xCD;

MG01=0x95.0xBA,0x97.0xB9,0x98.0xCA,0x99.0xCC;

● Example for DEC terminals and XTERM (15 pairs for MG1 on 3 lines):

MG10=0x6A.0xD9,0x6B.0xBF,0x6C.0xDA,0x6D.0xC0,0x6E.0xC5;

MG11=0x6F.0xC4,0x70.0xC4,0x71.0xC4,0x72.0xC4,0x73.0xC4;

MG12=0x74.0xC3,0x75.0xB4,0x76.0xC1,0x77.0xC2,0x78.0xB3;

















Appendix C Troubleshooting

Here are the answers to some frequently asked and particular questions.

FTP

Is there any way that the FTP can be configured to execute a script to automatically copy an entire directory from the host back to the PC?

It is impossible in the Point-and-Click mode (graphical interface). In the Command Line mode (text interface), you can:

● Create all necessary subdirectories (tree) at the local side;● Run the mget DIR command where DIR is the name of the directory.

In this case, all files from DIR and its subdirectories on the remote host will be copied to the current directory and its corresponding subdirectories on the local host.

But the best way to copy a directory with its subdirectories from a remote host to your PC is turning on the Include Subdirectories check box in the Copying Directory dialog box.

Can your FTP client make use of ELPF?

Yes it can. XSecurePro's FTP client automatically recognizes 'anonftpd', a secure FTP server supported EPLF.

The File Transfer Protocol (FTP) supports two commands that list files: NLST and LIST. The NLST response is easy to parse but provides very little information. The LIST response provides more information, but in a format that varies from system to system. The most common LIST formats are undocumented and impossible to parse reliably.

Easily Parsed LIST Format (EPLF) is a format for the LIST response that is usable by humans yet easy for programs to handle. This format is supported by 'anonftpd', a secure FTP server.

One visible advantage of EPLF is that a browser can easily display dates in the viewer's time zone and native language.

An EPLF server must respond to "LIST filename" with information about that file and no others, even if that file is a directory. A client that wants an EPLF list of the contents of a directory must first CWD to that directory. A client that merely wants a list of file names in a different directory may use NLST.


There are some problems with 'special' Unix file names.

FTP can choose the remote host's OS type (DOS, Unix, etc.). This gets FTP to 'understand' file names of the remote host's directory. To choose the OS type on the remote host, you may use the Server Types Option.

Problem: I need to be able to run an ftp command from a command-line that initiates a "PASSIVE" ftp connection. Is this possible with your product?

Yes, XSecurePro's FTP supports the PASSIVE ftp connection mode. You can check the Passive Transfers check box on the Settings tab of the main FTP window before clicking the Connect button. (See section Transfer Options in chapter FTP.)

You can add the following line to the [FTP] section of the xwp.ini file

Passive=1

to reflect the Passive Transfers option turned on or

Passive=0

to reflect the Passive Transfers option turned off.

You can create two ini-files for FTP: one with Passive=0 and another with Passive=1.

You can launch FTP with the command line parameter:

PATH\ftp.exe -xini <IniFilePath>


















NFS-Server

It seemed like my FTP server conflicted with your NFS-Server. I am using WarFTP server. Is there a known conflict between these two products?

As we know, WarFTP usually runs the 'portmapper' service daemon. You may check this by using the 'netstat –a' command.

If you see the TCP and/or UDP 'LISTEN' socket with '111' port number, then portmapper is active.

If you see also the 'LISTEN' socket(s) with '2049' port number, then you have NFS-Server active (already!).

The third important thing is the presence of the mountd 'LISTEN' socket(s). This service does not have a constant port number (it may be 1058, but not always).

Please also run the 'rpcinfo -p YourPC' command (where YourPC is the hostname or IP address of your PC with WarFTP) on any machine with UNIX-like system (Solaris, LINUX, AIX, OS/2). This command will show you all services that are registered in your WarFTP's portmapper.

If you see the 'mountd' and do not see 'nfs' registered in the portmapper, then you can simultaneously use our NFS-Server with WarFTP. Simply run it as 'nfs_serv.exe -ExternalPortmapper'.

Before disabling WarFTP, please try to run our NFS-Server with the 'nfs_serv.exe -ExternalPortmapper' command. If you obtain problems, then you need to disable somehow the WarFTP's portmapper to use our NFS-Server.

In any case, you should worry if you see the TCP and/or UDP 'LISTEN' socket with '111' port number before you run our NFS-Server.

I installed NFS-Server and set "NFS User Access" to 'any-host, any-user, any-group can read/write'. After mounting the PC-local-disk (C:\temp) on the Linux-file-system (/usr1/temp), I (not root-user) can read the PC-files. But I cannot write (and create) any file on the NFS-mounted disk. Only the root-user can write files. We use "RedHat 6.0" Linux.

There are two ways to specify "User ID" and "Group ID":

1) One recommended for "RedHat 6.0" Linux:

● Mount a PC-local-disk (as root-user)● Change directory to the mount point


● Run command 'chown -R <User ID>:<Group ID> <mount point>' (for example, 'chown -R root:wheel /usr1/temp')

2) One recommended for Solaris.

To set up the UID and GID that the (Solaris) nfs-client will see, you can edit the export.us file (in the XSecurePro home directory). For example, the following lines:

d:\mnt\ 2603 1003 W 0=>192.168.136.* 65535 65535 0

indicate that any host from the sub-network 192.168.136.* will be able to mount to 'd:\mnt', and UID and GID will be 2603 and 1003 after mounting (only digits are allowed here, not names. You can determine this by using the command 'id' on the UNIX box). By default, UID=0 and GID=0 (i.e. root).

You should use UID and GID only known to a UNIX host.

How can I control the file mode? Can I set or reset the 'system', 'archive', or 'hidden' attribute of MS Windows file (and directory) by using UNIX commands?

Unfortunately, the FAT file system does not support permissions similar to UNIX permissions (i.e. 'Read/Write/Execute' for 'user/group/world'). While writing files from UNIX to MS Windows, NFS-Server applies the following rules:

UNIX attributes DOS attributes

-r--r--r-- FILE_ATTRIBUTE_NORMAL

-rw-rw-rw- FILE_ATTRIBUTE_SYSTEM

at least one execution allowed FILE_ATTRIBUTE_HIDDEN

at least one write not allowed FILE_ATTRIBUTE_READONLY

for all files FILE_ATTRIBUTE_ARCHIVE

You can set/reset attributes by using UNIX commands. And so you can set up attributes of MS Windows file (for example, the command 'chmod +x <file name>' will produce the 'hidden' <file> on the MS Windows box).

How to run your NFS Server as a MS Windows XP service?

You can find full description of how to install, uninstall, make settings, specify properties, run and control NFS-Server as a MS Windows XP service in subsection The NFS-Server service Tab of section The Run Box in chapter Configuring XSecurePro.

Also, there is information on how to resolve access to NFS-Server for MS Windows Firewall.

I copy a file (1 GB) from NFS server (read operation) to the client PC by 2 ways: 1) from the mapped disk 'M'

2) from My Network Places/Entire Network/XwpNTrdr/Remote NFS Servers/xxx.xxx.xxx.xxx./Directory without disk mapping. I could not find out why there is so big difference in performance (more than 30%). I tried also copy operation from the client to the server (write operation) and the difference is smaller but still important. Thank you very much for your reply if there is any information that explains the problem.

The difference in performance between mapped disk and XwpNTrdr network place is in that MS Windows uses different components for mapped drive requests (MPR) and for UNC requests (MUP). The NFS-Client driver processes both of the request types equally.

Note that trace flags (enabled with the NFStrace utility and used by the NFS-Client driver) have an influence on performance of read/write operations. So you should switch off all trace flags to eliminate the trace influence. (See section The NFStrace Utility in Appendix E.)

Also, you can choose Async for Asynchronous Write mode or Sync for Synchronous Write mode that NFS-Client will use (for NFS-3 protocol version). This choice has critical influence on performance of write operations. (You can choose the mode on the The Advanced Tab described in section NFS-Client Settings under MS Windows NT4/2000/XP in chapter Network File System Client (NFS-Client).)

















XServer & XSettings & Font Service

I am able to get xterm on my Unix box, but I am unable to get xterm on my PC when I telnet-ssh to my Linux box running Kubuntu. When I try to run xterm from the telnet-ssh console on my PC I get the "Error of failed request" message.

The reason of this error message is absence of the font requested by xterm on your Kubuntu machine: "-misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso10646-1". One simple solution is to connect your XServer to any font server that supports these fonts (see section Font Server in chapter Font Control). Another solution is to download the Unicode ISO10646 fontset from Internet sites and include it in Font Path for your XServer to use it (see section Font Directory in chapter Font Control).

If I start one Xsession as normal privileged user and then afterwards another Xsession logged in as administrator they will both get DisplayNumber 0 which is pretty bad.

Yes, this is true. This may take place under Win2003 (and under WinXP with especial settings).

The Auto-DisplayNumber mode requires to create global Windows named memory objects to store necessary information. The default Vista security state denies to create such a memory object. Also, non-privileged users are not allowed to create shareable Windows objects.

You have two ways to avoid this: 1) Start XServer firstly from the administrative user (as you did) 2) Allow INTERACTIVE users to Create global objects. To do this, start the Administrative tools - Local Security Settings - User Rights Assignment dialog, choose Property of the Create global objects policy and add the INTERACTIVE group to the group list (it may already contain the ADMINISTRATORS and SERVICE groups).

Is it possible to convert fonts used in Motif to be used with XSecurePro (the fonts with the .pcf suffix)?

Yes, it is. You should create a directory for .pcf files, create the fonts.dir and fonts.ali files in it, and add the corresponding item to Font Path (the Priority ordered path box) by using XSettings. XServer makes use of .pcf fonts the same way as .snf fonts.

You can enable Trace Fonts Requests in XSettings to find out fonts that are absent (from the xserver.out file).

There are several ways to add fonts to XSecurePro (see Chapter Font Control):


1) Connect to a remote font server which provides fonts you need.

You can launch XSettings, press the FontPath button, enter your font server specification in the Font directory field, select a font server specification in the Priority ordered path box, and Insert the Font directory into the path list before/after the selected item.

To detect required font directories and their order on a remote host, please logon to the remote host by using the console (under the same account), and then run the command line "xset -q" from the xterm window or from the console. Please store the "Font Path:" from the output of this command.

You should add the missing paths to these fonts in the same order into the "catalogue=" line of the font server's config-file. Then, if the font server is running, restart it or re-read its config-file.

E.g., the config-file for Solaris is /usr/openwin/lib/X11/fontserver.cfg, for Linux /usr/X11R6/lib/X11/fs/config.

Note: If you are using a font server located on a Linux host, you cannot check its config-file because all fonts are included in the config-file.

If you are using X11 Forwarding for X-applications, you should use the forwarding for port 7100 of a font server too.

2) Copy fonts you need (.snf or .pcf files only) into a directory on your PC and include its name into the Font Path list.

Example for Asian fonts:

If you have Chinese, Japanese, Korean, or other 16-bit fonts supported by a UNIX host, you should:

1. Uncompress required font files (.pcf or .snf files only) to a new directory on your host (say, Asianfonts)

2. Run the "mkfontdir" utility for this directory to create the fonts.dir file.

To map new names to existing fonts, you should create the fonts.alias file (or edit the existing one).

3. Create a new directory under the FONTS folder on your PC (say, .../FONTS/Asianfnt) to contain new fonts

4. Copy all binary font files (.pcf or .snf files only) from the Asianfonts directory of your host to the .../FONTS/Asianfnt directory on your PC (e.g., by ftp in the binary mode)

5. Copy the fonts.dir text file from the Asianfonts directory of your host to the .../FONTS/Asianfnt directory on your PC (e.g., by ftp in the ASCII mode)

6. Copy the fonts.alias text file from the Asianfonts directory of your host to the .../FONTS/Asianfnt directory on your PC (e.g., by ftp in the ASCII mode) as the fonts.ali file

7. Add the path to the .../FONTS/Asianfnt directory on your PC to Font Path.

You can launch XSettings, press the Font Path button, enter the directory name in the Font directory field or select it by using Browse, select a font source specification in the Priority ordered path box, and Insert the Font directory into the path list before/after the selected item.

8. Check the .../FONTS/Asianfnt directory by using the XFontset Service utility.

Then, you can view the Entire Fonts List of the .../FONTS/Asianfnt directory.

3) Use XSettings' PSEUDO fonts feature to emulate X-fonts with MS Windows fonts which actually exist on your PC.

4) Create aliases for fonts you need in a directory to substitute them with MS Windows fonts which actually exist on your PC and include the directory name into the Font Path list.

For example, the 'sun-fontspecific' fonts may be substituted with the 'adobe-fontspecific' fonts.

5) Edit the fonts.ali file in any existing font directory and create aliases for absent fonts to substitute them with existing fonts.

Of course, the first and second ways are preferable.

You can try to run the following command line

fsinfo -server fontserverhost:portnumber

If you get the message:

'/usr/openwin/bin/fsinfo: unable to open server "fontserverhost:portnumber'

then check:

1. that the following font server line is present in the /etc/services file:

fs 7100/tcp # Font server

2. that this port (7100 in our case) is being listened on;

and run the following command on your host:

netstat -an | grep 7100

If you do not get any answer, then check configuration of the X font server on your host.

When trying to start some of our local UNIX applications, the following error was displayed - Cannot accept '/usr/local/Apstools/12.1/lib/fonts' FontPath Element.

You need to avoid this problem. While executing, your application adds a new item '/usr/local/Apstools/12.1/lib/fonts' to XServer's Font Path. This action is not legal for XSecurePro's XServer because it works only with local Font Path and/or with a remote font server path.

When using the X Display manager the font that is on the screen is the same as the one I am using now. But when I log in from the host or HP Xterminal the font looks like a 'sans serif'

or 'arial' type of font. How can I get the required font? I noted down the fonts that are loaded by an Hp-Xterminal when it boots up from the host. They are /usr/lib/X11/700X/fonts/hp-roman8/75dpi/system19.snf and system23.snf, system16.snf, system17.snf, system13.snf, ser11x19.snf. I copied these fonts to my local PC and added these fonts to the font path, but when I started the X Display manager, I received garbage on the screen, where the login and password words were before.

The HP-snf font format actually differs from the X11-snf font format. XSecurePro's X-session processes only X11-snf fonts and cannot process HP-snf fonts. X-session cannot distinguish between these formats because they have the same file name extension.

You have to convert the HP-snf to X11-snf.

Cut and Paste did not work between windows (e.g., between W'95 Notepad and SUN/UNIX Textedit). I have still to try dragging and dropping a file between windows (e.g., UNIX Filemanager to W'95 File system).

In your case, you should choose the CLIPBOARD X Selection to provide the transfer needed.

To use the cut&paste functions, you should know the global cut buffers (X Selections) that your X-application uses for these operations (from X-application manuals).

Different X-applications can use different X Selections for cut&paste. For example, normally,

● "xterm" uses the PRIMARY X Selection● "cmdtool" uses the CLIPBOARD X Selection● "dtterm" uses both (PRIMARY for mouse Button1/Button2 actions, CLIPBOARD for Edit

menu's Copy/Paste actions).

Before cut&paste, you should correctly define the global cut buffer (X Selection) that XServer and your X-application will use.

For example, to copy text between xterm and MS WordPad, you should specify the PRIMARY X Selection for xterm and XServer before copying.

For the xterm window, you can define the buffer by choosing: Select Options/XSelection... PRIMARY/OK.

Make sure that the Auto Clipboard Copy&Paste check box in the XSettings dialog box is enabled. (See section A Note on Copy and Paste in chapter Using XServer.)

If you want to copy text from xterm to MS WordPad, you can do the following:

In the xterm window:

1. Move the mouse pointer to the beginning of the text, hold down the mouse Button1 (usually left) while moving the pointer to the end of the text, and then release the button. The selected text is highlighted and saved in the PRIMARY global cut buffer.

In the WordPad window:

2. Move the mouse pointer to the place where you want to insert the text from the buffer and click the mouse Button1 (usually left).

3. Click the Edit menu, and then choose Paste (or Ctrl-V) to paste the text from the CLIPBOARD of MS Windows. The text selected in the xterm window will appear in the WordPad window.

If you want to copy text from MS WordPad to xterm, you can do the following:

In the WordPad window:

1. Move the mouse pointer to the beginning of the text, hold down the mouse Button1 (usually left) while moving the pointer to the end of the text, and then release the button. The selected text is highlighted.

2. Click the Edit menu, and then choose Copy (or Ctrl-C). The selected text is saved in the CLIPBOARD of MS Windows.

In the xterm window:

3. Move the mouse pointer to the place where you want to insert the text from the buffer and click the mouse Button2 to paste the text from the PRIMARY X Selection. The text selected in the WordPad window will appear in the xterm window.

The mouse Button2 is normally the middle button or simultaneously pressed left and right buttons if you have enabled the Middle Button Emulation check box in the XSettings dialog box.

I would like to know what True color support means... Will True color work with more than 256 colors?

True color support (in Windows) means that a video-driver supports the color palette with 64K colors. XServer supports 256-color palette and CAN operate with any High/True-color video-driver of Windows.

Is there a difference between using the X-manager and the windows manager in cutting and pasting?

XSecurePro cannot write the X Selection/bitmap to a file.

Is it possible to print X application's windows to my local computer (MS Windows 98 printer) with XSecurePro?

Yes, it is. On your local printer, you can print from MS Windows applications and from remote X applications as well (if the printer is accessible for them).

If you want to print from remote X applications to a printer connected to your PC (over the network),

● Start XSecurePro's LPD on your PC

● Configure LPD to use your printer by users from the remote host

● Configure your UNIX host (so the host could use LPD and your printer on your PC across the

network)

● Start X applications and print their windows from your host.

If you want to print an X application's window that you see on your display to a printer connected to your PC,

● Make sure that the X application's window is active on your display

● Press the Alt+Print Screen shortcut key to copy the window to MS Clipboard

● Paste MS Clipboard to a MS Windows application you want to use (e.g., MS Paint)

● Print the image from this application to your printer.

By using X Selections, you can transfer required text from your X application to a MS Windows application (e.g., from xterm to WordPad) and then print the whole document to your printer.

I want to run Netscape from my PC on the remote UNIX machine. I use 'your' telnet to log into the remote UNIX computer. There I can find my PC's IP address. I try to start 'xterm' on the UNIX machine. I think it does start in the 'background'. When I try to run, say, Netscape, 'it' complains that it cannot find 'display'. What the problem could be?

Make sure that your remote host is accessible from your PC. First, try to open a telnet connection to a remote host. If you can do that, then check whether you can start X-applications from the telnet session on your remote host:

● Start X-session on your PC

● Open the telnet connection to the remote host

● Launch any X-application from the telnet session:

e.g.,

/usr/bin/X11/xterm -display IP_address_of_your_PC:0&

or

/usr/bin/X11/xterm -display Name_of_your_PC:0&

(in this case, you should add the name and IP-address of your PC into the /etc/hosts file on your Unix host).

Has the xterm window appeared on the screen of your PC?

If not, check that TCP ports 6000 - 60xx used by XServer on your PC are accessible from the remote host.

If yes, you can try to launch X-applications by using the Startup utility. First:

● Find the configuration file of inetd, /etc/inetd.conf, (or xinetd) on the remote host (please find out which Internet service daemon is running on your remote host: inetd or xinetd)

● Check that the following lines in the /etc/inetd.conf file of the Unix host are present and are not commented-out (by default, these lines are commented-out):

"exec ..." for REXEC (512/tcp) (if you want to use rexec in Startup)

"shell ..." for RSH (514/tcp) (if you want to use rsh in Startup)

"login...." for RLOGIN (513/tcp) (if you want to use rlogin in Startup)

If the xinetd daemon is used on your remote host, it is recommended that you read corresponding manual pages for xinetd.

If these lines are present and are not commented-out, you can try to launch X-applications (or run any Unix command) by using Startup.

Launch Startup, select one of the start methods (REXEC/RSH/RLOGIN) supported by the Unix host (see the /etc/inetd.conf file of the Unix host), enter the Host Name or IP-address of the Unix host, User ID, and Password in corresponding fields of the Startup dialog box, enter any Unix command in the "Command" field (e.g. 'ls -l'), and then click the Execute button.

Is there any output of this command in the "Status Messages" field?

If yes, then enter the command launching xterm (e.g., /usr/X11R6/bin/xterm -display $(LOCALIP):0 ) and click the Execute button.

Has the xterm window appeared on the screen of your PC?

Also, you can try to use the XDMCP mode of XServer. If you want to use XServer in the XDMCP mode, please check that the xdm-daemon is running on the remote host and check XDMCP configuration.

To use XDMCP, you should launch XServer in the Single/Full or Multiple+RemoteWM mode because, if XServer is running in the Multiple mode, some remote window managers (including 'gnome' and KDE) close X-session when they detect any other running window manager (e.g., MS Windows window manager or local 'mwm').

To configure XServer, you should start the XSettings utility, select the Single/Full or Multiple+RemoteWM mode, enable the Use XDMCP check box, click the Settings button, and then specify XDMCP settings.

Before using XDMCP, make sure that XDMCP on the remote host listens to UDP port 177. To do so, run the "netstat -an|grep 177" command on the remote host. You may see from its output:

"udp 0 0 0.0.0.0:177 0.0.0.0:* "

(or for Solaris station: *.177 Idle)

If you do not see this, please check configuration of XDMCP on your remote host.

Also, make sure that UDP port 177 on the remote host is accessible from your PC (i.e. there are no any firewalls, etc. filtering these packages between your PC and the remote host).

If UDP port 177 on the remote host is not accessible from your PC, you cannot use XDMCP mode of XServer.

NOTES:

When XServer is running in the Single/Full or Multiple+RemoteWM mode, the remote window manager that you select will be used (e.g., 'olwm', CDE, 'twm', 'mwm', etc.).

If you want to use a remote window manager, please use the Single/Full or Multiple+RemoteWM mode. In this case, you should use the XDMCP mode or start any remote window manager from the Unix host (e.g., start 'xterm' and then start the required window manager from the xterm window). In this case, the remote window manager only provides the windows managing functions (moving, resizing, etc.).

Also, you can launch the local 'mwm' program (Motif Window Manager) on your PC from the X-session's Run menu (for the Single/Full or Multiple+RemoteWM mode). In this case, 'mwm' will provide the windows managing functions.

If you do not want to use a remote window manager, please use the Multiple mode. When XServer is running in the Multiple window mode, the MS Windows window manager is used and any other window manager is blocked.

Some remote window managers (including 'gnome' and KDE) close the X session if they detect any other running window manager. In this case, you cannot use the Multiple mode and should only use the Single/Full or Multiple+RemoteWM window mode.

Problem: I am new to using XServer from Windows and would like to use an SSH tunnel and display the entire gnome desktop on my Windows box.

If you have any X server running on your PC, you can launch an X application to this X server with any SSH client by using X11 Forwarding.

If a remote host supports SSH1 or SSH2 (i.e. the ssh-daemon is running), you can use the SSH session for logon to the remote host and then start any X application from the SSH session.

You can start remote X applications in the SSH mode of Telnet_SSH (XSecurePro's Telnet_SSH acts as SSH client in the SSH mode). To do so, you should:

● Launch Telnet_SSH

● Enter the host name or IP address of your remote computer

● Select the SSH interface

● Click OK.

SSH automatically takes care of xauth, $DISPLAY, etc. The SSH client enables X Forwarding by default, automatically sets the DISPLAY environment variable on the server machine, and provides forwarding of any X11 connections with this DISPLAY over the secure channel.

Xauthority information is automatically generated and forwarded to the remote machine. The local client automatically examines incoming X11 connections and replaces the authorization data with the real data.

With XSecurePro's Telnet_SSH, you can create an encrypted connection with a remote host and display any X applications on your PC. In this case, you cannot only use the XDMCP connection mode of XServer because SSH provides tunneling TCP packets only (it does not provide tunneling UDP packets).

In this case, your X-session can be as follows:

● Start the sshd-daemon on your remote host (if it is not running)

● Start X-session

● Logon to the remote host through the SSH mode of Telnet_SSH

● Start any X application (e.g. xterm&) from the SSH session by using the DISPLAY environment variable automatically set.

If the user is using X11 (the DISPLAY environment variable is set), the connection to the X11 display is automatically forwarded to the remote side in such a way that any X11 programs started from the shell (or command) will go through the encrypted channel, and the connection to the real X server will be made from the local machine. The user should not manually set DISPLAY from the SSH session. The DISPLAY value set by SSH will point to the server machine, but with a display number greater than zero. This is normal, and happens because SSH creates a "proxy" X server on the server machine for forwarding the connections over the encrypted channel.

Make sure that entry line "127.0.0.1 localhost" is present in the hosts system file of your PC. If you use "Access Control", you should include "localhost" into the "Valid Hosts File" (see section Using XSettings in chapter Configuring XSecurePro).

If you are using RSA key to log in a UNIX host, you should use the ssh-keygen program on the host to create the authentication key for SSH. Then you should copy the created identity file to your PC.

You can use the Startup utility to launch X applications through the encrypted channel created by the SSH client of XSecurePro. Through SSH connection, you can only use the REXEC method of Startup (if a remote host supports REXEC for localhost).

Before using SSH from the Startup utility, you should previously open an SSH connection to a remote computer. For example, to create the encrypted connection with your host,

1. Start Telnet_SSH

2. Select the SSH-1 or SSH-2 interface

3. Fill in the Host field

4. Click OK.

The "SSH Authentication" window will appear.

5. Fill in the User name field (e.g. John)

6. Fill in the Passphrase field (e.g. Smith)

7. Enable the Use plain password to log in check box

8. Click OK.

When your SSH connection is open, the "Telnet_SSH" window will appear.

Then if you want to use the Startup utility (with REXEC) through the created encrypted channel,

1. Start Startup

2. Select REXEC as start method

3. Fill in the Host Name/IP Address field

(e.g. 127.0.0.1, or the "localhost" host name if it exists in the hosts system file of MS Windows).

4. Fill in the User ID field (e.g. John)

5. Fill in the Password field (e.g. Smith)

6. Fill in the Command field

(e.g. /usr/bin/X11/xterm -display localhost:10&).

Note: You must use the same display that the "echo $DISPLAY" command shows in the Telnet_SSH session (but not 127.0.0.1:0).

7. Select the line with a required SSH connection from the list box under the Use SSH Forwarding check box

8. Check the Use SSH Forwarding check box

9. Click the Execute button.

The Startup utility will open REXEC to the remote host through the encrypted connection.

You can use the FTP utility to connect to remote hosts through the encrypted channel created by the SSH client of XSecurePro.

Before using SSH from FTP, you should previously open an SSH connection to a remote computer. For example, to create the encrypted connection with your host,

1. Start Telnet_SSH

2. Select the SSH-1 or SSH-2 interface

3. Fill in the Host field

4. Click OK.

The "SSH Authentication" window will appear.

5. Fill in the User name field (e.g. John)

6. Fill in the Passphrase field (e.g. Smith)

7. Enable the Use plain password to log in check box

8. Click OK.

When your SSH connection is open, the "Telnet_SSH" window will appear.

Then if you want to use FTP through the created encrypted channel,

1. Start FTP

2. Fill in the Host ID field

(e.g. 127.0.0.1, or the "localhost" host name if it exists in the hosts system file of MS Windows).

3. Fill in the User Name field (e.g. John)

4. Fill in the Password field (e.g. Smith)

5. Check the Use SSH Forwarding check box

6. Click the Connect button.

The "SSH Forwarding" window will appear.

7. Select the line with a required SSH connection from the list box

8. Click OK.

FTP will open connection to the remote host through the encrypted connection.














This page is a part of XSecurePro online Help Manual. X-SecurePro is X-Server for windows by Labtam bringing your PC to Unix and X-Windows. Seamless Secure integration from PC to Unix and X-Window System. Bringing Maximum Security while still finding all of the

standard access of X11, TCP/IP, FTP, TFTP, LPR, TELNET, NFS and SSH. Visit Home of X Server for windows for more information.


Appendix E

The NFSprobe Utility

The NFSprobe utility is designed for getting some useful information about computers (i.e. running NFS servers) available across your TCP/IP-based network. It allows you to check availability of exported resources on those systems you might mount to your PC. You can use NFSprobe to recognize your network environment for solving particular NFS tasks or network troubles.

While running, NFSprobe logs all information obtained from NFS servers on its requests to the nfsprobe.ptr file.

When you start NFSprobe, the NFSprobe window appears:

When you click the Exit button on the menu, NFSprobe closes the window and exits. The other commands are described below.

The RPC_Info Command

If you click the RPC_Info button on the menu, NFSprobe brings up the Rpc Information dialog box.

This option allows you to display a list of all RPC services registered with 'rpcbind' on remote hosts (like


the 'rpcinfo' command does, i.e. it makes an RPC call to an RPC server and reports what it finds).

You can change the following available options as required.

UDP

Specifies the UDP transport on which the RPC service is required (i.e. which has to be used for contacting given RPC services).

TCP

Specifies the TCP transport on which the RPC service is required (i.e. which has to be used for contacting given RPC services) on the specified host.

Host IP address

In this field, you specify the IP address of a remote host as the RPC server.

Use Broadcast Request

When enabled, this check box specifies to make a RPC broadcast to RPC servers (in your LAN) and to report all hosts and RPC programs that respond.

Show All Rpc Programs

When enabled, this check box allows you to displays a list of all registered RPC programs (with program numbers and version numbers) on specified host(s). Otherwise, information about 'rpcbind', 'mountd', and 'nfsd' is only displayed.

The Time Command

The Time command has two options: UTC_Time and Local_Time. These let you display Universal and Local time respectively on NFS server sites of your network and your PC as well.

The Diagnose Command

The Diagnose command has two options: Servers and Client. The Client option lets you check that your NFS-Client was installed with all components needed and is now functioning normally.

The Servers option checks access to available NFS servers on your network. You can view output information in the NFSprobe window.

The Network File System Checking Window

If you choose the Server option, NFSprobe brings up the Network File System Checking window with the default values in entry fields of the Options and Authentication sections. You can change available fields to the values as required.

If you click the Close button, NFSprobe closes the window and returns you back to the NFSprobe window.

If you click the Show Servers button in the Network File System Checking window with the Use Broadcast Requests check box enabled, then NFSprobe will send broadcast requests (using current Options and Authentication settings) to locate all available remote NFS servers, collect reply information, and make up the list of computers (NFS servers) found currently available across your network (LAN). You can view the hosts on the Host list box.

With the Use Broadcast Requests check box disabled, you must enter the IP address of a remote host in the Host list box and click the Check Server button to collect reply information from the NFS server specified.

If the Ask to connect via SSH check box is enabled, then you will be prompted to choose one of secure connection channels (using the SSH2 protocol) previously established between your PC and a remote SSH server.

Enter the IP address of an NFS server of your interest or select it from the Host list box, then click the Show Exports button. NFSprobe will display a list of exported resources of that NFS server.

Note that each exported directory may have a list of users which are allowed to access to it. To mount a remote resource according to the remote NFS access lists, you must provide valid values for UserID and GroupID in the Authentication section. If the user exists in several groups, they can be specified in the Group IDs field with the space or comma characters as separators. (The main group is specified in the GroupID field and the other groups are specified in the Group IDs field.)

Note that in an NFS network, once the user is authenticated, that user's access to network file resources is further defined by the permissions granted for certain files and folders. When browsing, you will be able to see all the exported folders, however, viewing the contents of the folders as well as opening and editing files will depend on whether you have the correct permissions.

When you select one of the exported directories seen in the Exported Resources list and click the Mount button, the Drive list box will be filled in with free drive letters of your PC.

If you click the Read Directory button, NFSprobe will output the contents of the exported directory in the NFSprobe window.

To control NFSprobe, you can use the following options in the Options section:

Timeout

This option is used to specify the amount of time (in seconds) that NFSprobe will wait for response on MOUNT and NFS protocols requests it sends to other computers over the network.

Max Retry Number

This option is used to specify a number of times not-replying occurs during the timeout specified before a timeout error due to no response from a server.

The NFStrace Utility

The NFStrace utility is designed for setting a number of trace flags (by toggling related check boxes) and passing them to the DLL and Driver modules of NFS-Client. According to the Trace Flags set, NFS-Client will store related information into the trace files you specified.

Normally, users should not arbitrarily turn on/off Trace Flags. The flags can noticeably slow down the traffic and generate a great amount of data. The NFStrace utility is meant for testing and analyzing NFS environment of your network.

You can run NFStrace under MS Windows NT4/2000/XP.

When you start NFStrace, the NFS Client Trace Flags window appears:

If you click the Close button, NFStrace closes the window with no changes.

Pressing the Apply button passes the Trace Flags set to the DLL and Driver modules of NFS-Client and closes the window.

Refresh restores all Trace Flags in the window to their initial states (when loaded NFS Driver and/or the latest Apply).

With the Save to use in next sessions check box enabled, you can store the current settings (after

Apply) and load them later (while loading NFS Driver).

The DLL Trace File and Driver Trace File fields specify the files to contain tracing data.

















Appendix D The PingNFS Utility

The PingNFS Utility

The PingNFS utility is designed for getting some useful information about computers available across your TCP/IP-based network. It allows you to check available connections to these computers (i.e. to running NFS servers) and to view their exported resources. You can use PingNFS to recognize your network environment for solving particular NFS tasks or network troubles.

When you start PingNFS, the pingNFS_w window with empty entry fields appears. At the top of the window, the MyHostName variable shows your PC's host name and the MyIP variable shows your PC's IP address.

If you enable the Use broadcast checkbox in the Servers section and then click the Get list button, PingNFS will send broadcast requests, collect reply information, and make up the list of computers found currently available across your network (LAN). The list shows you the information about possible connections you might establish with those computers (i.e. IP address, program, version, transport, port). Note that entry fields in the Programs section are grayed out.

If you click the Check button, PingNFS will check each available connection capability displayed and fill in the check column in the list with status results.

If you select an IP address from within the list and then click the Show exports button, PingNFS will display available exported resources of that computer in the bottom part of the window:


You can click the Clear list button to remove data displayed, change settings as required, and then use the Get list button again to repeat searching.

If you disable the Use broadcast checkbox, then the Server IP address or name field and the Use portmapper checkbox in the Programs section become available. You can specify the IP address of a computer you want, set Use portmapper on, and then click the Get list button. PingNFS will send requests and show you the list with the information for that server only. Note that entry fields in the Programs section are grayed out.

If you set Use portmapper off, then you have to specify the entry fields (or select values from the list box) in the Programs section (i.e. Program, Version, Transport, Port). Note that the Get list button changes to Add to list. You can use it to form the list with the data you want.

If you click the Check button, PingNFS will check connection capabilities specified and fill in the check column in the list with status results.

If you select an IP address from within the list and then click the Show exports button, PingNFS will send requests and show you available exported resources of that computer in the bottom part of the window:

The Time field is used to specify the amount of time (in seconds) that PingNFS will wait for reply on requests it sends to other computers over the network.

Cancel closes the window and exits PingNFS.
















< previous | content

Appendix F

Local X and Motif Clients

The XSecurePro package includes the following local X and Motif clients:

● mwm (based on OpenMotif 2.0)● glxinfo (the GLX extension local X Client)● glxgears (the GLX extension local X Client)● xclock● xdpyinfo● xev● xfd● xfontsel● xkill● xlsfonts● xmodmap● xprop● xrdb● xset● xshowcmap● xwininfo


To run one of these programs, click its name on the X-clients Program Folder of the package (when XServer is running) or from the Run menu of XServer. (In these cases, the clients are called with parameters specified by XServer.)

Also, you can launch the clients from Startup (in the lShell mode) or from the Start/Run menu of your MS Windows system. (In this case, you must specify startup parameters for the invoked X client on the command line.)

The local X clients were developed (to be run under MS Windows) with the X Development Kit supplied with the package.

You can take advantage of the local X clients when remote (UNIX) ones are inaccessible or inconvenient to run.

The following is brief descriptions of available local X clients. For more information, refer to corresponding manuals on these applications.


mwm

mwm is a local implementation of the Motif window manager (based on OpenMotif 2.0). The local mwm program may be useful when XServer is in the Single Window mode (this allows not to use a remote window manager).

glxinfo

glxinfo is a sample program for displaying info about a GLX extension and OpenGL renderer. It lists information about the GLX extension, OpenGL capable visuals, and the OpenGL renderer on an X server. The GLX and renderer info includes the version and extension attributes. The visual info lists the GLX visual attributes available for each OpenGL capable visual (e.g. whether the visual is double buffered, the component sizes, Z-buffering depth, etc). By default the visual info is presented in a concise 80 character wide tabular format. The -l option allows you to print interesting OpenGL limits.

glxgears

The glxgears program is a sample GLX version of the "gears" GL demo. It is a GLX demo that draws three rotating gears, and prints out framerate information to stdout. The -info option allows you to print out GL implementation information before running the demo.

xclock

The xclock program displays the time in analog or digital form. The time is continuously updated at a frequency that may be specified by the user.

xdpyinfo

The xdpyinfo program displays information about an X server. It is used to examine the capabilities of a server, the predefined values for various parameters used in communicating between clients and the server, and the different types of screens and visuals that are available.

xev

xev is the X Event Tester. You can run this standard X client locally (on your PC) to obtain the values of keysyms for keys. According to its manual, when xev is running, it creates a window and then asks the X server to send it notices called 'events' whenever anything happens to the window (such as being moved, resized, typed in, clicked in, mouse movements, button clicks, etc.). It is useful for seeing what causes events to occur and to display the information that they contain. For example, you can run xev to obtain the values of keysyms for key presses.

xfd

This program is used to displays all the characters in an X font. According to its manual, the characters are displayed in a grid of boxes, each large enough to hold any single character in the font. Individual character metrics (index, width, bearings, ascent and descent) can be displayed at the top of the window by clicking on the desired character.

xfontsel

The xfontsel application provides a simple way to display the fonts known to your X server, examine

samples of each, and retrieve the X Logical Font Description ("XLFD") full name for a font (i.e., xfontsel is a point & click interface for selecting X11 font names).

According to its manual, if the pattern option is not specified, all fonts with XLFD 14-part names will be selectable. To work with only a subset of the fonts, you can specify -pattern followed by a partially or fully qualified font name (e.g., "-pattern *medium*" will select that subset of fonts which contain the string "medium" somewhere in their font name). Be careful about escaping wildcard characters in your shell.

The sample option specifies the sample text to be used to display the selected font if the font is linearly indexed, overriding the default. The sample16 option specifies the sample text to be used to display the selected font if the font is matrix encoded, overriding the default. The noscaled option disables the ability to select scaled fonts at arbitrary pixel or point sizes. This makes it clear which bitmap sizes are advertised by the server, and can avoid an accidental and sometimes prolonged wait for a font to be scaled.

Clicking any pointer button in one of the XLFD field names will pop up a menu of the currently known possibilities for that field. If previous choices of other fields were made, only values for fonts that matched the previously selected fields will be selectable. To make other values selectable, you must deselect some other field(s) by choosing the '*' entry in that field.

Scalable fonts come back from the server with zero for the pixel size, point size, and average width fields. Selecting a font name with a zero in these positions results in an implementation-dependent size. Any pixel or point size can be selected to scale the font to a particular size. Any average width can be selected to anamorphically scale the font (although you may find this challenging given the size of the average width menu).

Clicking the left pointer button in the select widget will cause the currently selected font name to become the PRIMARY text selection as well as the PRIMARY_FONT selection. This then allows you to paste the string into other applications. The select button remains highlighted to remind you of this fact, and de-highlights when some other application takes the PRIMARY selection away.

xkill

The xkill program is a utility for forcing the X server to close connections to clients. This program is very dangerous, but is useful for aborting programs that have displayed undesired windows on a user's screen. According to its manual, if no resource identifier is given with -id, xkill will display a special cursor as a prompt for the user to select a window to be killed. If a pointer button is pressed over a non-root window, the server will close its connection to the client that created the window.

xlsfonts

This program is used to display server font list for X. According to its manual, xlsfonts lists the fonts that match the given pattern. The wildcard character '*' may be used to match any sequence of characters (including none), and '?' to match any single character. If no pattern is given, '*' is assumed. The '*' and '?' characters must be quoted to prevent them from being expanded by the shell.

The l option lists some attributes of the font on one line in addition to its name. The ll option lists font properties in addition to l output. The lll option lists character metrics in addition to ll output.

xmodmap

The xmodmap utility is for modifying keymaps and pointer button mappings in X. It is used to edit

and display the keyboard modifier map and keymap table that are used by client applications to convert event keycodes into keysyms. It is usually run from the user's session startup script to configure the keyboard according to personal tastes.

Some options that may be used with xmodmap (according to the manual):

● The -display display option specifies the host and display to use.● The -e expression option specifies an expression to be executed. Any number of expressions

may be specified from the command line.● The -pm option indicates that the current modifier map should be printed on the standard

output.● The -pk option indicates that the current keymap table should be printed on the standard

output.● The -pke option indicates that the current keymap table should be printed on the standard

output in the form of expressions that can be fed back to xmodmap.● The -pp option indicates that the current pointer map should be printed on the standard

output.

The filename argument specifies a file containing xmodmap expressions to be executed. This file is usually kept in the user's home directory with a name like .xmodmaprc.

The xmodmap program reads a list of expressions (from a command line or a file) and parses them all before attempting to execute any of them. This makes it possible to refer to keysyms that are being redefined in a natural way without having to worry as much about name conflicts.

The list of keysym names may be found in the header file X11/keysymdef.h (without the XK_ prefix) or the keysym database <XRoot>/lib/X11/XKeysymDB, where <XRoot> refers to the root of the X11 install tree.

Example:Many pointers are designed such that the first button is pressed using the index finger of the right hand. People who are left-handed frequently find that it is more comfortable to reverse the button codes that get generated so that the primary button is pressed using the index finger of the left hand. This could be done on a 3-button pointer as follows:

% xmodmap -e "pointer = 3 2 1"

xprop

The xprop utility is for displaying window and font properties in an X server. According to its manual, one window or font is selected using the command line arguments or possibly in the case of an X's window, by clicking on the desired window. A list of properties is then given, possibly with formatting information. Normally each property name is displayed by printing first the property name then its type (if it has one) in parentheses followed by its value.

xrdb

The xrdb utility is for controlling the X server resource database. According to its manual, xrdb is used to get or set the contents of the RESOURCE_MANAGER property on the root window of screen 0, or the SCREEN_RESOURCES property on the root window of any or all screens, or everything combined. You would normally run this program from your X startup file.

Most X clients use the screen-independent resource property, RESOURCE_MANAGER, and the screen-specific resource property, SCREEN_RESOURCES, to get user preferences about color, fonts, and so

on for applications. The RESOURCE_MANAGER property is used for resources that apply to all screens of the display. The SCREEN_RESOURCES property on each screen specifies additional (or overriding) resources to be used for that screen. When there is only one screen, SCREEN_RESOURCES is normally not used and all resources are just placed in the RESOURCE_MANAGER property.

xset

This program is used to set various user preference options of the display. According to its manual, the options control the bell parameters, key click, autorepeat, the turning on/off the keyboard LEDs, the mouse parameters, pixel color values, the screen saver parameters, the font path, Energy Star mode, power management, and many others.

xshowcmap

The xshowcmap program displays the contents of the currently active colormap in a window (a map of the system colors). The created window shows a square for every color currently defined in the server's active colormap. The number of squares is the number of colormap-cells the server supports.

xwininfo

The xwininfo utility is for displaying information about X's windows. According to its manual, various information is displayed depending on which options are selected. The user has the option of selecting the target window with the mouse or by specifying its window id or name. There are also special options to quickly obtain information on the screen's root window or on parent and/or children windows.

The stats (default) option causes the display of various attributes pertaining to the location and appearance of the selected window. Information displayed includes the location of the window, its width and height, its depth, border width, class, colormap id if any, map state, backing-store hint, and location of the corners.

The bits option causes the display of various attributes pertaining to the selected window's raw bits and how the selected window is to be stored. Displayed information includes the selected window's bit gravity, window gravity, backing-store hint, backing-planes value, backing pixel, and whether or not the window has save-under set.

The metric option causes all individual height, width, and x and y positions to be displayed in millimetres as well as number of pixels, based on what the server thinks the resolution is.

< previous | content













Documents

XSecurePro V8.3 - Help Manual - Labtam Inc · Telnet/SSH2 as SOCKS4 Proxy Details of a Session Telnet_SSH Menu Options The Help Menu The Commands Menu The Edit Menu The View Menu