News for hackers. Stuff that matters.
Re:Cryptographic Right Answers by tptacek on Thursday June 11, 2009 @11:41AM (#652893)
Oh and another thing Colin, you jerk:

All of your recommendations die in embedded applications, where nobody will use HMAC-SHA256 (or SHA256 at all) or RSA.

;)

Re:Cryptographic Right Answers by cperciva on Thursday June 11, 2009 @11:57AM (#652934)
This depends on how small your embedded systems are. If your system is too small to run RSA, it's probably too small to use any asymmetric crypto; and if it's too small to use HMAC-SHA256, it's probably too small to use any crypto at all.

There are certainly applications where I would revise my recommendations, but embedded isn't particularly one of them.

Re:Cryptographic Right Answers by tptacek on Thursday June 11, 2009 @11:59AM (#652939)
Systems that are too small to use RSA routinely use ECC.
Re:Cryptographic Right Answers by cperciva on Thursday June 11, 2009 @12:08PM (#652963)
I don't think that's quite right. The systems you're thinking of are almost certainly not too small to use RSA -- rather, they're too slow to use RSA. As I wrote in the article, ECC has advantages where speed is an important consideration.
Re:Cryptographic Right Answers by tptacek on Thursday June 11, 2009 @12:59PM (#653083)
I've definitely heard both objections --- space and time --- but my real point is, one of the app domains that most commonly hosts bespoke cryptography is largely incompatible with your recommendations.