9 ms·
I think the "good feeling" is supposed to be about their cryptographic experience and expertise. The second point about trust doesn't directly flow from the pr
by derefr 11y ago
I think the "good feeling" is supposed to be about their cryptographic experience and expertise.
The second point about trust doesn't directly flow from the previous sentence (which would make it sound like he's saying something like "I trust this person sight-unseen"); instead, he's just meaning that cryptography (like any technology) ultimately requires you to trust someone at some point, because you can't audit every line of every piece of software and firmware you're sitting on top of.
And because of that, while there can be a point where you know "enough" about a particular codebase's architecture and management to have faith in its stewardship (or enough to not have faith in said stewardship—OpenSSL, for example), you can't really ever know everything there is to know about a codebase now-and-forevermore such that you no longer have to trust anyone about anything.
- jkyle 11y agoSomewhat. But that's a pretty thin link of trust. People change jobs and I doubt the people he knows personally know every line of code either. In the end, he's trusting MS the company as a whole. Generally when I 'trust' open source, it's not a specific person I'm trusting. More so, I "trust" that given the millions of programmers in the world that will look at this code there will be one with similar interests to me that will catch any nefarious bits that slip in. I think these two kinds of trust are categorically different. One providing much more permanence than the other.