Import names immediately with COMPOSITE_EXPORT RFC 6680 specifies that GSS_Export_name_composite() "outputs a token that "can be imported with GSS_Import_name(), using GSS_C_NT_COMPOSITE_EXPORT as the name type...". Therefore, in the gss_import_name mechglue, we should perform the import process imediately when either GSS_C_NT_COMPOSITE_EXPORT or GSS_C_NT_EXPORT_NAME are used (not just for the later, as is the current functionality). The naming extension test was also updated to display the result of importing with GSS_C_NT_COMPOSITE_EXPORT in addition to GSS_C_NT_EXPORT_NAME. [ghudson@mit.edu: minor style changes] (cherry picked from commit 29dec110c43ae9cebdcd935906a3131ca9ac0c99) (cherry picked from commit f2302383dd3a32bf22f437c4e1d10533323db5dc) https://github.com/krb5/krb5/commit/9c2a5dd4dc2122e5e43cdc49069184f5c3dc7d95 Author: Solly Ross Committer: Tom Yu Commit: 9c2a5dd4dc2122e5e43cdc49069184f5c3dc7d95 Branch: krb5-1.12 src/lib/gssapi/mechglue/g_imp_name.c | 15 ++++++++------- src/tests/gssapi/t_export_name.c | 17 ++++++++++++++--- src/tests/gssapi/t_gssapi.py | 5 +++++ src/tests/gssapi/t_namingexts.c | 24 ++++++++++++++++++++++++ 4 files changed, 51 insertions(+), 10 deletions(-)