Hi,
I now have completed my approach to crack the 340 by focussing on line 17 of the cipher, starting with the 'C' symbol. I call it the FCCP-method. The method does work, however it is very computational, which still is a challenge. Nevertheless, the 340
is definitely crackable, imo:
1.
Define the '+' symbol (e.g. as 'L' - according to Bernoulli formula it has a 79% chance, second is 'S' with about 2.5% only)
2.
Define the 'L' symbol according to step one. In our case (+ being an 'L'), this is AEIOU and few other consonants (e.g. 'w' as in 'owl'). Please note that the 'L' symbol is one previous to the ++ symbol.
3.
Define the 5-gram 'IoFBc'. It consists out of two repeating trigrams, 'IoF' and 'FBc'. Both appear twice, it is likely that some other cleartext trigrams behind these cipher trigrams are actually present but well hidden behind other homophones. At least they are frequent, e.g. had a 0.5% chance to show up in the 340 twice. Both of them to be combined delivers us a 5-gram. From all 5-grams consisting of two frequent trigrams, we work us down according to a reliable frequency list 5-grams. One may soon see that only approximately 10-50 of such 5-grams actually come into focus, so we can handle them one after another. 'QUFBZ', for example, is not really a good candidate.
4.
Define the 'C' symbol as being any letter from A-Z. This leads us to the i]column[/i] of our future data table.
5.
Define the 'W' symbol and the 'o with horizontal line' symbol in combination as AA, AB,...ZY,ZZ (line of our table). Some combinations may be eliminated (e.g. QQ) as these two symbols follow directly after the ++ double symbol. This leads us to the
line of our data table. Our data table should now have approximately 37,180 entries.
6.
Set variable #1, the 'reverse L' symbol. Set
variable #2, the 'Zodiac symbol'. Both variables shall be checked out on each run individually, both A-Z, thus 676 settings to be done on each run.
7.
Concatenate all of the above to text strings. We do get a table of so-called
fictitiously created cleartext phrases (FCCPs, my term). These FCCPs may linguistically be nonsense - or not. All do have the same structure X_XXXXXXXXXXXXXXXX meaning that we do get a string of 16 letters (!) in a row. I never had imagined to even get 12..
8.
Analyse the data by comparing all FCCPs with a dictionary (excel 'aggregate' function..please don't ask me how..), doing so by e.g. searching for any word of length >6 or e.g. any combination of at least three words.
I did program this FCCP method by using Excel. So what was the result?
Based on the assumption that + is an 'L' (or whatever letter you think it should be), the creation of a table containing these 37,180 FCCPs (per run) goes like this:
a.) Entering 'IoFBc', e.g. 'TIONS'
b.) Setting variable #1, e.g. as 'C' (RUN 2) or 'D' (RUN 1)
c.) Setting variable #2, e.g. as 'B'
d.) Analyze all FCCPs from the data table with regard to linguistic structures (e.g. finding a word with length >6)
Based on the 5-gram 'TIONS' the results of the first two settings were the following:
RUN 1 (L, TIONS, D, B, length >6):
no resultRUN 2 (L, TIONS, C, B, length >6):
CONTROL, CENTRALThe FCCP method
does work as long as Z had used
any word of length >6 in this particular 16-letter phrase (the dictionary is therefore reduced, too, as all the shorter words can be ignored, btw). The cracking process eliminates all FCCPs not containing any of such word or linguistic structure. All 'positive' FCCPs are shown in e.g. a structure like this:
X_XXCONTROLXXXXXXX
All of the positive FCCPs can be checked out further: Finding a second word in the phrase or looking for a logical sense by reading the results. Expansion to a string of 18-letters is possible. Wouldn't there be any match, all words of length >5 must be searched for. However there are results:
While RUN 1 showed up with no results at all, in RUN 2 I could receive a total of 56 matches out of 37,180 (26 for each, CONTROL and CENTRAL). The procedure has thus eliminated 31,724 or 99.85% of 'nonsense' FCCPs. This, in fact, is the cracking process itself.
It is then possible to perform one run after another with 676 settings of variables for each 5-gram, e.g. TIONS, ATIVE,... etc. All that based on + being an L. So far the results have not led to a fully readable text. But so far I have only performed 5 runs of approximately a few thousands that are required to find the cleartext solution.
On my PC with 19 GFlops, which is quite slow, each run takes about 2 minutes. This leads us to 676 settings x 50 potential 5-grams x 2 minutes or a total of 33,800 runs x 2minutes. Thus approximately 7 weeks of calculation time is needed to check out all relevant settings (non-outlier). This is months if not years of work if we do consider changing the variables and extracting the results as well.
BUT:
If the cipher is a homophonic substitution cipher, like the 408 is, it then can be solved by using this method.
The only challenge is the computation: A computer with at least 10 Terraflops, better 100 Terraflops is required to find the cleartext solution in a reasonable time. The solution may appear on the next run or on the last..I do expect it to be found in the first third, thus 10,000 runs (with 676 settings each). Please note that the computational effort is also higher than in trial-and-error methods of sequences as the string has to be first concatenated and then checked against the complete dictionary (latter I keep small..better to apply on Z's language and faster).
The 340 is definitely not crackproof. Anybody got a Cray computer at home?
Below you see my table starting in C10, above is an auxiliary table plus the setting of variables. It goes down to C139 and is mostly hidden (~600 columns). On the right is the dictionary plus the results found. All FCCPs containing results can be looked up by the search function (or automatically, but I keep the file simple - it has approx. 500kb only - full of complicated formulas such as the 'aggregate' function making it able to compare all FCCPs with all words of the dictionary):
FCCPanalyzer.jpg
After five runs only, I was able to rule out 5 x 37,180 = 185,900 FCCPs of promising settings in a few minutes only. So these settings have never to be tried out again (min length >6). Looking into the billions of FCCPs possible, this is still quite a fast way to eliminate all of the nonsense FCCPs. In combination with our understanding of trigram, 5-gram frequencies, the method should well deliver the result when used with appropriate computation.
Advantages of the FCCP method:
1. If Z had interrupted the sequences (e.g. 'W' is frequent in line 17/18, however not present in other areas of the cipher), this method still works.
2. Sequence analysis has to check-out
all combinations. There is no reduction e.g. by considering a vowel (or consonant) previous to ++
3. Frequencies of trigrams, 5-grams can be considered thus the chances of finding the solution are extremely improved
4. Running a sequence analysis does not eliminate varieties. Thus on each run the same sequences could appear. The FCCP-method strictly rules out 'wrong' settings.
5. A direct analysis of individually defined linguistic criteria is possible. Positive FCCPs always represent a partial or fully readable text, not only a score value.
6. Intermediary peaks (hills climb..) can be avoided by further analysis of positive FCCPs while the sequence analysis usually gets stuck (or runs for ages)
7. ABCCA and vowel/consonant structures can be considered, e.g. by pre-selection in the dictionary
8. A smaller dictionary is required by e.g. searching only for words >6, which are likely to appear in a 16 or 18 letter phrase.
9. In fact it's the fastest way to determine a cleartext solution as all of the above supports the solving process to be quicker than a simple trial-and-error method (hills climb).
10. The method is applicable on all homophone substitutionn ciphers as long as they support structures to create FCCPs of a certain length (all others are unsolvable if not all varietes are checked).
I'm gonna make this my phdoc thesis

.
QT
You do not have the required permissions to view the files attached to this post.