> I don't think this is very well reasoned or rational. That’s correct, and that’s why I won’t touch the code: because users *aren’t* rational.
The Peace Corps and the CIA have a mutual understanding: if you’ve ever in your life worked for one, you’re forever barred from working for the other. They do this so the Peace Corps can be trusted to be purely humanitarian and have no ties to US intelligence. This rule has been in place for 25 years or more, and *still* Peace Corps volunteers get accused regularly of working for US intelligence. I’ve had people email me accusations of being an FBI mole and even send me death threats for having some government affiliations and being active in the community. I’m not kidding. You can see one example at http://sixdemonbag.org/threat.xhtml . There have been several others over the years. Users *aren’t* rational, and there’s a very vocal segment of the community that screams bloody murder and conspiracy at every opportunity. For that reason, I don’t touch the code. > I'm convinced it's harder to implement backdoors and vulnerabilities in > code, if it has less lines, is clean and well-documented. This is likely true, but... > Why that's the case? I just looked at the code for some minutes, and I > wanted to know, what happens before sending an email, and what happens > after sending an encrypted and signed email. I didn't spend much time, > but not chance for me. I'm not a code reviewer. I wouldn't know, where > to begin, to study Enigmail. … this makes me doubt your qualifications to make such a statement.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ enigmail-users mailing list enigmail-users@enigmail.net To unsubscribe or make changes to your subscription click here: https://admin.hostpoint.ch/mailman/listinfo/enigmail-users_enigmail.net