As per Relevance of the word following, we have this rfc below:
Network Working Group T.
Request for Comments: 1373
October 1992
PORTABLE
Status of this
This memo provides information for the Internet community. It
not specify an Internet standard. Distribution of this memo
unlimited
This document comes in two parts. The first part is for
people who wish to set up their own DUAs (Directory User Interfaces
to access the Directory. It includes some brief notes on
operation of the DUAs and instructions for their creation
installation. The instructions are given in an easy-to-follow, step
by-step format. It is fully expected that the user will be able
perform the necessary operations as he reads through the
for the first time and have a working DUA when he finishes.
second part is for ISODE-maintainers wishing to provide portable
to users. This part gives instructions in a similar but longer
step-by-step format. It is fully expected that the maintainer will
able to perform the necessary operations as he reads through
instructions for the first time and have a working
package/supporting service when he finishes
The document currently has four sub-parts for each larger part.
sub-parts detail the following DUAs: WHOIS, "de," dixie's "ud"
ISODE's "doog." It is intended that additional sub-parts will
added to the document as new, portable DUA packages are designed
Where pertinent, the document assumes ISODE 8.0 is being used
1. Instructions for DUA-
A WHOIS interface to X.500 may be available on any ISODE-
machine which also runs a DSA (Directory System Agent.) Check
your local, ISODE-maintainer. If the service is available, users
access the Directory with the following command
whois -h <hostname>
Tignor [Page 1]
RFC 1373 DSA Support for Portable DUAs October 1992
<hostname> indicates the name of the host machine offering the
interface, surrounded by quotes. refers to
special, user-friendly syntax developed by Steve Hardcastle-Kille
UFN format is a comma-separated list of DN component values
(Attribute types are omitted.) The criteria for identifying
components in UFN is often less stringent than normal. For example
@c=US@st=California@o=Information
Institute@ou=HPCC@cn=Tom
could be uniquely specified in UFN syntax
tignor,isi,ca,
So to find this entry through WHOIS, one would type
whois -h "gum.isi.edu" tignor,isi,ca,
See Steve Hardcastle-Kille's Work in Progress, "User Friendly Naming
for details
Use of the "de" DUA is fully explained by the program's help section
New users should type "?" at the first prompt after installing
running the de executable
The de executable can be created and installed by the
simple steps
If you do not have a file called ".unknown_tailor" in your
directory, create it now. This file should contain the
single line
etcpath: /isode/etc
where is the full path name of your $
directory
If you do not have a directory $HOME/isode/bin, where "$HOME"
your home directory, create it now
ftp the compressed tar file "de-portable.tar.Z" from your local
ISODE-resident machine and put it in your isode directory.
you cannot find this file locally, it is available by
Tignor [Page 2]
RFC 1373 DSA Support for Portable DUAs October 1992
ftp from "gum.isi.edu" in the "x500" directory
cd $HOME/
uncompress < de-portable.tar.Z | tar xf -
If your name is listed in the Directory, edit the de/
file and add a line reading
username:
where indicates your Distinguished Name in
Directory
cp de/detailor de/etc/
Edit the CONFIG.make variables BINDIR, ETCDIR and SBINDIR
refer to your isode/bin, isode/etc and isode/etc directories
respectively. (The isode/etc directory was created by
previous command.)
ranlib libdsap.
ranlib libisode.
cd
./make
./make inst-
There is one error you may encounter during this procedure,
the "./make all" command
"Redeclaration of sprintf." in general.
If this error occurs, the following sub-procedure will fix
problem
Invoke your editor for the file ../h/general.
Search for the string "sprintf".
Cut the line with the "#endif" string which follows the
reading
char *sprintf ();
Paste the line under the line which reads "#endif". This
#endif line is exactly three lines below the current line
Tignor [Page 3]
RFC 1373 DSA Support for Portable DUAs October 1992
Save the file and quit the editor
Type "./make all" again. It should now compile smoothly. Finish up
typing "./make inst-all".
Dixie/
The "ud" DUA is designed for users doing most of their X.500
in one branch of the DIT (Directory Information Tree.) The
operates from a predefined "base," a position in the DIT one or
branches above the entries to be queried. The base is usually
organization name, such as
@c=US@st=California@o=Information Sciences
Ud starts with a preset base. (See below.) But this base can
changed with the "cb" command. "cb" takes the full DN of the new
as an argument. For example
cb @c=GB@o=University College
With a preset base, searching is easy. The user finds entries
the base with the "find" command. "find" takes the last component
the DN of the entry as its sole argument. The criteria for
argument is very loose. The partial matching performed by ud
return the desired data or a clarification request if the name is
all close to the real thing
For example, with a base "@c=US@st=California@o=Information
Institute", the
ou=HPCC@cn=Tom
could be found by
find
at the ud prompt
Other commands in ud are briefly described by the program's
section. Interested users should type "?" at the first prompt,
installing and running the executable
"Ud" comes with the "dixie" package, a mini-environment
specifically to support lightweight Directory access. Using
requires that a dixie server is running along with a DSA on
local, ISODE-resident machine. Before retrieving the dixie package
Tignor [Page 4]
RFC 1373 DSA Support for Portable DUAs October 1992
check with your local DSA manager to see that the dixie server is
and running
Once you're sure that everything is set up at the DSA-manager's end
the ud executable can be created and installed by the
simple steps
If you do not have a directory $HOME/isode/bin, where "$HOME"
your home directory, create it now
ftp (anonymously) the compressed tar file "dixie-<
#>.tar.Z", where is the number of the
release, from "terminator.cc.umich.edu" and put it in your
directory. The file is available in the "x500" directory
terminator
cd $HOME/
uncompress < dixie-.tar.Z | tar xf -
This creates the dixie environment. As a user interested in ud only
there are a number of things in the package that will be taking
space to no purpose. The following sequence of commands will get
of them
cd dixie-
rm -r
rm -r
rm -r
rm -r
cd ..
That done, we continue to bring ud to life
cd dixie-
Edit the file "ud/ud.h". There are two constants for which
will need to supply new values: DEFAULT_BASE and DEFAULT_SERVER
DEFAULT_BASE identifies ud's "base" upon startup, as
above. It takes a quoted DN as a value, e.g.,
"@c=US@st=California@o=Information Sciences Institute".
DEFAULT_SERVER identifies the machine which hosts the
server, i.e. your local, ISODE-resident machine. This
Tignor [Page 5]
RFC 1373 DSA Support for Portable DUAs October 1992
takes a quoted string as a value, e.g., "gum.isi.edu".
Edit the file "Makefile". Set the value of the BINDIR
to "/isode/bin", where is the full pathname
the user's home directory
make depend-
make ud-
make inst-
The "doog" DUA retrieves information on entries supplied by the
in UFN format. UFN format refers to a special, user-friendly
developed by Steve Hardcastle-Kille. UFN format is a comma-
list of DN component values. (Attribute types are omitted.)
criteria for identifying DN components in UFN is often less
than normal. For example
@c=US@st=California@o=Information
Institute@ou=HPCC@cn=Tom
could be specified in UFN syntax (and doog)
tignor,isi,ca,
See Steve Hardcastle-Kille's Work in Progress, "User Friendly Naming
for details
Other commands in doog are briefly described by the program's
section. Interested users should type "?" at the first prompt,
installing and running the executable
The doog executable can be created and installed by the
simple steps
If you do not have a file called ".unknown_tailor" in your
directory, create it now. This file should contain the
single line
etcpath: /isode/etc
where is the full path name of your $
directory
If you do not have a directory $HOME/isode/bin, where "$HOME"
Tignor [Page 6]
RFC 1373 DSA Support for Portable DUAs October 1992
your home directory, create it now
ftp the compressed tar file "doog-portable.tar.Z" from
local, ISODE-resident machine and put it in your
directory. If you cannot find this file locally, it is
by anonymous ftp from "gum.isi.edu" in the "x500" directory
cd $HOME/
uncompress < doog-isode-8.0.tar.Z | tar xf -
Edit the CONFIG.make variables BINDIR, ETCDIR and SBINDIR
refer to your isode/bin, isode/etc and isode/etc directories
respectively. (The isode/etc directory was created by
previous command.)
ranlib libdsap.
ranlib libisode.
cd
./make
./make inst-
2. Instructions for ISODE-
"WHOIS" is a simple program already available at most
workstations and hosts. It is normally used to access the database
users at NIC.DDN.MIL. The instructions below explain how to use
to access data in the White Pages Pilot X.500 database.
instructions are taken nearly word for word from the "PSI White
Pilot Project Administrator's Guide," section 2.8.3.
Choose a machine in your local environment which is running the
project software. This machine will offer the white pages service
a network port offering an emulation of the WHOIS service
On this machine, modify the /etc/services file so that it contains
entry like this
whitepages 17005/
Next, edit the file /etc/servers so that it has an entry like this
Tignor [Page 7]
RFC 1373 DSA Support for Portable DUAs October 1992
whitepages tcp $(SBINDIR)in.
Because most user interfaces to WHOIS, e.g., whois(1c), do not
the user to specify a special port, you should probably also add
line as well
whois tcp$(SBINDIR)in.
If you already have a line for whois in the servers file, then
are already running a WHOIS service, and you should NOT add a
whois line. This machine is not a good choice for running the
pages via WHOIS emulation
Note that on newer systems derived from Berkeley UNIX, /etc/
is called /etc/inetd.conf
The whitepages
On those systems which are to access the white pages via the
and not locally (i.e., those systems which are not running the
project software), you should determine how the user invokes
WHOIS service via the network. For UNIX systems, you should provide
shell script like this
: run this script through /bin/
exec /usr/ucb/whois -h wp.psi.net "$*"
where the name of a host running the pilot project software
substituted for whitepages, e.g., wp.psi.net. This host must have
files /etc/services and /etc/servers edited as described above
The compressed tar file for "de" can be created by the
sequence of commands. (Note: In the instructions which follow
indicates the top level of the ISODE distribution.)
cd /others/quipu/
Edit the de/detailor file to set the following options
dsa_address: (the address of your DSA
default_country: (your country
default_org: (your organization
cp de/make temp
Tignor [Page 8]
RFC 1373 DSA Support for Portable DUAs October 1992
Edit the de/make file so that the last line reads as follows
exec $M TOPDIR=../ -f ../CONFIG.make -f Makefile ${1+"$@"}
tar -cf de-portable.tar de/*
mv temp1 de/
mv de-portable.tar
(Here, is the directory immediately
ETCDIR.)
cd
tar -rf de-portable.tar etc/dsaptailor etc/
etc/oidtable.at etc/oidtable.oc etc/oidtable.
mv de-portable.tar
cd
cp config/CONFIG.make .
tar -rf de-portable.tar h/* h/quipu/* util/* CONFIG.
libdsap.a libisode.
rm CONFIG.
compress de-portable.
The compressed tar file for de will appear in the top level
of the ISODE distribution as "de-portable.tar.Z".
Dixie/
The latest version of the dixie distribution is available
anonymous ftp at "terminator.cc.umich.edu" in the "x500" directory
The file is named "dixie-.tar.Z", where is
number of the latest release
In order for anyone to use dixie clients, there must be a
dixie server which they can connect to. To set up the dixie server
the DSA manager should take the dixie package and explode/
it in the top level directory of the ISODE distribution. This is
with the following command
uncompress < dixie-.tar.Z | tar xf -
Tignor [Page 9]
RFC 1373 DSA Support for Portable DUAs October 1992
where is the version number of your dixie package.
will create a "dixie-" directory. The dixie server,
library and any DUAs included with the package will be in
directory branch. Software to support dixie on machines other
UNIX is included as well. This software is stored in the
"dos", "macintosh" and "vms". UNIX users should feel free to
these directories and all their contents. Commands of the form
rm -r
where is the directory name, should accomplish this task
In the top level of the dixie distribution is a file
"Makefile". The file holds several variables which should
configured to match those of your ISODE environment
BINDIR
ETCDIR
INCLUDEDIR
In the "server" directory below the top level of the
distribution is another "Makefile" file. Configure the
variable in this file, as well
After setting these variables, cd to the top level of the
distribution and type the following commands
make depend-
make server-
make inst-
This will create and install the dixie server in your ETCDIR. cd
the ETCDIR and type "dixie" to start the server
The compressed tar file for "doog" can be created by the
sequence of commands. (Note: In the instructions which follow
indicates the top level of the ISODE distribution.)
cd /others/quipu/
cp doog/make temp
Tignor [Page 10]
RFC 1373 DSA Support for Portable DUAs October 1992
Edit the doog/make file so that the last line reads as follows
exec $M TOPDIR=../ -f ../CONFIG.make -f Makefile ${1+"$@"}
cp doog/query/make temp
Edit the doog/query/make file so that the last line reads
follows
exec $M TOPDIR=../../ -f ../../CONFIG.make -f
${1+"$@"}
tar -cf doog-portable.tar doog/*
mv temp1 doog/
mv temp2 doog/query/
mv doog-portable.tar ../../..
cd ../../..
cp config/CONFIG.make .
tar -rf doog-portable.tar h/* h/quipu/* util/* CONFIG.
libdsap.a libisode.
rm CONFIG.
mv doog-portable.tar
(Here, is the directory immediately
ETCDIR.)
cd
tar -rf doog-portable.tar etc/dsaptailor etc/
etc/oidtable.at etc/oidtable.gen etc/oidtable.
compress doog-portable.
The compressed tar file for doog will appear in the
immediately above ETCDIR as "doog-portable.tar.Z".
Security
Security issues are not discussed in this memo
Tignor [Page 11]
RFC 1373 DSA Support for Portable DUAs October 1992
Author's
Tom
University of Southern
Information Sciences
4676 Admiralty
Marina del Rey, CA 90292
Phone: (310) 822-1511
EMail: tpt2@isi.
Tignor [Page 12]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
