What I'm talking about is a hand cipher which uses phonemes instead of individual characters and pictograms instead of the usual shuffling/substitution methods (e.g Caesar, Solitare, Vignere).

The pictograms would be composite images made from smaller images that represent each phoneme in the word. These images are are drawn by hand.

Would this deter computers at all in breaking the cipher? (I'm thinking it would be difficult to input the images for analysis given our current image recognition utilities).

  • $\begingroup$ Why are you just worried about computers? It seems like this would be easily cracked by hand. $\endgroup$ – cpast Apr 11 '15 at 0:11
  • $\begingroup$ @cpast I just want something hard to crack through computer analysis, whether or not it can be cracked by hand is something I can deal with later. And also, the point is exactly that, something which can be cracked easily by humans but not by computers $\endgroup$ – Dider Apr 11 '15 at 0:24
  • $\begingroup$ What, in case we have to rise against the machines? $\endgroup$ – Maarten Bodewes Apr 11 '15 at 0:34
  • $\begingroup$ No, in case the machines rise against us $\endgroup$ – Dider Apr 11 '15 at 3:44
  • $\begingroup$ Usually a cipher is cracked by a human /using/ a machine. It will be hard to create something which is harder to break if you have more computational power. $\endgroup$ – Aleph Apr 13 '15 at 7:05

Yes, of course it would deter computers...

... if it were done as substitution and every instantiation of a symbol had a new meaning. This would avoid frequency analysis.

But you are going to be drawing a lot of pictures, and your correspondent is going to need a thick book of hand-drawn symbols if you have a lot of traffic (will each of your hand-drawn symbols look exactly alike each time you draw it?).

Moreover, you now have a physical security problem. And keep in mind that this isn't art class--it's cryptography. But what you propose was widely done in the past, especially in the sixteenth century, and it was serious business.

However, the sixteenth century is over.

If you go ahead anyway, you should not reuse your symbols if they map one-to-one to an individual phoneme (if you only use substitution and not transposition). If you are ambitious and you enjoy drawing, you could create a system in which you map a phoneme to a different pictogram each time, which would surely be effective--but, again, this would all be time-consuming.

Nothing is gained by using phonemes, and perhaps nothing is gained by drawing the symbols by hand (unless you do not trust your computer). Just use ASCII or extended ASCII.

Let's skip the fact that not only will the language have to be agreed upon, but also the dialect. Doing this for English (at least) is going to become a rat's nest of uncertainty very quickly. Which system of phonemes to use also needs to be determined, and this will not be easy. Will you use IPA? Will you say there are 42 or 44 phonemes? Which English dictionary will you use to determine/check the pronunciation? What is the pronunciation? If you look at various English dictionaries, you might be surprised to discover that they sometimes disagree about proper pronunciation.

Anyway, let's consider this ciphertext (plaintext "go up") based on English phonemes:

β ┤ Ω ♯

Is a computer going to be able to break it without knowledge of your code book? No. Without knowledge of your preshared secrets, cryptanalysis is going to hit a wall.

Is this cryptography? Yes. According to Claude Shannon:

... “true” secrecy systems where the meaning of the message is concealed by cipher, code, etc., although its existence is not hidden, and the enemy is assumed to have any special equipment necessary to intercept and record the transmitted signal.

But do we want to go back to this the kind of primitive cryptography? Other methods exist which are much easier and far better--and may offer an integrity check and authentication.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.