"some versions of perl's garbage collector are buggy and leak memory" about jobflow

[rofl0r]

you're quite obsessed with that memleak stuff, huh ?
i reckon it's something that regularly comes up on your mailing list...
i guess i could just remove the line if that makes you happy (i don't think i'm willing to invest hours to find a perl version that leaks memory under specific circumstances)

[ole-tange]

"you're quite obsessed with that memleak stuff, huh ?"

Not really. Memleak detection has been part of the automated testing for quite a while, so it is unlikely to show up again for normal usage.

I am, however, puzzled why you continue to include such a claim with no evidence.

It would be akin to someone writing about jobflow:

"jobflow is written in C. Many programs written in C are vulnerable to buffer overflows. These are often used for getting unauthorized access to systems."

While all of this is technically true, it gives the impression that there are many known buffer overflow errors in jobflow, and that these pose a security risk. I would find that misleading if there was no evidence to support that claim.

I have only found a single buffer overflow error in your code, and I do not think that error can be exploited by an attacker:

$ echo a | jobflow -exec echo {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {} {}
Segmentation fault (core dumped)

I hope you will find this report helpful and hope that you will either back up your claim with evidence or remove the claim.

[rofl0r]

good catch, thanks for your report.