summaryrefslogtreecommitdiffstats
path: root/src/lib
diff options
context:
space:
mode:
authorGreg Hudson <ghudson@mit.edu>2012-12-13 14:53:58 -0500
committerGreg Hudson <ghudson@mit.edu>2012-12-13 14:53:58 -0500
commit70f2d9a093c71624269b2317c62ad0993126bc40 (patch)
tree261ce59d111855a2132c9c8a58ebe8b3f3f99484 /src/lib
parent85c378e9e44ca184209056f118e75b6511cb40b8 (diff)
downloadkrb5-70f2d9a093c71624269b2317c62ad0993126bc40.tar.gz
krb5-70f2d9a093c71624269b2317c62ad0993126bc40.tar.xz
krb5-70f2d9a093c71624269b2317c62ad0993126bc40.zip
Use an empty challenge for the password question
If a question's challenge is NULL, it is unnecessarily difficult for a responder callback to detect whether it was asked. So it's better to use an empty challenge when there is no challenge data to communicate. Do this for the "password" question. ticket: 7499 (new) target_version: 1.11 tags: pullup
Diffstat (limited to 'src/lib')
-rw-r--r--src/lib/krb5/krb/gic_pwd.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/lib/krb5/krb/gic_pwd.c b/src/lib/krb5/krb/gic_pwd.c
index 8ffa342be..30da8c9b3 100644
--- a/src/lib/krb5/krb/gic_pwd.c
+++ b/src/lib/krb5/krb/gic_pwd.c
@@ -36,7 +36,7 @@ krb5_get_as_key_password(krb5_context context,
return k5_response_items_ask_question(ritems,
KRB5_RESPONDER_QUESTION_PASSWORD,
- NULL );
+ "");
}
/* If there's already a key of the correct etype, we're done.