Conversation

Replying to
Starting some misinformation / harassment campaign against me because you're upset about the technical analysis that I publish is not going to stop me from publishing it. You'll just convince me to start publishing a lot more and not keeping it within the GrapheneOS community.
1
7
Content in the GrapheneOS usage guide / FAQ is written to concisely answer questions asked over and over in a standard place. If I'm going to get such a hassle over a small (and accurate) paragraph, how pissed will you be if I start making a series of blog posts about the topics?
1
6
Maybe stop wasting so much of my time and energy spreading misinformation and character assassinations. It is not going to silence me. I've already started posting more about the topics. It's only going to force me to start writing extensively about it and pissing you off more.
1
7
There's a massive amount of work that could be turned into many blog posts about privacy and security topics, including lots of the code written for analysis / testing. If the tiny amount I publish as part of giving concise advice bothers you, don't motivate doing it beyond that.
1
3
Also, projects hostile to security researchers including myself lose the benefit of getting bug reports / disclosure. We regularly report problems upstream, but not to projects treating us badly. I've spent years sitting on bugs and proof of concepts for Mozilla projects already.
1
3
I don't care about the bug bounty money that's given up by sitting on them. If you treat myself or other researchers badly, I'm not going to work with you. Sitting on them is neutral, and not actively helping is not a good enough response to the kind of thing that's happening.
4