[19201] in Kerberos

home help back first fref pref prev next nref lref last post

Re: Apps aquiring tickets

daemon@ATHENA.MIT.EDU (Sam Hartman)
Tue May 6 17:41:34 2003

To: Ken Raeburn <raeburn@mit.edu>
From: Sam Hartman <hartmans@MIT.EDU>
Date: Tue, 06 May 2003 17:40:44 -0400
In-Reply-To: <tx13cjrx234.fsf@mit.edu> (Ken Raeburn's message of "Tue, 06
 May 2003 16:16:47 -0400")
Message-ID: <tslhe87da8z.fsf@mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: greg@enjellic.com
cc: kerberos@mit.edu
Errors-To: kerberos-bounces@mit.edu

People looking at this should consider the Kerberos login library
architecture used by KFM and look at whether that architecture is
appropriate for other platforms.

Decisions that KLL makes:

1) The graphical prompting is done in the context of the application.
   You could argue against this because it means any arbitrary
   application can prompt you for a password.

2) Library functions may attempt to interact with the terminal and get
    tickets in text mode.

Note that MIT will continue to have to support KLL for KFM, so any
significaantly different architecture will be harder for us to accept.

Personally I'm not yet convinced this problem is worth solving.  I
think the Windows approach of getting tickets at login and continually
renewing them is appropriate.

________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

home help back first fref pref prev next nref lref last post