Should Privacy Guides require open-source, source-first or source-available as a criteria for all tools?

Meh, I see FUTO as a middle ground between privacy and proprietary in favor of protecting company assets.

what the hell is all this fuss about, of course open source is a PREREQUISITE to achieve privacy. IT is the most fundamental opsec requirement for privacy.

On the clientside at least, you need transparency to be able to know what your software is doing (hence the FOSS requirement), and ONLY THEN are you able to know if it is spying on you or not, and if after reading the code you see that it doesnt spy on you, then it won’t.

Transparency (FOSS) is a requirement for Privacy. I am kind of shocked to see that people don’t seem to get that even here.

Should Privacy Guides require FOSS as a criteria for all tools ?

I wouldn’t call them privacy guides if that weren’t the case. It is a total no-brainer Yes 100% of course.

http://blog.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/opsec/opsec4levels/index.html
http://blog.nowherejezfoltodf4jiyl6r56jnzintap5vyjlia7fkirfsnfizflqd.onion/opsec/closedsource/index.html

1 Like