[3003] in SIPB_Linux_Development
Re: registration of linux machines
daemon@ATHENA.MIT.EDU (Garry Zacheiss)
Tue Sep 26 22:58:26 2000
Message-Id: <200009270258.WAA17673@hodge-podge.mit.edu>
To: Alex Coventry <alex_c@MIT.EDU>
cc: linux-dev@MIT.EDU
In-Reply-To: Your message of "Tue, 26 Sep 2000 22:51:47 EDT."
<200009270251.WAA01321@alice-whacker.mit.edu>
Date: Tue, 26 Sep 2000 22:58:00 -0400
From: Garry Zacheiss <zacheiss@MIT.EDU>
>> So, according to Gary Zacheiss, all hesreq really needs is the hostname
>> and the machine architecture, so anyone who sends mail saying 'Please
>> register me for hesiod' will get it at the hostname they sent mail
>> from. Sound good?
That's not quite what I said. I said we needed to know the hostname
of the machine and the architecture they would like hesiod for, and at
least when I was doing hesreq, I would always do cursory authentication
and make sure that the address the mail was sent from corresponded to
the owner or contact of the machine in moira.
That said, it seems the best thing to do is to add a screen to the
installer that presents a copy of a piece of mail that will be sent to
hesreq saying "Please create public Linux hesiod for host foo", with foo
filled in, and present a button to the user asking for confirmation in
sending that mail.
I don't know how hard it would be to add this to the installer. If
it's too technically difficult, just putting up a "visit this URL" to
register is probably fine.
>> While I was thinking about this, it occurred to me that we should check
>> using stella that the IP address the user gives is registered in moira
>> to the hostname the user gives. Is there any way to access stella
>> before all the packages have been installed?
This seems unnecessarily complex and not worth the effort; also note
that you won't have access to stella (or any moira clients) until afs
has started, since the Athena packages only install attachandrun scripts
for the moira clients, which are maintained outside of the release.
Garry
