I've made contact with Iain, the developer of NSSM and he's looking into this. You may want to watch his git repo for updates.
Thanks,
Chris
On 18 Jul 2017 16:52, "Chris Rowson" <christopherrowson at gmail.com> wrote:
Ah - the repo I checked did not belong to the author - Somebody had forked it. That'll be why it doesn't look active --> https://github.com/ kirillkovalenko/nssm
I have emailed the author referenced in the commit above.
Thanks,
Chris
On Tue, Jul 18, 2017 at 4:40 PM, Alessandro Tinivelli < Alessandro.Tinivelli at faacgroup.com> wrote:
Hi Chris,
as we all know, almost all of the code in the world has potential security issues. When someone finds a flaw, the best idea is to notify privately the author(s) of the code itself, so he(they) can take appropriate countermeasures as soon as possible.
NSSM is actively maintained as you can see here https://git.nssm.cc/?p=nssm.git
If you click on any of the commit you can see author's email address. He says "To report a bug, use my email address from any of the commits..." ( https://nssm.cc/bugs). Please do this giving the more details possible, so he can enhance the security of the code.
Thank you very much Alessandro
Xymon mailing list Xymon at xymon.com http://lists.xymon.com/mailman/listinfo/xymon