Received: from SOUTH-STATION-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA03072; Thu, 28 Dec 95 06:51:50 EST
Received: from trefle.saclay.cea.fr by MIT.EDU with SMTP
	id AA02292; Thu, 28 Dec 95 06:51:27 EST
Received: from oeillet.saclay.cea.fr by trefle.saclay.cea.fr
	(8.6.10/ CEANET-ROUTER-3.0) with ESMTP id MAA00921
	for <owner-kerberos@MIT.EDU>; Thu, 28 Dec 1995 12:51:07 +0100
Received: from localhost by oeillet.saclay.cea.fr
	(8.6.10/ CEANET-ROUTER-3.0) with internal id MBS17889
	; Thu, 28 Dec 1995 12:52:26 +0100
Date: Thu, 28 Dec 1995 12:52:26 +0100
From: Mailer-Daemon@oeillet.saclay.cea.fr (Mail Delivery Subsystem)
Subject: Returned mail: Cannot send message for 3 days
Message-Id: <199512281152.MBS17889@oeillet.saclay.cea.fr>
To: <owner-kerberos@MIT.EDU>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="MBS17889.820151546/oeillet.saclay.cea.fr"

This is a MIME-encapsulated message

--MBS17889.820151546/oeillet.saclay.cea.fr

The original message was received at Sun, 24 Dec 1995 14:35:04 +0100
from trefle.saclay.cea.fr [132.166.192.212]

   ----- The following addresses had delivery problems -----
<zucco@gardenia.saclay.cea.fr>  (unrecoverable error)

   ----- Transcript of session follows -----
<zucco@gardenia.saclay.cea.fr>... Deferred: Connection timed out with gardenia.saclay.cea.fr.
Message could not be delivered for 3 days
Message will be deleted from queue

   ----- Original message follows -----

--MBS17889.820151546/oeillet.saclay.cea.fr
Content-Type: message/rfc822

Return-Path: <owner-kerberos@MIT.EDU>
Received: from trefle.saclay.cea.fr by oeillet.saclay.cea.fr
	(8.6.10/ CEANET-ROUTER-3.0) with ESMTP id OAA06379
	for <zucco@gardenia.saclay.cea.fr>; Sun, 24 Dec 1995 14:35:04 +0100
Received: from MIT.EDU by trefle.saclay.cea.fr
	(8.6.10/ CEANET-ROUTER-3.0) with SMTP id OAA11205
	for <zucco@gardenia.saclay.cea.fr>; Sun, 24 Dec 1995 14:33:48 +0100
Received: from pad-thai.cam.ov.com by MIT.EDU with SMTP
	id AA14610; Sun, 24 Dec 95 08:22:30 EST
Received:  by pad-thai.cam.ov.com (8.6.12/)
	id <IAA16798@pad-thai.cam.ov.com>; Sun, 24 Dec 1995 08:25:31 -0500
Received: from GATEWAY by pad-thai.cam.ov.com with netnews
	for kerberos-wrapper@cam.ov.com (kerberos@mit.edu)
To: kerberos@MIT.EDU
Date: 24 Dec 1995 04:30:07 -0500
From: tls@rek.tjls.com (Thor Lancelot Simon)
Message-Id: <4bj6iv$2d3@fearsome.tjls.com>
Organization: Never!
Sender: usenet@cam.ov.com
References: <Pine.LNX.3.91.951223204028.3021A-100000@excelsior>, <199512240320.WAA13253@toxicwaste.media.mit.edu>
Subject: Re: Thinking of moving to kerberos, lots of questions

In article <199512240320.WAA13253@toxicwaste.media.mit.edu>,
Derek Atkins <warlord@MIT.EDU> wrote:
>> 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?

Berkeley's "register" client and server did this.  Unfortunately they aren't
really compatible with kadmin; you'd have to run a separate kadmind and
registerd, and modify your kdb_init to create the keys register wants to use.

But if you want to look at the source, it's in the domestic 4.4Lite
distribution.
-- 
Thor Lancelot Simon                                             tls@rek.tjls.com

   Where is the day that melted into one rich noise?          --Thomas Wolfe

--MBS17889.820151546/oeillet.saclay.cea.fr--

