PN3_10074

 

Patch PN3_10074
Keyword JRFS
Description Patches to ease configuration
Date June 13, 1998
Patch Details This patch provides the following fixes and enhancements to jRFS and the jConnect Library. The main aim of this patch is to ease
configuration of jRFS for large user configurations by allowing use of an asterisk as a wild card character in the configuration files to alleviate explicit specification.

  1. Allow an asterisk wild card character to be used in the jnet_map, jnet_env and jnet_access configuration files.

  2. Enable default user configuration

  3. Provide message encryption capability in standard product.

  4. Fix bug when attempting to open a multiple data section on remote system via remote MD Qpointer.

  5. Fix bug in trace when displaying socket port number on big-endian system.

  6. Issue new copyright notice.



Asterisk in configuration files.

It is now possible to use an asterisk within the jConnect configuration and security files to skip the need to explicitly specify
each entry. Explicit entries can still be used however must be placed BEFORE any wild card entries which may match.

e.g. In jnet_map - Config file to map client entries to external entries.

LOCAL:ORDER_SYSTEM jRFS * *
REMOTE:SunBox jRFS orders

The above entry will now map all Remote File Access users, (jRFS), attempting to access the ORDER_SYSTEM, (via R Pointers),
to the user id of ‘orders’ on the networked system known as ‘SunBox’.

In jnet_env - Config file to configure additional environment variables.

ENV:jRFS orders *
JEDIFILENAME_MD=/app/ORDERS/MD
JEDIFILEPATH=/app/ORDERS/data1;/app/ORDERS/data2

The above entry will configure ALL clients connecting as user ‘orders’ to be configured with an MD of ‘/app/ORDERS/MD’ and a
be able to access files in subdirectories ‘data1’ and ‘data2’ of the directory ‘/app/ORDERS’.

In net_access - Security file to use on NT or on Unix in place of ruserok files.


SunBox jbase * jRFS - Unix Entry

The above entry would allow Remote Files Server, (jRFS), access to ALL clients called ‘jbase’ from system ‘SunBox’


Enable Default User.

A default user can be configured in the jnet_access file to allow all matching entries to map to the default user.

e.g.
DEFAULTUSER=defuser

SunBox jbase DEFAULT jRFS

All ‘jbase’ clients connecting from the ‘SunBox’ for jRFS access will use the DEFAULT user, in this case ‘defuser’ for access. If
the DEFAULTUSER is not specified a user of ‘jrfs’ is assumed.


Encryption

jConnect message encryption has been available however it has not been enabled in the standard product. This patch now enables the use of encryption when required. The receive side will automatically detected when encryption has been invoked. The send side needs to be configured to use it, by setting the following parameters in the jnet_config configuration file.

encode=on To encrypt just the initial connection string from the client to the server, which contains access information.

dataencode=on To encrypt all data packets sent from this host.

Obviously there is an overhead to using encryption thus the requirement for the configuration parameters.

This patch description is for use by jBASE customers and VARs as an aid to supporting their jBASE installations only and may not be redistributed or published in any form without prior written permission of jBASE Software. This page was produced on February 14, 2000.