News for hackers. Stuff that matters.
Re:Ninja Threat Modeling by tptacek on Tuesday October 20, 2009 @01:49PM (#892876)
I used to say that, and every time I did, people would yell at me, so I've been conditioned not to.

Although I'll stick my neck out and say "crypto; don't even bother".

Re:Ninja Threat Modeling by cperciva on Tuesday October 20, 2009 @02:44PM (#893016)
crypto; don't even bother

I'm supposed to yell at you now, right? :-)

In all seriousness, cryptography doesn't really fall into the "complexity which might introduce security flaws" category: Most cryptographic code is extremely simple. Yes, it's easy to get cryptography wrong; but the ways which people get cryptography wrong make it useless, not harmful. It's very difficult to write an HMAC with a buffer overflow.

Re:Ninja Threat Modeling by tptacek on Tuesday October 20, 2009 @03:40PM (#893148)
You still think that people know what HMAC is. Most people think HMAC means "hash a key in with the message".
Re:Ninja Threat Modeling by cperciva on Tuesday October 20, 2009 @04:33PM (#893298)
My point remains even if people do get confused about that: Their crypto might be broken and useless, but it still won't be harmful.
Re:Ninja Threat Modeling by tptacek on Tuesday October 20, 2009 @04:43PM (#893313)
Dude. You just saw what happened to Flickr. Stop being argumentative.
Re:Ninja Threat Modeling by cperciva on Tuesday October 20, 2009 @04:58PM (#893336)
What happened to Flickr would have happened even faster if they hadn't used crypto at all. Their crypto was broken, but didn't make things worse than they would have been in the absence of crypto.