🚀 go-pugleaf

In article <1992Nov20.032345.18307@kodak.kodak.com>,
deal@tempus.Kodak.Com (Stephen M. Deal) writes:

>One major implication of distributed processing (of which C/S is but one
>manifestation) is that of authentication.
...
>How do you authorize a client? Can you even trust a client? Perhaps
>those clients executing on a node that has password protection (e.g.
>UNIX, VAX/VMS) can be trusted but what about single tasking nodes that
>run a Disk Operating System (a.k.a. DOS)?
...
>Kerberos (from MIT's Project Athena) provides a glimmer of hope but I
>have not seen any C/S vendor embrace this approach.
...
>Has anyone given much thought to client authentication on PCs and Macs?
>Does anyone have any thoughts on how a server (DB  or otherwise) would
>handle such a mechanism?

You may want to look at RFC 931, "Authentication server", which
proposes a protocol for user authentication from remote clients.

RFC's (Requests for Comments) are available from nic.ddn.nil
via anonymous ftp.  You may be able to locate it elsewhere as well.
If you can't locate it, I can email a copy to you.

--
Steve Bacher (Batchman)                 Draper Laboratory
Internet: seb@draper.com                Cambridge, MA, USA