krb5 commit: Test that kinit -k -i picks the intended principal

Benjamin Kaduk kaduk at MIT.EDU
Thu May 22 17:34:37 EDT 2014


https://github.com/krb5/krb5/commit/44adf120d8548b9bb43a380e6f1889840c4a4a3d
commit 44adf120d8548b9bb43a380e6f1889840c4a4a3d
Author: Ben Kaduk <kaduk at mit.edu>
Date:   Mon May 19 16:38:42 2014 -0400

    Test that kinit -k -i picks the intended principal
    
    Prior to ticket 7892 it would use the default host/ principal
    when no principal was given on the command line.
    
    ticket: 7892

 src/tests/t_keytab.py |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/src/tests/t_keytab.py b/src/tests/t_keytab.py
index 3008911..8e2cd23 100644
--- a/src/tests/t_keytab.py
+++ b/src/tests/t_keytab.py
@@ -20,6 +20,9 @@ if 'no suitable keys' not in output:
 
 # Test kinit and klist with client keytab defaults.
 realm.extract_keytab(realm.user_princ, realm.client_keytab);
+realm.run([kinit, '-k', '-i'])
+realm.klist(realm.user_princ)
+realm.run([kdestroy])
 realm.kinit(realm.user_princ, flags=['-k', '-i'])
 realm.klist(realm.user_princ)
 out = realm.run([klist, '-k', '-i'])


More information about the cvs-krb5 mailing list