Use gssalloc memory management where appropriate
authorSam Hartman <hartmans@mit.edu>
Fri, 14 Oct 2011 14:40:10 +0000 (14:40 +0000)
committerSam Hartman <hartmans@mit.edu>
Fri, 14 Oct 2011 14:40:10 +0000 (14:40 +0000)
commit800358b1790ef82710af0b6021c6ff2dca2b0de7
tree49f106379347bdf032708c5f8f13b6820ca220d3
parent3ab619b8ffa9337498e49caa8e75f6e03a56e71c
Use gssalloc memory management where appropriate

gss_buffer_t may be freed in a different module from where they
are allocated so it is not safe to use strdup/malloc/calloc/free.
similarly, gss_OID_set need to use gssalloc functions.

Signed-off-by: Kevin Wasserman <kevin.wasserman@painless-security.com>
git-svn-id: svn://anonsvn.mit.edu/krb5/trunk@25332 dc483132-0cff-0310-8789-dd5450dbe970
17 files changed:
src/appl/gss-sample/gss-server.c
src/lib/gssapi/generic/oid_ops.c
src/lib/gssapi/generic/rel_buffer.c
src/lib/gssapi/generic/rel_oid_set.c
src/lib/gssapi/generic/util_buffer.c
src/lib/gssapi/krb5/accept_sec_context.c
src/lib/gssapi/krb5/gssapi_krb5.c
src/lib/gssapi/krb5/init_sec_context.c
src/lib/gssapi/krb5/k5seal.c
src/lib/gssapi/krb5/k5sealv3.c
src/lib/gssapi/krb5/k5unseal.c
src/lib/gssapi/krb5/util_crypt.c
src/lib/gssapi/mechglue/g_dsp_status.c
src/lib/gssapi/mechglue/g_glue.c
src/lib/gssapi/mechglue/g_rel_buffer.c
src/lib/gssapi/mechglue/g_rel_name.c
src/lib/gssapi/mechglue/g_wrap_aead.c