Article View: comp.protocols.kerberos
Article #851Getting new principal key
From: Randy Buckland
Date: Thu, 19 Nov 1992 19:35
Date: Thu, 19 Nov 1992 19:35
23 lines
1462 bytes
1462 bytes
For various reasons, I need to perform the following sequence of operations: 1. Run kinit (or equivalent) on machine A 2. Run telnet/rlogin/rsh like utility on machine A 2a. utility contacts machine B 2b. server on machine B authenticates user from A 2c. server on machine B creates new ticket file for user on B 2d. server on machine B runs desired command under user's environment. 3. server on machine B removes tickets and cleans up in general after command has completed The problem I have is that I can't figure out how to do step 2c. For example, if the command passed to B is "klist", it should list just the krbtgt ticket for that user. The V4 rsh/etc. tools will not do step 2c The reason I want to do this is to allow the command run on machine B to run as the user and get tickets of it's own for other operations. I just need some way to propigate the krbtgt ticket. -- Randy Buckland "It's hard to work North Carolina State University in a group when you're randy_buckland@ncsu.edu (919) 515-5491 omnipotent" -- Q
Technical Details
Message-ID:
<rcb.722201703@news.ncsu.edu>Path:
arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!rock!taco!rcbShow Full Headers
Complete Article Headers
Newsgroups: comp.protocols.kerberos Path: arc1-ca.pugleaf.net!sparky!uunet!stanford.edu!rock!taco!rcb From: rcb@ncsu.edu (Randy Buckland) Subject: Getting new principal key Message-ID: <rcb.722201703@news.ncsu.edu> Sender: news@ncsu.edu (USENET News System) Organization: North Carolina State University Date: Thu, 19 Nov 1992 19:35:03 GMT Lines: 23