Generating KRB5 keytab Ticket

oudjehani dina oudjehani.dina at
Thu Feb 19 10:50:06 EST 2004


I have the same problem, did you find a solution?

Thnks for your help!

Dina..From kenh at Fri Feb 20 10:30:58 2004
	by (8.12.8p2/8.12.8) with ESMTP id i1KFUvqb008554
	for <krbdev at>; Fri, 20 Feb 2004 10:30:57 -0500 (EST)
Received: from (
	for <krbdev at>; Fri, 20 Feb 2004 10:30:56 -0500 (EST)
Received: from ( [])
	(authenticated bits=0)i1KFUqg5008861
	for <krbdev at>; Fri, 20 Feb 2004 10:30:53 -0500 (EST)
Message-Id: <200402201530.i1KFUqg5008861 at>
To: krbdev at
In-Reply-To: Message from Sam Hartman <hartmans at> 
	<tslad3e1yym.fsf at> 
X-Face: "Evs"_GpJ]],xS)b$T2#V&{KfP_i2`TlPrY$Iv9+TQ!6+`~+l)#7I)0xr1>4hfd{#0B4
	WIn3jU;bql;{2Uq%zw5bF4?%F&&j8 at KaT?#vBGk}u07<+6/`.F-3_GA at 6Bq5gN9\+s;_d
	gD\SW #]iN_U0 KUmOR.P<|um5yP<ea#^"SJK;C*}fMI;
Date: Fri, 20 Feb 2004 10:30:52 -0500
From: Ken Hornstein <kenh at>
X-Spam-Score: () hits=0 User Authenticated
X-Virus-Scanned: NAI Completed
X-Scanned-By: MIMEDefang 2.30 (www . roaringpenguin . com / mimedefang)
Subject: Re: Discussion of krb5_get_init_creds_password() behavior was
 Re:problem with the kinit_prompter in kfw 2.5 
X-BeenThere: krbdev at
X-Mailman-Version: 2.1
Precedence: list
List-Id: Kerberos Developers Mailing List <>
List-Help: <mailto:krbdev-request at>
List-Post: <mailto:krbdev at>
List-Subscribe: <>,
	<mailto:krbdev-request at>
List-Archive: <>
List-Unsubscribe: <>,
	<mailto:krbdev-request at>
X-List-Received-Date: Fri, 20 Feb 2004 15:30:58 -0000

>So, I'm confused.  I agree there is a problem if you enter in a null
>password and in that case you will get double prompted.
>In all other cases I fail to see the problem.  Note that you have to
>explicitly declare your list of master KDCs.  By default in 1.3.x, no
>KDCs are masters and no second attempt is made.

"Hm".  The reason this screws me is that it results in a double-prompt
for a hardware preauth token code if the first one is incorrect.  But
I've noticed that this still happens in the 1.3.x-based code I'm
using.  Perhaps I messed up the merge somewhere; I need to look at it
more closely.


More information about the krbdev mailing list