Subj : Re: binkd error
To   : Dan Cross
From : Tony Langdon
Date : Thu Jan 30 2020 09:17 pm

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

 DC> With luck, the upstream maintainer will address the pull request
 DC> quickly, either by applying my patches or coming up with another fix.
 DC> If you need this quickly, however, you could clone my fork
 DC> (https://github.com/fat-dragon/binkd.git) and build from source.

Building from source is not an issue, mine is built from source anyway. :)

 DC> The code path with the use-after-free was dependent on the source of
 DC> the information.  If you used the default port, the pointer in question
 DC> would end up pointing to memory that wasn't free()'d; if you used a
 DC> non-standard port in your configuration file (e.g.,
 DC> `agency.bbs.bz:24556`), you'd tickle the bug; hence why it doesn't show
 DC> up everyhwere.

Interesting, and the FSX hub does use a non standard port, from memory. 
Reducing path latency to a minimum seems to help.

 DC> Rather the aggressiveness I mentioned with respect to free()'d memory
 DC> has to do with the malloc() implementation writing garbage into the
 DC> free()'d region of memory, precisely to detect these sorts of
 DC> use-after-free issues.

That, I don't know. :)


.... Back Up My Hard Drive? I Can't Find The Reverse Switch!
=== MultiMail/Win v0.51
--- SBBSecho 3.10-Linux
 * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

.