Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!rutgers!mtune!wrcola!kathy
From: kathy@wrcola.UUCP (K.M.Vincent)
Newsgroups: comp.unix.questions
Subject: Re: Hostname aliasing in HDB UUCP
Message-ID: <849@wrcola.UUCP>
Date: Thu, 27-Aug-87 11:44:34 EDT
Article-I.D.: wrcola.849
Posted: Thu Aug 27 11:44:34 1987
Date-Received: Sat, 29-Aug-87 09:58:38 EDT
References: <623@quacky.UUCP>
Reply-To: kathy@wrcola.UUCP (K.M.Vincent)
Organization: AT&T, Winston-Salem, NC
Lines: 37

In article <623@quacky.UUCP> dce@mips.UUCP (David Elliott) writes:
>
>The situation is that system X wants to talk to system Y, while
>calling it Z.
>
>That is, the Systems file entry looks like:
>
>	hp-cup Any ...
>
>but the machine on the other side is actually named 'hpda'.
>
>Does anyone know of any way to "alias" a Systems entry in this
>way, or is it just unsafe?


I've heard of this being done - but with the called end
controlling the situation.  For example, cuaepd was not a real
machine - it was a "virtual" machine on cuae2, set up to enable
people to access mod.sources archives.  

Someone else I know did the same thing.  He set up his system
so that if another machine called in looking for "market" - his
"virtual machine" - his machine "bpsrate" allowed a different set
of permissions and such.  [Ed.note: The names have been changed
to protect the innocent.]

The key was in the Permissions file.  There's an option you can
set (sorry, no docs handy, and I don't remember the name) so that,
if machine A calls in and tells your machine it's looking for
machine X, your machine tells machine A that it *is* machine X. 
And away you go.

Unsafe, yes ...


Kathy Vincent -----> AT&T: {ihnp4|mtune|burl}!wrcola!kathy
              -----> Home: {ihnp4|mtune|ptsfa|codas}!bakerst!kathy