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

-=> On 01-30-20 06:12, Dan Cross wrote to Tony Langdon <=-

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

Ahh, OK.  Good find by the looks of it.  

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

Hopefully I can get hold of the fixed source.  I've had to take a number of
measures like restricting callouts to the affected node to IPv4 only, and also
hardcoding the IPv4 IP in the node entry, because DNS lookups were also
problematic for the affected node..

A second link running over ZeroTier started showing similar issues recently,
but switching that link to connect directly across the open Internet was enough
to get that link working.

It's odd that it only affects some links.  

My system is a fairly busy Pi that's running 2 BBSs, which may explain why
malloc() is being a bit aggressive. :)


.... Cut my pizza into six pieces please.  I can't eat eight.
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
 * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

.