3 ms·
I don't think it's necessarily this easy. While I would say "yes" to the question, I already know that if I write a piece of crypto software, it will be used by
by bluejekyll 10y ago
I don't think it's necessarily this easy. While I would say "yes" to the question, I already know that if I write a piece of crypto software, it will be used by bad players to hide their illicit activities, including governments hiding what they are doing to their population.
Similarly, almost all open-source software can be used by these bad actors. I doubt any of them write their router OSes, e.g. FreeBSD, but should I not contribute to that code because I know they are using it to suppress or track voices inside their country? Similar arguments for DNS or other tools that can be used to snoop on citizens.
Now, I would sign something saying I would not take a contract or money from them, but at the same time I think the US/EU sanctions actually already require that.
So how would we design it with these obvious caveats?