there lay a mysterious cipher -- a coded message that appears to have remained unsolved. Until now." That's the start of a very interesting article in Wall Street Journal. Thanks to my friend Prof. Haym Hirsh for the pointer.
Features
Stuff from us
Academic Legal Writing: personalized bookplates
In Search of Jefferson's Moose
Sources on the Second Amendment
.
.
.
Those cryptanalysts are an interesting bunch. You really can't keep things secret from them, or at least you couldn't pre-computers, and maybe not even now.
That particular coding method may not have been unbreakable, but I doubt it could have been broken within the lifetime of its author, and that's "good enough" for most applications.
Today we have a much more sophisticated understanding of ciphers, codes and language in general than we did in the late 18th and early 19th centuries. Entire branches of mathematics used today in developing and breaking codes didn't even exist then.
It isn't.
I know exactly what you mean! I absolutely howled the other day when I met a guy who didn't read The Economist. Who knew that such people existed?!? Clutch the pearls!
Well that is awfully fair of you.
I am guessing that in 1776, some people used the and while others did not.
When 2000 came around, I decided to quietly observe when people stopped using "Two thousand" followed by the year and started using "Twenty" followed by the year.
(By the way, from my observation most people will switch in 2010. In casual conversation it is "two thousand nine" but next year is "twenty ten")
I've been using it since 1-Jan-2001. (I briefly considered saying "twenty hundred", but that was just silly.) But I've rarely heard anyone else use it, and it amazes me. I mean, we call 1909 "nineteen-oh-nine", not "nineteen hundred and nine", so why is this year "two thousand and nine" instead of the shorter (by one syllable) "twenty-oh-nine"?
There is only one code type that is unbreakable (one time pads qualify if generated by truly random numbers and used properly). That is a code in which the key is at least as long as all the information transmitted in the code. Since that faile to meet one of the codemaker's other criteria (that it be easy to remember), there is no code that can meet the stated criteria.
And the writer of the article does not understand that a cipher is not a code.
(All this vaguely remembered, and probably misremember, from Simon Singh's beautifully written and informative Code Book, a must-have for every cypherpunk on your Xmas list.)
If you have a comment about spelling, typos, or format errors, please e-mail the poster directly rather than posting a comment.
Comment Policy: We reserve the right to edit or delete comments, and in extreme cases to ban commenters, at our discretion. Comments must be relevant and civil (and, especially, free of name-calling). We think of comment threads like dinner parties at our homes. If you make the party unpleasant for us or for others, we'd rather you went elsewhere. We're happy to see a wide range of viewpoints, but we want all of them to be expressed as politely as possible.
We realize that such a comment policy can never be evenly enforced, because we can't possibly monitor every comment equally well. Hundreds of comments are posted every day here, and we don't read them all. Those we read, we read with different degrees of attention, and in different moods. We try to be fair, but we make no promises.
And remember, it's a big Internet. If you think we were mistaken in removing your post (or, in extreme cases, in removing you) -- or if you prefer a more free-for-all approach -- there are surely plenty of ways you can still get your views out.