Subject: | krb5 apps in source tree should not use deprecated API |
Applications that are distributed in the source tree should not use the
deprecated API. People should be able to look at the code as examples
of what and not to do.
There are four apps:
kprop: Uses krb5_get_in_tkt_with_keytab, krb5_auth_con_initivector
ksu: Uses âkrb5_get_in_tkt_with_password
kdc5_hammer: krb5_get_in_tkt_with_password
lib/kadm5/unit-test/setkey-test: krb5_get_in_tkt_with_keytab
In addition, internal library code uses the deprecated code:
krb5_build_principal_alloc_va depends on deprecated
krb5_build_principal_va (trivial fix - use the krb5int version)
krb_get_in_tkt_with_skey uses krb5_get_in_tkt and
krb5_get_in_tkt_with_keytab
deprecated API. People should be able to look at the code as examples
of what and not to do.
There are four apps:
kprop: Uses krb5_get_in_tkt_with_keytab, krb5_auth_con_initivector
ksu: Uses âkrb5_get_in_tkt_with_password
kdc5_hammer: krb5_get_in_tkt_with_password
lib/kadm5/unit-test/setkey-test: krb5_get_in_tkt_with_keytab
In addition, internal library code uses the deprecated code:
krb5_build_principal_alloc_va depends on deprecated
krb5_build_principal_va (trivial fix - use the krb5int version)
krb_get_in_tkt_with_skey uses krb5_get_in_tkt and
krb5_get_in_tkt_with_keytab