Comment by fractorial
2 days ago
Irrespective of opinions about a project or its authors, disclosing a potential security issue in a public forum is markedly not responsible disclosure.
2 days ago
Irrespective of opinions about a project or its authors, disclosing a potential security issue in a public forum is markedly not responsible disclosure.
> Irrespective of opinions about a project or its authors, disclosing a potential security issue in a public forum is markedly not responsible disclosure
Lol, what you wanted me to do instead, email the author and do the entire chain for a issue I found from 30 seconds of skimming the code? We're on a open forum talking about before-alpha software people share with the community to get feedback, I'm expecting this is exactly what the author wants, that's why they're here in the first place.
Besides, personally I file myself in the category of people not being very responsible folks in general, so I guess thanks? I'd still disagree "responsible disclosure" even applies here.
Thank you for taking the time to inspect this so carefully. You were right, and I treated it as an urgent security issue. The updated version fixed the mentioned problem. All macOS, Windows, and Linux packages have been rebuilt.
I also agree with your broader product criticism. If you are still willing to try the patched release, I would genuinely value both a security re-check and your thoughts on what the smallest useful editor integration should look like. Thank you again for catching this before more people installed it.