For last few weeks the GPU apps were trying to break ALQFI taken from here: http://cryptocellar.org/bgac/GArmy_messages.html

The GPU app is very fast and at the current rate, on average it takes just under a minute to do a full walk over all possible wheel settings of an 'army' enigma (UKW B, wheels 1-5)

So far we did:

- nearly 8000 walks running mode 2 (-a), with scores "023" (icscore - bigram - trigram) using "1941" dictionary set (batch g3_alqfi87_9)
- nearly 6000 walks running mode 2 (-a), with scores "023" (icscore - bigram - trigram) using dictionaries provided by Alex (the author), codenamed AVv1 (batch g3_alqfi87_8)
- nearly 6000 walks running mode 2 (-a), scores "013" (icscore - unigram - trigram) using dictionaries provided by Alex (batch g3_alqfi87_7)
- nearly 10000 walks mode 2 (-a), scores "023" using 86v1 dict set (this is a newer revision of 1941 dictionary) & nearly 7000 walks with the same set running scores "013".

Combined thats nearly 40,000 walks over all the possible wheels settings, and the message is still unbroken (unless the solution is already found but for some reason has a score lower than top scores, but that's unlikely). I'm going to write a script that will dump all the unique results for all batches for review, there used to be a live view but that's unusable now due to database size.

At 87 letters length the message should be breakable quite easily if there is nothing wrong with it (well obviously it's not an easy one because it was listed for quite a long time and remains unbroken).
The next step I'd like to try before giving up on ALQFI is to trim the first or last {n} letters. At around 70 letters it should still be breakable with some luck and lots of restarts, and shortening may help if there is any kind of damage near the beginning or end of the message.

Or, if anyone has better idea, please let me know.

---

M4 Project homepage
M4 Project wiki