4 ms·
I don't think the advice not to implement your own crypto stuff ever meant that no one should do it under any circumstances. It means that application programme
by fauigerzigerk 13y ago
I don't think the advice not to implement your own crypto stuff ever meant that no one should do it under any circumstances. It means that application programmers should not do it as part of their application. And that, I think, is good advice.
I certainly wouldn't want to see corporate devs at my bank implement some custom "secure" http communications protocol.
What we need is two or three well funded TLS/SSL implementations competing with each other, kind of like we have a handful of competing web browser implementations or C++ compiler implementations or operating systems, all done by experts in their field.
- StavrosK 13y agoIsn't PolarSSL like that? Maybe pure open source isn't a good fit for critical applications.
- fauigerzigerk 13y agoWhat is "pure opensource"? It's hard to imagine a credible closed source implementation in the age of NSA ubiquity. I don't know PolarSSL. If it's a reasonably complete implementation then maybe it deserves more attention.
- StavrosK 13y agoIsn't PolarSSL like that? Maybe pure open source isn't a good fit for critical applications.