News for hackers. Stuff that matters.
Re:Be wary of one-time pads and other crypto unicorns by diminoten on Thursday March 26, 2015 @07:18AM (#9268809)
It ends up being a product of the fact that the smartest crypto folks aren't software developers, and the smartest software developers (or the most innovative -- the guys starting companies or building products) aren't crypto folks.

So you have a bunch of what are effectively scientists who aren't all that familiar with how products get made (first build something, release it, then refine it over time through feedback) and you have a bunch of developers who aren't familiar with how security products are managed (you don't release anything until you're willing to put people's lives on your product).

What you're left with is an ecosystem of developers releasing code that's not cryptographically sound because they need feedback and a community to help them refine the software, and crypto scientists who scream bloody murder every time they find a bug because, "what if the next Snowden uses your new tool!?!"

Everyone's right in this argument, it's just hard to bridge the gap between these two very different schools of thought.

Re:Be wary of one-time pads and other crypto unicorns by tptacek on Thursday March 26, 2015 @11:23AM (#9270278)
Snowden and Greenwald actually used one of the most popular of those tools, as you know, and according to the person who did the most conclusive, reputable, and devastating security analysis of that tool, they used it during a time when it was catastrophically broken.

The clear message you are trying to communicate is that the security community hyperventilates over security problems to the detriment of the community. That's not what happens. Look at Lavabit --- another example: the problem with serverside encrypted Internet email was absolutely written off as hyperventilation, to the detriment of every single Lavabit user, whose communications were almost certainly recorded and are, as a result of the way Lavabit handled a request for Snowden's communications, retroactively decrypted.

Re:Be wary of one-time pads and other crypto unicorns by diminoten on Thursday March 26, 2015 @12:01PM (#9270591)
Since our prior conversations, I've softened on my stance and at this point I think it's mostly just a UX issue. I don't think you or any other expert is wrong in being as... "hyper" about the problems in current software. I just think "your" (as the stand-in for crypto experts everywhere) solutions are, while strong, not the best UX, and I consider UX to be a critical part of security -- if people won't use it, then it's not good.

All I'm saying here is that there's a disconnect between security and usability that needs to be bridged, and sometimes one side forgets about the difficulty of correctly implementing the other.

Re:Be wary of one-time pads and other crypto unicorns by tptacek on Thursday March 26, 2015 @12:07PM (#9270655)
I'm sorry, but just to make sure I'm getting my point across, I'm going to restate it more simply:

Security people freak out at new amateur encryption tools because when they don't, those tools get adopted by hapless users who entrust real secrets with them. It's not a theoretical concern; it happens over and over again in the real world. It happened to Snowden twice, once with Cryptocat and once with Lavabit. In both instances, crypto experts begged people not to use those tools. In both instances, misguided privacy advocates pushed back on the crypto experts. The tools either didn't get fixed (because, in Lavabit's case, they couldn't be) or didn't get fixed in time. Almost certainly, NSA has decrypted intercepts as a result.

It's happening right now with other tools. It will, with certainty:100%, happen again with Cryptocat.

During the snake oil era of medicine, people used to take radium tonics as a cure-all. That's what these tools are: radium tonics.

Re:Be wary of one-time pads and other crypto unicorns by some_furry on Thursday March 26, 2015 @12:59PM (#9271154)
It doesn't help that Nadim seems to have stopped supporting Cryptocat to focus on Peer.io instead.
Re:Be wary of one-time pads and other crypto unicorns by diminoten on Thursday March 26, 2015 @12:38PM (#9270949)
That's not really what I'm talking about, though it is a manifestation.

"Don't use the tool" is a cryptographically sound piece of advice, given what you know about the specific implementation, but it's utterly useless for Cryptocat, from a product standpoint. What's a developer supposed to do when a crypto expert just says, "no"? That's terrible feedback, it needs to be better, and it can be better (sometimes it actually is better, I think you've mentioned in the past that you've lent a hand to Cryptocat).

As with every other "theory vs. practice" discussion, the theorists need to tone down the rhetoric, and the practitioners need to actually listen to what the theorists are saying.

Re:Be wary of one-time pads and other crypto unicorns by tptacek on Thursday March 26, 2015 @12:49PM (#9271041)
To be clear: I've never done anything to help Cryptocat, nor will I.

The right thing to happen with Cryptocat is for it to be scrapped. Its security issues pervade beyond bad cryptography. Its users are literally better off with Google Hangouts or iMessage.

And, in fact, the same was true of Lavabit: there was no recommendation that would allow a mail service that worked (for users) the same way Google Mail to resist serious attacks. But that was the premise of the system! It needed to be scrapped.

Re:Be wary of one-time pads and other crypto unicorns by diminoten on Thursday March 26, 2015 @01:10PM (#9271257)
And this is the nonuseful advice that the crypto experts need to stop giving. Joe Developer sees this advice and decides not to write crypto software.

That's unambiguously bad, because the software industry thrives on failing a lot until a good solution is found.

There needs to be a way to develop crypto software that falls in a land of, "Don't use this yet, but maybe someday after we're done testing it, you can start using it and be secure" rather than "nope, just scrap the whole thing".

Re:Be wary of one-time pads and other crypto unicorns by kasey_junk on Thursday March 26, 2015 @01:24PM (#9271415)
I am not a crypto expert and don't have a position wrt this particular problem domain but:

"the software industry thrives on failing a lot until a good solution is found"

may be at the heart of the disagreement. It is true that some parts of the software industry are best served by this style of iterative failure based progress, but it is unfair to say that the entirety of software is best developed this way.

There exist whole classes of problems where the failure modes of their solutions are quite simply worse than any potential value those solutions can provide. Those class of problems should NOT be iteratively developed, rather they should be rigorously engineered and formally verified.

I suspect your disagreement stems from whether you think crypto systems exist inside or outside that problem set.

Re:Be wary of one-time pads and other crypto unicorns by crpatino on Thursday March 26, 2015 @04:26PM (#9272835)
You are wrong on practically every account:

> Joe Developer sees this advice and decides not to write crypto software.

False. Moe Manager stomps his foot and makes Joe Developer wire together "something good enough", regardless of Joe's qualifications. Since neither Joe nor Moe are able to tell how good a crypto system is, they invariably end up with something in the awful-to-kludge spectrum. Both Moe and Joe need to be repeatedly reminded that they don't know enough about this non trivial problem to make good enough calls.

> That's unambiguously bad, because the software industry thrives on failing a lot until a good solution is found.

"Unambiguosly bad" is a thought stopper, a rhetoric trick. This just means that since you don't like any of the options made available to you by reality (like... paying big bucks to a real expert), self deception is preferable.

Now, the fact that our software industry thrives on failure... I am ashamed to say that this just means our industry is really good at externalizing the consequences of our own incompetence to the customers. This is all good and fun, until real lives are on the line. Crypto is one of those cases, so it is one of those lines you don't cross.

> There needs to be a way to develop crypto software that falls in a land of, "Don't use this yet, but maybe someday after we're done testing it, you can start using it and be secure" rather than "nope, just scrap the whole thing".

Are you familiar with the term "Security by Design"? It is one of those pesky realities I was talking about. It basically says that you cannot create a product giving no concern to security, sprinkle some crypto fairy dust on top of it, and magically turn it into a secure product. If you try to do that, you'll end up with a product with broken security.

Which is not all that bad in practice. There are lots of useful products that we all are better of having in insecure form than not having at all. But if the whole point of product X is to be "Y, but done securely" there is no redeeming feature that can save X from the axe.

Re:Be wary of one-time pads and other crypto unicorns by diminoten on Thursday March 26, 2015 @06:04PM (#9273450)
I'm not sure how to respond to this. On one hand you talk about "rhetorical show stoppers", and on the other hand you reply to a statement I've made with the one word sentence, "False.", and in another sentence you say I'm "wrong on practically every account".

I guess I could point out that there lies, in a continuum of software, a place for experimental products which offer nothing other than the exploration of an idea and the opportunity to refine said idea through testing and discussion. I could also point out that your strawman of "sprinkle some crypto fairy dust" is entirely irrelevant to this conversation, and that your lack of understanding of how threat actors are modeled is evident in your inability to comprehend a tool that might protect against certain threats but can acceptably not protect against all threats.

But I think those points would fall on the "ears" of someone who just wants to be combative. Maybe someone else will pick up where you left off and engage in a more honest and less antagonizing manner, but this deep in the comment tree, "here be dragons".

Re:Be wary of one-time pads and other crypto unicorns by crpatino on Friday March 27, 2015 @06:00PM (#9279307)
I guess am sorry that we ended up in bitter ends of a pointy discussion. For what's worth, I was not trolling. I stand by anything that I said (specially the "sprinkle of crypto fairy dust", which I have seen IRL more often that I wish). If I am ignorant or not, I am by definition unqualified to tell.

Other than that, if you prefer to have non combative discussions, please stop bossing professionals around and tell them what to do. Specially if they are not providing a service you paid money for.

Re:Be wary of one-time pads and other crypto unicorns by diminoten on Sunday March 29, 2015 @11:09AM (#9285067)
I am a professional and I "boss" other professionals around on this topic (admittedly, mostly other topics, but this specific one does come up) for a living.

But it's funny, because what you're saying here (don't "boss" people around) is similar to what I am saying, with regard to experimental crypto software. The crypto experts need to let the developers develop, and find a constructive way to contribute to that process, rather than chicken-little every time a bug appears.

Imagine software that comes out, stating: "This software is not meant to do anything other than hide your porn from your mother. Please do not use this software to do anything other than protect yourself against a threat who has limited understanding of computers and software."

As that software matures, the disclaimer could expand to, "This software is not meant to do anything other than protect information against low-level criminal activity. Please do not use this software to do anything other than to protect your information from larceny or identity theft. This software will not protect you against a sophisticated or well-resourced actor."

Eventually expanding to, "This software has been tested by a community of crypto experts. While there is currently no known reason why this software won't protect your information from all bad actors, there is no guarantee in place that your information is absolutely safe. Always exercise extreme caution when protecting your data from sophisticated actors."

The idea being that, once an experimental piece of software becomes "good enough", it can be used to protect against a more diverse threat model.

The idea that you have to ship an NSA-proof product on day 1 is completely unfeasible and will never happen, and the crypto scientists out there need to realize that.

Re:Be wary of one-time pads and other crypto unicorns by crpatino on Monday March 30, 2015 @12:54PM (#9290800)
You keep talking about bugs and therefore you keep missing the point. As a matter of fact, I tend to agree with you that the Infosec community would benefit enormously by adopting some of the best practices that we lowly programmers take for granted. There would arguably be less bug and less high-profile bugs that way.

What I am trying to point out is that you cannot fix a flawed Security Design by incremental improvements. I am not talking about individual coding defects or even desirable features that have been left temporarily unimplemented on purpose. I am talking about Stupid!Ideas that get implemented because there was nobody around that recognized them as such, and then the usual traits of human nature (denial, previous investment bias, rationalization, etc) prevents the incumbents from scrapping those ideas until insurmountable evidence is assembled.

The article in question talks about using One Time Pads (OTPs) to conceal secrets. This is an idea that sounds good, OTP is mathematically proven to be "unbreakable" and all that... The problem is when theory meets practice and nobody asks the hard question: How are sender and receiver going to share the OTP prior to sending the real message.

This is not a trivial question to ask, giving the fact that OTP must have the same amount of bits as the message it is protecting. You can also not "recycle" a single OTP for many messages (that would be a Many Time Pad, which by definition violates the very preconditions that make OTP secure).

So, you end up with the scheme used in spy movies (I have no idea how real spies worked during the Cold War). Each spy carries around a code-book of OTPs that he received in hand by a trusted contact. The fact of being in possession of such book is itself a proof of being a spy so he was to take great care to hide it, which is hard because it is a whole book (OTP, lots a lots of messages). Also, the spy agency will have the cumbersome work of providing a different code-book to each spy (because otherwise, when the enemy catches one spy, they could theoretically run the OTP on all previous communications from suspected spies and have each one of them rounded and shot before the word comes out that the first spy was in prison).

This example also serves to illustrate another point. Maybe a Bad!Idea can be made to work in a limited way, if need is dire and resources are plenty. But any organization which kept secrets of real importance and tried to rely on this kind of solution would end up eaten alive by any adversary that had heard the words "asymmetric cryptography" spoken together.

Re:Be wary of one-time pads and other crypto unicorns by diminoten on Tuesday March 31, 2015 @06:43PM (#9300407)
I'm trying to understand how you could possibly think I've been talking about "Bad!Idea" at all.

I really can't find in anything I've written where I talked about writing a "bad" piece of crypto software. In fact, I've been talking about a potentially "good" piece of crypto software that isn't getting written because no software is perfect, but that's what crypto experts are demanding out of the gate.

Can you more succinctly sum up what you're trying to say? Do you think software shouldn't be written in the crypto space unless it's perfect from v0.0.0? I can't imagine you think that, so I'm wondering what exactly it is you're arguing here.

Re:Be wary of one-time pads and other crypto unicorns by wglb on Thursday March 26, 2015 @02:09PM (#9271847)
Where software industry thrives on failing a lot until a good solution is found.

Except where it is important. Failing a lot in crypto can have deadly consequences that are not visible until it is too late.

Re:Be wary of one-time pads and other crypto unicorns by Nursie on Thursday March 26, 2015 @02:41PM (#9272131)
>> Joe Developer sees this advice and decides not to write crypto software.

He probably shouldn't. That's pretty much the point.

(--edit-- or he should consult with people who have studied this, find out about best practice, use existing solutions where possible, etc etc)

Re:Be wary of one-time pads and other crypto unicorns by diminoten on Thursday March 26, 2015 @06:07PM (#9273460)
Why must he? Why can't he build whatever he likes? Who are you to tell Joe what he can and can't do with regards to software development?

This is the problem -- you and others are trying to perpetuate the idea that software must always be "complete" the moment it's put on GitHub. Why must Joe Developer adhere to your rigorous definition of what a software product is?

Joe Developer should be free to tinker, and if he wants to tinker with crypto, crypto experts should let him. Currently they don't, and that's why we don't have any good crypto software.

Re:Be wary of one-time pads and other crypto unicorns by Nursie on Thursday March 26, 2015 @07:06PM (#9273751)
>> Joe Developer should be free to tinker, and if he wants to tinker with crypto, crypto experts should let him. Currently they don't, and that's why we don't have any good crypto software.

He can tinker.

He can learn.

He can do any of the many excellent free courses, tutorials and challenges on the net.

He can implement attacks against toy problems, and real problems.

And eventually, he can get deeper into implementing it.

What he will absolutely and rightly be shot down for is making unverifiable claims about the security or what he's tinkering with, and try to profit from his claims.

I'm sorry if you have a problem with that.

Re:Be wary of one-time pads and other crypto unicorns by diminoten on Thursday March 26, 2015 @07:39PM (#9273890)
When did he make unverifiable claims? When did he profit from his claims?

It's a nice straw man, but not what I suggested at all.

Re:Be wary of one-time pads and other crypto unicorns by Nursie on Thursday March 26, 2015 @09:20PM (#9274254)
>> When did he make unverifiable claims? When did he profit from his claims?

When he launched an app that claimed to be the new safest thing ever, surely? Perhaps with an unbreakable One-Time-Pad. You know, the stuff we're commenting on here...

Re:Be wary of one-time pads and other crypto unicorns by diminoten on Saturday March 28, 2015 @01:59PM (#9282187)
> You know, the stuff we're commenting on here...

Nope, not at all the stuff we're commenting on. We're commenting on the stuff that hasn't been written yet and probably won't be written at all because of your negative attitude.

Re:Be wary of one-time pads and other crypto unicorns by Nursie on Saturday March 28, 2015 @07:26PM (#9283189)
If it won't be written because people get shot down when they make outrageous claims about their security then I'm ok with that. Everyone should be.

I'm not sure what it is you want here. Nobody's telling you not to use it. Nobody's telling you not to tinker. Everyone's encouraging you to learn, and giving you advice on the best way of doing that. You seem to want every bad, amateurish attempt at novel crypto, accompanied by self aggrandising copy, to be hailed as if it was awesome. It's not.

Re:Be wary of one-time pads and other crypto unicorns by diminoten on Sunday March 29, 2015 @11:12AM (#9285073)
> If it won't be written because people get shot down when they make outrageous claims about their security then I'm ok with that. Everyone should be.

Again, you strawman me. Where in my argument did I talk about making outrageous claims? I would very much appreciate it if you separated "make outrageous claims" from "develop open source security software".

Re:Be wary of one-time pads and other crypto unicorns by Nursie on Sunday March 29, 2015 @06:46PM (#9286780)
>> Again, you strawman me. Where in my argument did I talk about making outrageous claims?

You appear to be annoyed that folks write take-downs on software like the one linked to by the article. This is the outrageous claim. If you feel this is not what you're saying then fine, I'm not sure we actually have an argument.

>> I would very much appreciate it if you separated "make outrageous claims" from "develop open source security software".

There's no reason not to develop OSS security software. There's every reason to put up big warnings saying you can't vouch for its security. There's every reason to ask people who know what they're talking about to take a look, and to be humble when they point out flaws, and to rework it if that's the case. There's every reason to take some of the excellent free courses.

But there's also no reason to go off-piste. Why develop this crazy new OTP scheme? There's existing crypto for exactly these use cases. Leave the devising and proving of new crypto constructs to the deeply-versed and the academics, who know how to prove this stuff (and disprove it).

It's like saying "I can't write my OSS networking project because people keep telling me not to rewrite the TCP stack without learning about TCP first". Do you need to rewrite the stack? If so, if you want to do a good job then it's going to take a hell of a lot of knowledge and training. Why not use the OS API?

Re:Be wary of one-time pads and other crypto unicorns by diminoten on Monday March 30, 2015 @11:26AM (#9290125)
Your need to be right has driven us so far afield from the original topic, I'm actually somewhat impressed.

I don't know what you think I wrote, but no one here at any time suggested writing a new crypto scheme.

It's 4 days later. I've made my point over and over again, and you understand it. You have even restated my point yourself, in your second paragraph.

I'm done. You agreed with me, and everything else you're trying to talk about is just you begging to be validated. I can't feed this anymore, sorry.

Re:Be wary of one-time pads and other crypto unicorns by Nursie on Sunday March 29, 2015 @07:03PM (#9286830)
I think we probably still have a fundamental disconnect here.

Can I ask you, when I say - "people writing software products generally shouldn't be creating novel cryptosystems" - what is it you hear?

Do you hear someone saying "you shouldn't be writing software that uses encryption" ?

Because that's not what I'm saying.

A cryptosystem is something like what's going on here - we have messages secured by OTPs, generated using SecureRandom and exchanged over an encrypted channel using an AES key displayed on the screen for the other party to scan.

So what I'm saying is "hey, why not use the industry standards for your crypto? Inventing cryptosystems is way hard and you probably got it wrong. You can still make your cool apps on top of it!"

Re:Be wary of one-time pads and other crypto unicorns by Nursie on Thursday March 26, 2015 @07:29AM (#9268834)
With fairly minimal training one can learn to use existing, secure constructions. Hell, there are now protocols designed specifically for this, open source ones at that.

In fact everyone who even considers touching anything crypto-related should know one simple thing - do not invent your own schemas!

Re:Be wary of one-time pads and other crypto unicorns by diminoten on Thursday March 26, 2015 @07:49AM (#9268880)
If it's minimal, can you please outline the training required to write secure code?

Perhaps you could forward that minimal training to the openssl folks, and maybe you could singlehandedly solve the security crisis currently taking place in software.

Re:Be wary of one-time pads and other crypto unicorns by Nursie on Thursday March 26, 2015 @08:56AM (#9269168)
>> If it's minimal, can you please outline the training required to write secure code?

Nope, because that's not what I claimed.

Re:Be wary of one-time pads and other crypto unicorns by diminoten on Thursday March 26, 2015 @09:03AM (#9269204)
Then can you please outline specifically what training would be required to accomplish... whatever it is you did claim that was, "relatively minimal"?

What classes? What books? What certifications or degrees?

Re:Be wary of one-time pads and other crypto unicorns by tptacek on Thursday March 26, 2015 @11:58AM (#9270560)
My suggestion is: work your way through the Matasano Crypto Challenges. They're free, just sitting there on a static web page, with no signup required.

Actually implement cryptographic attacks before trying to design crypto.

That's not just my recommendation; it's also what Bruce Schneier has been writing for decades.

The problem with my suggestion is that most people who work their way from block cipher attacks through RSA error oracles are "scared straight", and lose the desire to plunk fancy crypto into their applications. Once you see how subtle some of the most devastating attacks are, you start to see why so few crypto engineers write chat apps.

Re:Be wary of one-time pads and other crypto unicorns by jerematasno on Thursday March 26, 2015 @02:13PM (#9271889)
> The problem with my suggestion

I fail to see the problem...

Re:Be wary of one-time pads and other crypto unicorns by Nursie on Thursday March 26, 2015 @09:32AM (#9269403)
Personally I would recommend (if this is a serious question and you're not just trying to challenge my assertion about minimal training) putting yourself through Coursera's Crypto 101, and learning to use a library like NaCl, or borrow a well-reviewed open protocol like TextSecure, which is in TextSecure, Signal and (lately) WhatsApp.

I'm not saying that with minimal training you can write an OpenSSL equivalent, or even create a novel cryptosystem on top of OpenSSL, people writing software products generally shouldn't be creating novel cryptosystems in the first place (and I speak as someone that implements crypto-systems for a living, usually very well defined crypto-systems from banking standards).

Re:Be wary of one-time pads and other crypto unicorns by diminoten on Thursday March 26, 2015 @09:35AM (#9269421)
I'm highly doubtful that a person who's done the training you've recommended will be capable of writing secure software.

The fact that you think it's that easy is a wonderful example of why there's such a disconnect between developers and crypto experts.

Re:Be wary of one-time pads and other crypto unicorns by Nursie on Thursday March 26, 2015 @09:41AM (#9269466)
For the second time, I didn't claim they could write secure software! I'm not even claiming I can write secure software, it's a hard problem.

What they can do is use existing, secure constructions, which at least gives them a fighting chance. Inventing new stuff does not.

Re:Be wary of one-time pads and other crypto unicorns by diminoten on Thursday March 26, 2015 @09:51AM (#9269547)
You did claim they could write secure software, at least that's what you wrote.

If that's not what you meant, then I understand.

Re:Be wary of one-time pads and other crypto unicorns by Nursie on Thursday March 26, 2015 @09:56AM (#9269595)
I think we must be miscommunicating here, I'm genuinely not seeing where I said that (it would not be the first time I have been hilariously unobservant though).

The nearest I can see to that is where I said - "With fairly minimal training one can learn to use existing, secure constructions." - which I think I've qualified/explained now?

Re:Be wary of one-time pads and other crypto unicorns by tptacek on Thursday March 26, 2015 @12:54PM (#9271096)
He's misunderstood you, and then run away with his misunderstanding, perhaps because he thinks it's a more interesting back-and-forth to bounce around than what you actually said.

My reading of what you wrote is: it doesn't take much training to use Libsodium. To the extent that providing cryptographic security is important, you can solve the problem by delegating it to the Nacl designers and Sodium implementors. That's mostly true.

I did not see you making an argument about how simple the entire security problem was to solve.

Re:Be wary of one-time pads and other crypto unicorns by diminoten on Thursday March 26, 2015 @01:13PM (#9271294)
Precisely this. "It's not hard to learn to use a crypto library" is not an interesting conversation, and so I actively tried to have a more interesting conversation about "it's actually pretty damn hard to implement crypto software".

Since when is learning a single crypto library the end-all solution to writing good crypto software?

Re:Be wary of one-time pads and other crypto unicorns by Nursie on Thursday March 26, 2015 @01:20PM (#9271378)
>> I actively tried to have a more interesting conversation about "it's actually pretty damn hard to implement crypto software".

You might have said that!

>> Since when is learning a single crypto library the end-all solution to writing good crypto software?

It's not, but it's a start, a start which all of these stories that hit HN and get torn to pieces are missing.

-- edit --

When I made my comment that you can learn to use existing things with minimal training I should have padded it out by telling you the reason I was saying that - learning to use well-understood crypto primitives, and (if you can) pre-provided crypto implementations is far from all you need to make secure software. But it's a start.

"Hey, come and look at our neat new crypto, it's awesome!" is a big red flag, and it's a red flag with a subtext that reads: We don't know what we're doing.

Software that does use good constructions and good implementations can still be done very badly, it's true.

To go back to your first comment, you say there's this gap between the way crypto people work and the way developers develop - that may well be so, but in most of the messaging apps we see here on HN the developer hasn't really even attempted to bridge that gap.

Think about it like cooking a meal - you're asking what it takes to become a top chef but in the case we're discussing they didn't even start their marinara sauce with tomatoes.

Re:Be wary of one-time pads and other crypto unicorns by pharrington on Thursday March 26, 2015 @11:20AM (#9270252)
There is infinitely more to writing secure software than correctly using secure cryptographic constructs.
Re:Be wary of one-time pads and other crypto unicorns by Nursie on Thursday March 26, 2015 @01:19PM (#9271362)
This is what I should have said a few messages up the chain!

Writing secure software is hard and covers a lot more than your choice of ciphers, protocols etc. It's possible to make all the right choices and still make insecure software for so many reasons. OpenSSL was referenced up-thread - simple buffer overruns/lack of bounds checking is one way in which that failed (heartbleed).

In order to write secure software one needs first to define what we're aiming at, what does secure mean in the domain in which we operate? And that's non-trivial in itself.

But by choosing well-known constructions and (hopefully) well tested implementations we can minimise some classes of potential problems.

Re:Be wary of one-time pads and other crypto unicorns by wglb on Thursday March 26, 2015 @09:40PM (#9274309)
> smartest crypto folks aren't software developers,

This dismisses the talents of DJB who is one of the better software developers and a very good cryptographer.