[16306] in Kerberos_V5_Development
Re: Project Review: kinit -C
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Wed Sep 15 17:15:26 2010
Mime-Version: 1.0 (Apple Message framework v1081)
From: Ken Raeburn <raeburn@mit.edu>
In-Reply-To: <tsl4odrm8g3.fsf@live.mit.edu>
Date: Wed, 15 Sep 2010 17:15:19 -0400
Message-Id: <77C88064-5F44-4367-8921-3AC46358AD89@mit.edu>
To: "krbdev@mit.edu Dev List" <krbdev@mit.edu>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
Wouldn't most of this problem go away if keytab types were pluggable?
If kinit gets the -C option, it sets the use-keytab flag and sets the keytab type to KDB: and goes about its business. If the plugin doesn't exist (probably because you're not on the KDC), you detect the magic error code combined with the -C flag and print a custom message. (Maybe more than one error code: keytab type unknown; database not found; permission denied.) One kinit binary fits all.
That would just leave the question of whether pluggable keytab types are a good idea. :-)
Ken
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
