0x914409F1

>The problem is not the tool, it is how you use the tool. @alonbl This logic doesn't apply to every tool ever invented. For example: the square wheel. CMake's bugs,...

Note: that's only for miniupnpc. I haven't scanned the other paths.

I currently run automated builds for https://github.com/monero-project/monero and https://gitlab.com/kovri-project/kovri. I could easily add miniupnp to the list of my builds after I add miniupnp to my coverity dashboard. You would...

Note: the automated builds would be against the master branch every N days (around 2 to 3 days).

@cmaves In the future, please respect [responsible disclosure](https://en.wikipedia.org/wiki/Responsible_disclosure) by using using Monero's [Vulnerability Response Process](https://github.com/monero-project/meta/blob/master/VULNERABILITY_RESPONSE_PROCESS.md) regardless of whether this issue is a confirmed vulnerability or not. Thank you.

Does [this list](https://github.com/monero-project/meta/issues/62#issuecomment-313512337) still apply? If so, should we PR the list for easy reference?

Opened https://github.com/monero-project/meta/issues/119.

Great guide, really :+1: Would you consider adding a link to the VRP in the section *Report vulnerabilities responsibly*? https://github.com/monero-project/meta/blob/master/VULNERABILITY_RESPONSE_PROCESS.md It also covers MRL, as does the bounty.

>Self-assembling workgroups have every right to be as open or as closed as they want to be, and I don’t see value in trying to force my idea of how...

@rehrar You've completed side-stepped addressing the issue of project centralization while reiterating what I've already said. What a waste of time to read. >There was indeed a bug with Taiga...