dunigan@MSR.EPM.ORNL.GOV (Tom Dunigan 576-2522) (04/25/89)
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)
bcn@JUNE.CS.WASHINGTON.EDU (Clifford Neuman) (05/01/89)
Date: Tue, 25 Apr 89 09:45:21 EDT From: dunigan@MSR.EPM.ORNL.GOV (Tom Dunigan 576-2522) 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? Are the clients trusted? If not, then this scenario requires public key cryptography since all the clients will know the key. If you trust all the clients and can accept each client having the ability to impersonate the server, then all that is needed is a way to generate multiple tickets containing a common session key. Allowing this is under consideration. ~ Cliff