s3:gse: MIT krb5 1.8.1 has a bug in gss_wrap_iov()

gss_krb5int_make_seal_token_v3_iov() doesn't set '*conf_state'.

metze

diff --git a/source3/librpc/crypto/gse.c b/source3/librpc/crypto/gse.c
index c7dfc399380537fddf7dd60d3aa4a47798cbcdb2..9eaef5aa44d4cc6db8070a6490ba769c80e1a837 100644 (file)
--- a/source3/librpc/crypto/gse.c
+++ b/source3/librpc/crypto/gse.c
@@ -782,7 +782,7 @@ NTSTATUS gse_seal(TALLOC_CTX *mem_ctx, struct gse_context *gse_ctx,
        OM_uint32 gss_min, gss_maj;
        gss_iov_buffer_desc iov[2];
        int req_seal = 1; /* setting to 1 means we request sign+seal */
-       int sealed;
+       int sealed = 1;
        NTSTATUS status;
 
        /* allocate the memory ourselves so we do not need to talloc_memdup */