The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] NFS & Kerberos woes...
Date: Wed, 26 Dec 2018 01:48:42 -0700	[thread overview]
Message-ID: <9a102767-bff2-c6e6-d585-23cac100d715@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <20181226020119.GF18199@mcvoy.com>

[-- Attachment #1: Type: text/plain, Size: 856 bytes --]

On 12/25/18 7:01 PM, Larry McVoy wrote:
> I'm an NFS guy, learned it a bit at uwisc and then a lot more at Sun. 
> But Sun didn't do the Kerberos stuff, at least while I was there.

That sort of surprises me.  I guess I had assumed that NFS was Sun 
centric.  Though I shouldn't be surprised that someone else stood on 
Sun's shoulders and extended NFS.  Especially when (I think that) 
Kerberos MIT centric.

> Didn't Kerberos come from MIT?  If so, I bet anything that Ted Ts'o 
> would know the details.  My guess is it was part of project athena and 
> I think that overlaps with Ted.  Yo, Ted, Merry Christmas, what about 
> this Kerberos authentication stuff?  :)

Thank you for the response Larry.  It's amazing what can be learned by 
participating in the TUHS mailing list & community.  :-D



-- 
Grant. . . .
unix || die


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4008 bytes --]

  parent reply	other threads:[~2018-12-26  8:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-26  0:49 Grant Taylor via TUHS
2018-12-26  2:01 ` Larry McVoy
2018-12-26  4:49   ` Theodore Y. Ts'o
2018-12-26  8:45     ` Grant Taylor via TUHS
2018-12-27  6:27     ` Grant Taylor via TUHS
2018-12-26  8:48   ` Grant Taylor via TUHS [this message]
2018-12-27  6:24 ` [TUHS] NFS & Kerberos woes... — SOLVED Grant Taylor via TUHS

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9a102767-bff2-c6e6-d585-23cac100d715@spamtrap.tnetconsulting.net \
    --to=tuhs@minnie.tuhs.org \
    --cc=gtaylor@tnetconsulting.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).