Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!purdue!decwrl!shelby!MSR.EPM.ORNL.GOV!dunigan
From: dunigan@MSR.EPM.ORNL.GOV (Tom Dunigan 576-2522)
Newsgroups: comp.protocols.kerberos
Subject: session key for broadcast service -- how?
Message-ID: <8904251345.AA09920@MSR.EPM.ORNL.GOV>
Date: 25 Apr 89 13:45:21 GMT
Sender: daemon@shelby.Stanford.EDU
Organization: The Internet
Lines: 14

is there a mechansim for a "broadcast server" to request a session
key, and then have clients be able to request that same session key
so they can verify the "safe" messages from the broadcast server?


e.g., clients want to verify that routing updates (RIP) are coming
from a valid router and that the messages haven't been tampered.
Registered router requests "session key", clients routing listeners
request key(s) for known router(s).  Routers broadcast "safe" messages,
listeners can thus verify.


(of course, if routing updates were point-to-point service, then
use of Kerberos is obvious)