Re: krb5 mechanism OID; Was: Re: FW: memory leak in some KerberosAPIs?

[Love <lha@stacken.kth.se>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Love <lha@stacken.kth.se> writes:

> Buck Huppmann <buckh@pobox.com> writes:
>
>>> For the first problem, can you try this ?
>>
>> don't you also need one here?
>
> Yes, you are right. I've just test compiled this. I'm traving so I'll test
> and commit this later.

So, I've done some testing and it seem to work (need to verify that it
doesn't leak memory still), next generate snapshot (each monday unless
Johan make it happen more often) will contain the changes.

Love

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (NetBSD)

iQIVAwUBPu6U7RZyDLTSep3UAQIdlQ//VDi9QpqOQGDLb8GISLkYnb9GfODpVtja
F5LrpJ7Wa1zysueee1ddPrW4mQFTtbD6rm27wKOWemwYdfYPiHkoZYI+OsxqAsP5
fDYF1Hszr/FW6ujZAk6qvy8IGM7+YPwRWGv15QWYenlrphq1+/r7p20OiANavsXg
nxMsMgHb+RwWdvX36GdVgEoxSiZFM4Q/jNWpF13cLM/fC1XhmoEMZjArkTUY/blg
ZHPfoA/js+fYJQGKn4x18CIvRY9AWGK4+AgAQSaOqycsrKosE/ceT3lNyTdLOc9j
uXLPkBNu6L1CFon3/c0jks9Sqdt8yfEhhZ2MoVFDtkDKvYpO8rO0jnDvCLNK1Cfw
LdsUMYEKRBewLtqnzh9u/tgBMbGll3z5WsCh2sQ3SvonidFSF+rYvjPyssf2AAVD
Mnb+VIyGPLj6RCsktwpx4qX+cwfzVoEmoordFZpwtx5l8qW+snSg7KTuiFjwfxme
UDaAcLkN1URaGG5jTwCMmO0JocY2zdMfIZvZnUHFkOVtxYT+Rn6I+LlAo6Q0xs8L
1uMVBH6rv5Ix1MB4lEBVwrAEWqkN9IR3g1WYFysStaYI09Crm8WYj1uXZbULIGEw
B78/tBUtuZjNcdMeVAq2apsdsWA9eJ7gl/0ioo9MfaYAs5hn7Pn5BYyJZtljcM3h
ikjKDBlr1aA=
=EYXY
-----END PGP SIGNATURE-----