Ask HN: How to communicate security issues to the community of software project
Some project recently had an issue that let remote, unauthenticated users read any file from the server it ran on as long as user permissions did not interfere.<p>The fix to that issue was implemented in a reasonable time frame but the release was not specially advertised. Instead the mention was inside the body of a generic &quot;softwareproject Version 1.2.3 released&quot; post.<p>When I posted some pretty angry comments about this, I was met with a mixture of understandable personal defense (&quot;we do this in our free time, don&#x27;t be so negative&quot;) and ignorance (&quot;the users should take care about sandboxing and permissions themselves&quot;).<p>The software is widely deployed on government systems and companies all over the world. Randomly sampling Google results gave me more vulnerable servers than not.<p>I feel that the project misses the severity of this issue and neglects the security of its users. I want to make sure they understand this and how to prevent similar problems in communication in the future.<p>Looking around for some best practices on this, I came up blank.<p>How could the project have communicated the issue better? What are the commonly exercised best practices. Are there industry standards?<p>Thanks!