| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
From: Greg Hudson <ghudson@mit.edu> To: Nicolas Williams <Nicolas.Williams@sun.com> In-Reply-To: <20100322222459.GN19496@Sun.COM> Date: Tue, 23 Mar 2010 12:31:09 -0400 Message-ID: <1269361869.7493.442.camel@ray> Mime-Version: 1.0 Cc: MIT Kerberos Dev List <krbdev@mit.edu> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: krbdev-bounces@mit.edu On Mon, 2010-03-22 at 18:24 -0400, Nicolas Williams wrote: > But boy do we need prompt type information in pam_krb5! [...] > Yes, but the prompter may still need to know what this is about. [...] > Clearly it's OK to use it. But using it doesn't solve Will's problem. [...] > There's a set of prompt types that are specific to PKINIT that would > greatly help Will now: > > - insert-token > - enter-PIN > - enter-PIN-on-the-smartcard's-PIN-pad Can I have a bit more information about what Sun's pam_krb5 implementation wants to do with the prompt types? We can probably add these three once I understand the need for them. _______________________________________________ krbdev mailing list krbdev@mit.edu https://mailman.mit.edu/mailman/listinfo/krbdev
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |