Projects/Password response item - Revision history

Ghudson at 15:51, 12 October 2012

2012-10-12T15:51:01Z

Ghudson: /* Internal view */

2012-10-12T15:50:39Z

‎Internal view

Ghudson: /* clpreauth module view */

2012-10-11T15:46:15Z

‎clpreauth module view

Ghudson: /* clpreauth module view */

2012-10-11T15:44:30Z

‎clpreauth module view

Ghudson: New page: {{project-early}} This project is a follow-on to Projects/Responder. For clpreauth modules, it specifies a way for preauth modules to get the AS key using either the supplied passwor...

2012-09-18T02:12:39Z

New page: {{project-early}} This project is a follow-on to Projects/Responder. For clpreauth modules, it specifies a way for preauth modules to get the AS key using either the supplied passwor...

New page

{{project-early}}

This project is a follow-on to [[Projects/Responder]]. For clpreauth modules, it specifies a way for preauth modules to get the AS key using either the supplied password or keytab, the responder, or the prompter as appropriate. For applications, it specifies a way to supply the password via the responder.

==clpreauth module view==

Some client preauth mechanisms, such as encrypted timestamp or encrypted challenge, need access to the client's long-term key in order to prove knowledge of it. These mechanisms are used most often with a password, but can also be used with a keytab. When a password is used, it may currently be obtained from the password parameter to krb5_get_init_creds_password or from the prompter. Although we would like the password to be obtained from the responder when appropriate, we cannot do so by having the clpreauth module directly ask for the password.

Instead, a clpreauth module's prep_questions method can indicate interest in the client long-term key with a new callback:

void (*need_as_key)(krb5_context context, krb5_clpreauth_rock rock);

This informs libkrb5 that the module's process method will require the long-term key. The module uses the existing get_as_key callback to obtain the key in the process method.

==Application view==

An application can currently supply the password as a parameter to krb5_get_init_creds_password, or it can wait to be prompted for the password via the prompter. In addition to these options, we add a response item type whose name is "password", whose challenge is NULL, and whose answer is simply the password. Applications can refer to this response item name using the new constant KRB5_RESPONDER_QUESTION_PASSWORD.

==Internal view==

Passwords are currently obtained through the gak_fct parameter of krb5int_get_init_creds(). We amend this interface (which is non-public)

(TBD)

← Older revision		Revision as of 15:51, 12 October 2012
Line 1:		Line 1:
−	{{project-~~early~~}}	+	{{project-rel\|1.11}}

	This project is a follow-on to [[Projects/Responder]]. For clpreauth modules, it specifies a way for preauth modules to get the AS key using either the supplied password or keytab, the responder, or the prompter as appropriate. For applications, it specifies a way to supply the password via the responder.		This project is a follow-on to [[Projects/Responder]]. For clpreauth modules, it specifies a way for preauth modules to get the AS key using either the supplied password or keytab, the responder, or the prompter as appropriate. For applications, it specifies a way to supply the password via the responder.

← Older revision		Revision as of 15:50, 12 October 2012
Line 19:		Line 19:
	==Internal view==		==Internal view==

−	Passwords are currently obtained through the gak_fct parameter of krb5int_get_init_creds(). We amend this interface (which is non-public)	+	Passwords are currently obtained through the gak_fct parameter of krb5int_get_init_creds(). We amend this interface (which is non-public) in two ways:

−	(TBD)
		+	* A new argument is added to give the gak function access to the response items for the authentication.
		+
		+	* A gak function can be called with a null as_key parameter in order to indicate a future interest in the AS key.
		+
		+	The gic_keytab gak function does nothing with the response items and performs no operations when a future interest in the AS key is indicated. The gic_pwd gak function adds the password question to the response items if a future interest in the AS key is indicated (unless the password is already available through the API), and retrieves the password from the response items when the AS key is requested.

@@ Line 9: / Line 9: @@
 Instead, a clpreauth module's prep_questions method can indicate interest in the client long-term key with a new callback:
-    krb5_error_code (*need_as_key)(krb5_context context, krb5_clpreauth_rock rock);
+    void (*need_as_key)(krb5_context context, krb5_clpreauth_rock rock);
 This informs libkrb5 that the module's process method will require the long-term key.  The module uses the existing get_as_key callback to obtain the key in the process method.