Bug#311977: libkrb53: gss_init_sec_context sometimes fails to initialise output_token

2005-07-18 Thread Russ Allbery
Sergio Gelato [EMAIL PROTECTED] writes: Russ Allbery wrote: It looks like this only fails when gss_init_sec_context returns an error, and RFC 2744 isn't entirely clear on whether the output token is supposed to be initialized in that case, but I can certainly see the convenience argument for

Bug#311977: libkrb53: gss_init_sec_context sometimes fails to initialise output_token

2005-07-12 Thread Sergio Gelato
Russ Allbery wrote: It looks like this only fails when gss_init_sec_context returns an error, and RFC 2744 isn't entirely clear on whether the output token is supposed to be initialized in that case, but I can certainly see the convenience argument for doing so. I find the example code in RFC

Bug#311977: libkrb53: gss_init_sec_context sometimes fails to initialise output_token

2005-07-10 Thread Russ Allbery
Sergio Gelato [EMAIL PROTECTED] writes: Package: libkrb53 Version: 1.3.6-2 In investigating a suspicious free(): invalid pointer message from ssh-krb5 3.8.1p1-7 I discovered that gss_init_sec_context() doesn't always initialise output_token (setting output_token-length=0 would be enough)