Skip Menu |
 

From: tlyu@mit.edu
Subject: CVS Commit
* init_sec_context.c (krb5_gss_init_sec_context): Free
default_enctypes to avoid leaking returned value from
krb5_get_tgs_ktypes.

* k5unseal.c (kg_unseal_v1): Explicitly set token.value to NULL if
token.length == 0, to avoid spurious uninitialized memory
references when calling memcpy() with a zero length.


To generate a diff of this commit:



cvs diff -r1.222 -r1.223 krb5/src/lib/gssapi/krb5/ChangeLog
cvs diff -r1.69 -r1.70 krb5/src/lib/gssapi/krb5/init_sec_context.c
cvs diff -r1.28 -r1.29 krb5/src/lib/gssapi/krb5/k5unseal.c
From: tlyu@mit.edu
Subject: CVS Commit
pullup from trunk


To generate a diff of this commit:



cvs diff -r1.218.2.4 -r1.218.2.5 krb5/src/lib/gssapi/krb5/ChangeLog
cvs diff -r1.66.2.3 -r1.66.2.4
krb5/src/lib/gssapi/krb5/init_sec_context.c
cvs diff -r1.28 -r1.28.2.1 krb5/src/lib/gssapi/krb5/k5unseal.c
From: Kent_Wu@trendmicro.com
Subject: RE: [krbdev.mit.edu #1604] CVS Commit
Date: Mon, 16 Jun 2003 10:55:48 -0700
To: <rt-comment@krbdev.mit.edu>
RT-Send-Cc:
Tom:

Thx for the update. Do you mean you've fixed all the latest three memory leak problems including the one you said you wouldn't give it a high priority? And when will you guys put up a new Beta in the web?

Thx.

Kent

Show quoted text
-----Original Message-----
From: Tom Yu via RT [mailto:rt-comment@krbdev.mit.edu]
Sent: Friday, June 13, 2003 5:09 PM
Cc: Kent Wu (RD-US); krb5-prs@mit.edu
Subject: [krbdev.mit.edu #1604] CVS Commit


pullup from trunk


To generate a diff of this commit:



cvs diff -r1.218.2.4 -r1.218.2.5 krb5/src/lib/gssapi/krb5/ChangeLog
cvs diff -r1.66.2.3 -r1.66.2.4
krb5/src/lib/gssapi/krb5/init_sec_context.c
cvs diff -r1.28 -r1.28.2.1 krb5/src/lib/gssapi/krb5/k5unseal.c
To: rt@krbdev.mit.edu
Subject: Re: [krbdev.mit.edu #1604] CVS Commit
From: Tom Yu <tlyu@mit.edu>
Date: Tue, 17 Jun 2003 02:50:03 -0400
RT-Send-Cc:
Show quoted text
>>>>> "Kent" == Kent Wu@trendmicro com via RT <rt-comment@krbdev.mit.edu> writes:

Show quoted text
Kent> Thx for the update. Do you mean you've fixed all the latest
Kent> three memory leak problems including the one you said you
Kent> wouldn't give it a high priority? And when will you guys put
Kent> up a new Beta in the web?

It turns out that it wasn't too difficult to track down the ktypes
leak, which is this ticket [#1604]. I'll reply to the other issues in
the other ticket.

---Tom