Justin Troutman
October 20th, 2009, 02:04 AM
Part 2 of "Green Cryptography: Cleaner Engineering Through Recycling" was published recently by IEEE Security & Privacy. Now that parts 1 and 2 have been published, it won't be long until we'll put the original, extended draft online. In the meanwhile, we welcome any feedback, and encourage it. (For those without access to IEEE's publications, part 1 is currently available as a free PDF download (http://www2.computer.org/cms/Computer.org/ComputingNow/homepage/2009/0909/W_SP_GreenCryptography.pdf).)
For those of you who don't know, this is the joint work of myself and Vincent Rijmen (co-designer of the AES, along with Joan Daemen). Essentially, "green cryptography" is about recycling, for the purpose of keeping the implementation as clean and simple as possible. Why? Because when cryptography fails, it's almost always because of the implementation -- not the cryptography itself.
We propose this paradigm of design that shows how minimalist implementations and mature cryptography can be wed into a simple and secure design. Realistically, if you're worrying about the cryptography, you're worrying about a problem that's largely solved; green cryptography addresses the real problem, and makes the fix accessible to those who are left to deal with it -- the developers.
For those of you who don't know, this is the joint work of myself and Vincent Rijmen (co-designer of the AES, along with Joan Daemen). Essentially, "green cryptography" is about recycling, for the purpose of keeping the implementation as clean and simple as possible. Why? Because when cryptography fails, it's almost always because of the implementation -- not the cryptography itself.
We propose this paradigm of design that shows how minimalist implementations and mature cryptography can be wed into a simple and secure design. Realistically, if you're worrying about the cryptography, you're worrying about a problem that's largely solved; green cryptography addresses the real problem, and makes the fix accessible to those who are left to deal with it -- the developers.