[20188] in Kerberos_V5_Development
Re: Assertion failure due to repeated K5_KEY_GSS_SPNEGO_STATUS
daemon@ATHENA.MIT.EDU (Greg Hudson)
Thu Oct 15 18:55:57 2020
To: Adam Dabrowski <adabrowski@nomachine.com>, <krbdev@mit.edu>
From: Greg Hudson <ghudson@mit.edu>
Message-ID: <b632f154-b76c-1c3d-779f-ed263e010ee3@mit.edu>
Date: Thu, 15 Oct 2020 18:55:45 -0400
MIME-Version: 1.0
In-Reply-To: <2e40edd7-1774-2ba2-ee8d-aef68658177b@nomachine.com>
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On 10/15/20 5:49 PM, Adam Dabrowski wrote:
> 1. Libgssapi_krb.so.2.2 is loaded dynamically with dlopen.
> 2. Call to gss_init_sec_context - library initialization, first
> registration of K5_KEY_GSS_SPNEGO_STATUS.
> 3. libgssapi_krb.so.2.2 is unloaded, however libkrb5support stays in the
> process memory.
> 4. Steps 1., 2..
> 5. Abort due to failed assertion 'destructors_set[keynum] == 0' in
> k5_key_register.
If you edit gss_spnegoint_lib_fini() and add:
k5_key_delete(K5_KEY_GSS_SPNEGO_STATUS);
does the problem go away? I think this was neglected in commit
d160bc733a3dbeb6d84f4e175234ff18738d9f66 .
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
