Josip Rodin wrote:
>> To avoid a memory leak, the pointers should be initialized before they
>> are used. I've committed a change to the v2.1.x branch which fixes this.
>
> This didn't seem to end up in 2.1.12, why is that?
2.1.12 came out before the patch was done. The patch went in on
Nov
On Mon, Nov 28, 2011 at 01:48:18PM +0100, Alan T DeKok wrote:
> Josip Rodin wrote:
> > That just doesn't seem safe enough when an analogous bit of parsing code in
> > cf_section_parse() does:
> ..
> > and cf_item_parse() can fail, so it stands to reason that *data can
> > remain unwritten, and shou
Josip Rodin wrote:
> That just doesn't seem safe enough when an analogous bit of parsing code in
> cf_section_parse() does:
..
> and cf_item_parse() can fail, so it stands to reason that *data can
> remain unwritten, and should not be free()'d.
The solution is to write to data. The reason is th
On Thu, Dec 09, 2010 at 11:59:07AM +0100, Ralf Hildebrandt wrote:
> Package: freeradius
> Version: 2.1.10+dfsg-2
> Severity: normal
>
> >>From our log:
>
> ...
> Dec 9 11:46:08 dns-cbf freeradius[5716]: Login OK: [00-1A-4B-28-BD-76] (from
> client 10.43.24.10 port 31016 cli 00-1A-4B-28-BD-76)
>
Package: freeradius
Version: 2.1.10+dfsg-2
Severity: normal
>From our log:
...
Dec 9 11:46:08 dns-cbf freeradius[5716]: Login OK: [00-1A-4B-28-BD-76] (from
client 10.43.24.10 port 31016 cli 00-1A-4B-28-BD-76)
Dec 9 11:46:11 dns-cbf logger: /usr/local/scripts/updateradiususers :
reloading fre
5 matches
Mail list logo
