Cipher of Advanced Encryption Substitution And Rotation

In the rapidly changing world of eternal mathematical truths, we need to innovativize for the sustanation of our competitive advantage. So instead of serving our customer base with the same old encryption algorithms that are used by governments, military, and most of the Internet, we want to provide the world with new, proprietary systems that should clearly set us apart in the marketplace and among the expert community.

With great pleasure, I’d like to introduce our forthcoming encryption system: Cipher of Advanced Encryption Substitution And Rotation (CAESAR).

Rationale for CAESAR

No salt but the finest

Himalayan Rock SaltUsing block equality (described below) largely obviates the problem of obtaining a good salt or nonce in our cryptography. But because we will be transitioning to our new system, there are cases where we still need to find a good salt. Most cryptographic implementations have been written in the C programming language, and so for past decades the fashion as been for C-salt. C-salt, of course, was an improvement on table salt, which entirely failed to discourage the use of tables in cracking passwords.

Times have changed, and C-salt is now passé. Instead people have been discovering the virtues of Himalayan salt. Thus we sent off an expedition to Pakistan, Afghanistan, Nepal, India, and Bhutan to find and bring back the finest and rarest of salts for our encryption recipes. To protect our interests, this salt and its origins must remain secret.

Rotation, modularity, and alphabets

Pretty much all computer ciphers are based on the theory of finite groups. CAESAR is no different. Indeed, despite the fact that we just came up with the system recently, the use of groups and rotation in CAESAR may fairly be said to be precedent setting. Yeah, history can be weird that way.

We are faced with one difficulty in our approach. Our expedition to far off lands described above discovered something that completely shocked us in addition returning with a source of salt. They discovered that not everyone speaks English. Not only did this astonishing discovery lead to our researchers submitting a number of papers to various academic journals (oddly, we have not heard back from them), and caused considerable delays and expense for the expedition itself; it also means that our original rotation would not work as effectively in alphabets that use more than the English letters A through Z.

After careful consideration of this issue, we realized that requiring such people to use English would actually increase their security. They would be using a language that those around them may not be able to read, thus giving them a second layer of encryption. This showed how forward thinking our design was. It automatically provided higher security in some unanticipated cases.

All blocks are equal!

Blockrights designOne of the problem with the kinds of block ciphers is their lack of equality when used in CBC or CTR modes. We, however, want to return the spirit of ECB mode in which all blocks are equal (Credit for this particular insight goes to the people at 0-Day Clothing).

In addition to the fairness issues in support of the notion that all blocks should be treated equally, it must be noted that mathematics is built on the notion of a mathematical function. Ensuring that a given input produces a unique value, turning to something like ECB mode helps restore us to mathematical purity.

Where to from here?

I have provided only a few of the highlights of CAESAR and our new thinking in cryptography. This custom made, bleeding-edge scheme will doubtless place us in a unique position in the security community. Look for more new projects in the future, possibly a year from the date of this article’s publication, April 1. One we are looking at is System of Natural Additive Key Encryption—Overloaded In Layers.

Other posts in this series

  1. Guess why we're moving to 256-bit AES keys (March 9, 2013)
  2. Authenticated Encryption and how not to get caught chasing a coyote (January 18, 2013)
  3. Doing the two-step until the end of time (December 20, 2012)
  4. Alan Turing's contribution can't be computed (December 8, 2012)
  5. Hashing fast and slow: GPUs and 1Password (December 5, 2012)
  6. Credit card numbers, checksums, and hashes. The story of a robocall scam (October 18, 2012)
  7. Flames and collisions (June 7, 2012)
  8. A salt-free diet is bad for your security (June 6, 2012)
  9. Cipher of Advanced Encryption Substitution And Rotation (April 1, 2012)
  10. Do you know where your software comes from? Gatekeeper will help (March 1, 2012)
  11. AES Encryption isn't Cracked (August 18, 2011)
0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.