Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA25834; Tue, 26 Dec 95 22:29:34 EST Received: by MIT.EDU id AB11289; Tue, 26 Dec 95 22:29:06 EST Date: Tue, 26 Dec 95 22:29:06 EST From: MAILER-DAEMON@MIT.EDU (Mail Delivery Subsystem) Subject: Returned mail: Cannot send message for 3 days Message-Id: <9512270329.AB11289@MIT.EDU> To: To: proven@PO7.LOCAL To: tytso@PO9.LOCAL To: basch@lehman.com To: jis@E40-PO.LOCAL To: tlyu@PO9.LOCAL ----- Transcript of session follows ----- 421 pyro.rh.imsa.edu.tcp... Deferred: Connection timed out during user open with pyro.rh.imsa.edu 451 hangman@pyro.rh.imsa.edu... Cannot send message for 3 days hangman@pyro.rh.imsa.edu... Cannot send message for 3 days ----- Unsent message follows ----- Received: from toxicwaste.media.mit.edu by MIT.EDU with SMTP id AA05966; Sat, 23 Dec 95 22:20:51 EST Received: (from warlord@localhost) by toxicwaste.media.mit.edu (8.6.10/8.6.10) id WAA13253; Sat, 23 Dec 1995 22:20:52 -0500 Message-Id: <199512240320.WAA13253@toxicwaste.media.mit.edu> To: "Calvin G. Smith" Cc: kerberos@MIT.EDU Subject: Re: Thinking of moving to kerberos, lots of questions In-Reply-To: Your message of "Sat, 23 Dec 1995 21:17:10 EST." Date: Sat, 23 Dec 1995 22:20:52 EST From: Derek Atkins > drat. I was afraid of that. Any sources out there that I can use? When I was a summer intern at Bellcore a few years ago I wrote one. But I don't have the source anymore. Basically, what you do is take a login that understands both kerberos and YP, hack it up a little to do the appropriate checks, and then add some of the kadmin "ank" code to add a new key to the database. Alternatively, you can provide a user-space program that does the same thing -- ask a user for a password, compare it to the passwd entry in YP, and then add the password to kerberos. This, too, would be fairly simple to write but I don't have code for you... Perhaps someone else has code to share? -derek PS: I might have to write something like this in the next few months, but not in the near future.