Fixed an issue where I was not ending the threads properly leading to increased memory and cpu build up when processing many ciphers.

Recompiled with optimizations resulting in a big speed increase. Keys checked per second is now in the millions for my system.

Great approach, checking it out asap,

QT

Thanks Quicktrader,

I’m still working on it, let me know if anything.

I just released a new version which has a big change: each thread now handles it own cipher, in previous versions all threads worked together on one cipher. I’ve also done some minor optimizations here and there. And I retuned the hill climber for ciphers with a multiplicity (63/340) of that around the Zodiac 340.

The "time per cipher" setting has been replaced with "keys per cipher". I recommend that for serious use you put this at 20000000 (20 million). I can currently not guarantee score stability below this point, I’ll see if I can get this down. This is about 5-10 seconds per cipher on my system (i7 930).

0.4

Nearly doubled the speed of the program. A serious bug was fixed that let some threads load the same cipher as the first thread, if you have been using this program I recommend retesting everything you did so far. Some problems considering file input and output are fixed.

I’ve been working on score stability as a top priority. If for example you score 100 copies of a cipher, I would like the difference between the minimum and maximum score for each copy to be within 1%. Currently this is more like 2-3% for 10 to 20 million keys per cipher. Score stability for lower amount of keys has been increased significantly, I find the program useable starting from 5 million keys per cipher for 340 like ciphers.

Jarlve, I just wanted to say I haven’t had time to review your program but I am excited to hear about your progress. Please keep up the wonderful work you are doing!

I will soon start experimenting with the automatic solvers again to help me explore some ideas. It is nice to have several different programs to pick from now!

Thank you doranchak,

0.5

Added a colorful UI with some basic options, plus/minus keys to increase/decrease threads, 0=pause. u/i keys to increase/decrease keys per cipher. It shows all kind of handy stats, pressing the x key will exit the program after letting the threads finish and generating a text log in the results directory + a screenshot of the window in the root. Fixed some minor problems here and there.

I have stress-tested the program up to 125.000 ciphers (30+ hours of computing) and nothing went wrong. I’ll update the main post with some extra information about the UI as soon as I have some more time.

I also want to note that this program is designed to seperate the wheat from the chaff and to get the job done for many and not necessarily provide the best solve quality. Though it should mostly be more than adequate but ZKDecrypto will probably provide a higher quality, better readable plaintext.

Here is an example for the 408, notice that some letters (k,x,etc) are missing. And that the solve is not perfect.

isihehalsingpeopl
ebecauseitissomuc
hfunatiumoretunth
anhillingwasdgime
intheforrestbecau
semanisthemoatcan
gertueinamalotall
tohillsomethanggi
vesmethemoatthril
lingedperenceatis
evenbetterthinget
tingyourrochsoftw
ithagarsthebestpa
rtofitiathiewheni
caeiwillbereborni
nparidaceuncassth
eihavehissedwillb
ecomemyslavesiwil
snotgaveyoumyname
becauseyouwisltry
tosloicownorutopm
ycollectingotssav
esformyafterlitee
beorietemethhpati

JarIve can you run the 340 through your system but first remove all of the first and last lines.
cheers

Hey Mr lowe,

I’ve read about your idea – that some lines may be filler – and find it interesting. I’m planning to do a big test in that direction (43680 variants) in the weekend. I’ll report back with the findings in a new thread and we’ll see from there, stay tuned.

I believe it is glurk who promotes the filler theory and I agree with him. To make this code you could write out your code in plaintext on a grid place it on a light box place your paper over the top and write your code over it choosing your symbols along the way from a prepared list . The semi circle on the side could be the left over from an aligning circle crossing both papers.(similar to a carpenters method of realigning timber flooring when lifted) Well best of luck to you I hope it all goes well. It would be great to get some form of word structures or consecutive words. Interest levels are set on high..cheers..

I also want to note that this program is designed to separate the weed from the chaff

It’s ‘wheat’ from the chaff btw. I’m not being pedantic but it’s the only thing I’ve understood so far lol.

Good work btw tackling this. I am following this thread, albeit clueless-ish, with interest.

Lol traveller1st, can’t stop laughing… what a silly mistake on my behalf.

Mr lowe,

My computer started work on the filler idea. It could take up to 100 hours and after that I will try to analyze the data and report back, I’ll need a week or two.