Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!mit-eddie!ll-xn!ames!ucbcad!ucbvax!decvax!eagle_snax!geoff
From: geoff@eagle_snax.UUCP ( R.H. coast near the top)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: Authentication
Message-ID: <210@eagle_snax.UUCP>
Date: Sun, 18-Oct-87 11:29:06 EDT
Article-I.D.: eagle_sn.210
Posted: Sun Oct 18 11:29:06 1987
Date-Received: Tue, 20-Oct-87 23:52:49 EDT
References: <12342540195.19.BILLW@MATHOM.CISCO.COM> <[SRI-NIC.ARPA]Wed,.14.Oct.87.18:49:04.PDT.STJOHNS>
Lines: 14
Summary: I gave up and rolled my own

I faced this problem with PC-NFS: how do you "log in" to a PC and
acquire credentials to use over the wire. Finding nothing in the
standards world, I rolled my own: a fairly trivial RPC-based
implementation. The server side code ("pcnfsd") is in the public
domain, and a number of people are using it. It doesn't use
encryption (useless unless you're going to do it ALL right: see
the "Secure RPC" paper from one of the recent Usenix's) but it
does use a rot13-like scrambling to discourage casual browsers.

-- 
Geoff Arnold, Sun Microsystems       | "Picture a bright blue ball,
East Coast Division (home of PC-NFS) |  Spinning, spinning free;
UUCP: {ihnp4,decwrl,...}!sun!garnold |  Dizzy with possibility...
ARPA: garnold@sun.com                |  Ashes, ashes, all fall down..."