From: Kent_Wu@trendmicro.com
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Subject: RE: [krbdev.mit.edu #1656]
Date: Thu, 10 Jul 2003 15:52:22 -0700
Message-Id: <7DE4EF03D8D61B44B927E4A059B2644C017B0356@65-200-113-18.trendmicro.com>
Thread-Topic: [krbdev.mit.edu #1656]
Thread-Index: AcNHFhpLidSyGNfaS62XJZ9fMhG8kwAH6fgA
To: <rt-comment@krbdev.mit.edu>
Content-Transfer-Encoding: 8bit
RT-Send-Cc: 
Content-Length: 1240

Yes, Tom. I do pass GSS_C_NO_CREDENTIAL to gss_init_sec_context(). This leak happens when I didn't get the TGT beforehand. Got a handle on this one yet?

Kent

-----Original Message-----
From: Tom Yu via RT [mailto:rt-comment@krbdev.mit.edu]
Sent: Thursday, July 10, 2003 12:05 PM
To: Kent Wu (RD-US)
Cc: krb5-prs@mit.edu
Subject: Re: [krbdev.mit.edu #1656]


>>>>> "Kent" == Kent Wu@trendmicro com via RT <rt-comment@krbdev.mit.edu> writes:

Kent> Not sure what you meant but I'm following up with #1601.

Kent> Kent

Kent> -----Original Message-----
Kent> From: rt@krbdev.mit.edu [mailto:rt@krbdev.mit.edu]
Kent> Sent: Wednesday, July 09, 2003 1:39 PM
Kent> To: Kent Wu (RD-US)
Kent> Subject: No ticket id specified


Kent> comment aliases require a TicketId to work on

This means that you sent to rt-comment@krbdev.mit.edu without a valid
ticket ID in the "Subject:" header.  Sending to rt-krb5@krbdev.mit.edu
would have opened a new ticket.  It's probably correct to open a new
ticket for this, though, as it is a new issue.  It is important to
retain the ticket ID string (in this case, [krbdev.mit.edu #1656] ) in
the subject to avoid confusing RT.

Anyway, are you passing in GSS_C_NO_CREDENTIAL to
gss_init_sec_context()?

---Tom