Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA23668; Sat, 30 Sep 95 07:19:33 EDT Received: from argus.posten.se by MIT.EDU with SMTP id AA05969; Sat, 30 Sep 95 07:19:03 EDT Received: (from smap@localhost) by argus.posten.se (8.6.12/8.6.12) id MAA12617 for ; Sat, 30 Sep 1995 12:19:25 +0100 Received: from unknown(147.14.7.70) by argus via smap (V1.3mjr) id sma012614; Sat Sep 30 12:18:27 1995 Received: from localhost (localhost) by info.Posten.SE (8.6.10/8.6.9) with internal id MAA08311; Sat, 30 Sep 1995 12:18:46 +0100 Date: Sat, 30 Sep 1995 12:18:46 +0100 From: Mail Delivery Subsystem Subject: Returned mail: warning: cannot send message for 4 hours Message-Id: <199509301118.MAA08311@info.Posten.SE> To: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="MAA08311.812459926/info.Posten.SE" This is a MIME-encapsulated message --MAA08311.812459926/info.Posten.SE ********************************************** ** THIS IS A WARNING MESSAGE ONLY ** ** YOU DO NOT NEED TO RESEND YOUR MESSAGE ** ********************************************** The original message was received at Sat, 30 Sep 1995 08:08:44 +0100 from argus [192.121.54.163] ----- The following addresses had delivery problems ----- (transient failure) ----- Transcript of session follows ----- ... Deferred: Connection timed out with a18.psab.posten.se. Warning: message still undelivered after 4 hours Will keep trying until message is 5 days old ----- Original message follows ----- --MAA08311.812459926/info.Posten.SE Content-Type: message/rfc822 Return-Path: owner-kerberos@MIT.EDU Received: from argus.posten.se (argus [192.121.54.163]) by info.Posten.SE (8.6.10/8.6.9) with ESMTP id IAA07400 for ; Sat, 30 Sep 1995 08:08:44 +0100 Received: (from smap@localhost) by argus.posten.se (8.6.12/8.6.12) id IAA11571 for ; Sat, 30 Sep 1995 08:08:22 +0100 Received: from pacific-carrier-annex.mit.edu(18.72.0.21) by argus via smap (V1.3mjr) id sma011569; Sat Sep 30 08:08:02 1995 Received: from pad-thai.cam.ov.com by MIT.EDU with SMTP id AA28227; Sat, 30 Sep 95 02:44:42 EDT Received: by pad-thai.cam.ov.com (8.6.12/) id ; Sat, 30 Sep 1995 02:46:57 -0400 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: 29 Sep 1995 21:25:39 GMT From: orion@iastate.edu (Phi H Truong) Message-Id: <44ho8j$1bm@news.iastate.edu> Organization: Iowa State University, Ames, Iowa USA Sender: usenet@cam.ov.com References: <448ih1$m3e@aladdin.iii.org.tw>, <44f4ru$i1a@eco.twg.com> Reply-To: orion@iastate.edu (Phi H Truong) Subject: Re: How to remove principal ? In article <44f4ru$i1a@eco.twg.com>, Reece R. Pollack wrote: > >In article <448ih1$m3e@aladdin.iii.org.tw>, root@linux.golden.com.tw (root) writes: >|>I've install kerbero IV on Solaris 2.4. Everything is fine. But only I >|>don't know how to remove a principal from kerberos' database. Is there >|>any utility available for removing principal ? I've tried kadmin, but >|>it doesn't contain the removal function. > >This was an (unfortunately) intentional omission. The only way to remove >a principal from a V4 database is to dump the database, edit the dumped >file with a text editor to remove the (un)desired records, then reload >the database. > Look into the sources of libkdb you will find out that isn't hard to create a facility to remove principal without dumping the database. you shouldn't remove the master key though, i.e. restrictions checking. -- _____ Phi H. Truong "No wisdom. No enlightenment. Only you." orion@iastate.edu ISU Computation Center Systems Analyst 237 Durham Center ph: (515) 294 -1420 --MAA08311.812459926/info.Posten.SE--