Use ENCTYPE_NULL in the krb5_crypto_init() call.
authorGuy Harris <guy@alum.mit.edu>
Sat, 20 Dec 2014 01:56:17 +0000 (17:56 -0800)
committerGuy Harris <guy@alum.mit.edu>
Sat, 20 Dec 2014 01:57:03 +0000 (01:57 +0000)
commit2f44afef8017f8c3b85818488236b28702f56324
treee2f4986531f5bbfd970fb4d25cefde63c506a727
parent237695390988485f60a14c3624158b2a0f7a8297
Use ENCTYPE_NULL in the krb5_crypto_init() call.

That appears to be a name supplied both by MIT and Heimdal Kerberos.
Using it makes it a bit clearer what the code is doing, and might avoid
type clash warnings if it's the right type (e.g., if it's a member of an
enum, as it is in Heimdal, and the corresponding argument to
krb5_crypto_init() is of the same type, the types will match).

Change-Id: I81b79223f789b8d1ec47180b7636ac1d83e03681
Reviewed-on: https://code.wireshark.org/review/5898
Reviewed-by: Guy Harris <guy@alum.mit.edu>
asn1/kerberos/packet-kerberos-template.c
epan/dissectors/packet-kerberos.c