Subj : Re: binkd error
To   : Tony Langdon
From : Dan Cross
Date : Thu Jan 30 2020 06:12 am

On 03 Jul 2019 at 02:40p, Tony Langdon pondered and said...
 
 TL> I've been running binkd fairly successfully for 2.5 years on this
 TL> system, and for the most part, it's been flawless.  However, on polling
 TL> one particular uplink, I've started getting a strange error, which is
 TL> not giving me a lot of clues.

I ran into this today.  The root cause is a use-after-free bug in
binkd; this bug has been present since sometime in 2001 according
to the git history.  Most people probably won't notice it unless
your system's malloc() is aggressive about poisoning memory returned
by free().

I've sent a pull request to fix it upstream.
https://github.com/pgul/binkd/pull/16

--- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)

.