Oh! I missed that. Thanks for your help!
You can also change to only output ciphers with a score over (variable) just like in the old AZdecrypt. CPU threads, iterations, restarts, ioc weight, it is all there.
That’s great. Thank you very much for the tips and your continuing efforts to improve this fantastic solver.
A new AZdecrypt update (1.07) has been added to the main page.
What is new?
– Substitution + null symbols solver. It decrypts ciphers were a bunch of symbols are to be removed, assuming that every instance of that symbol needs to be removed.
– The Stats menu has been split into Stats and More stats.
– Encoding randomization tests have been added to More stats, it attempts to find sections of randomization in sequential homophonic substitution ciphers.
– Stats options has been added to the options menu. It allows to change some settings that pertain to the encoding randomization and plaintext/encoding direction tests.
– 2 and 3-symbol cycles output with details has been added to More stats.
– Renamed the Substitution + by rows solver to Substitution + row bound.
– Various other updates and bug fixes.
Jarlve, I’m playing with creating my own custom ngrams files to use in AZdecrypt. It looks pretty straightforward so far, but I have one question: How do I come up with the value for Ngramfactor in the INI file?
Jarlve, I’m playing with creating my own custom ngrams files to use in AZdecrypt. It looks pretty straightforward so far, but I have one question: How do I come up with the value for Ngramfactor in the INI file?
The ngram factor decides the AZdecrypt scores. I usually set it to such a value that the 408 scores about 23225 as a simple measure of normalization. Also, the settings are optimized to work in that score range.
Putting more ngram items on one line will improve loading times but keep each line under 1 megabyte or so. The alphabet in the .ini file must match the alphabet used in the ngram file itself, case sensitive. And the order of the alphabet affects the vigenère solver. The ngram file loading routine is not fail safe but there are some checks, if AZdecrypt reports back the correct number of ngram items than most likely everything is okay.
OK – Thanks for the explanation!
A new AZdecrypt update (1.08) has been added to the main page.
What is new?
– New solver: Substitution + polyphones [auto]. It can solve wildcard ciphers automatically and more. The number of extra letters to use can be changed via the options menu. I recommend that you use 6-grams and a multiplicity weight of 1 or lower/higher. This multiplicity weight ensures that the solver uses as few extra letters as possible.
– Renamed the Substitution + user defined polyphones solver to Substitution + polyphones [user].
– Improved solver: Substitution + transposition and added some options to alter.
– New solver: Merge seq. homophones with options to alter. Works very well on sequential homophonic substitution ciphers without much encoding randomization.
– Added option: (General) output to batch. Will output all solutions of a solver in a file instead of many when set to 1.
– Added option: (General) output additional stats. Ngram score of solution and plaintext to ciphertext cycles score.
– Slightly improved n-gram loading times.
– Improved options menus.
– Bugfixes.
A demo of the Substitution + polyphones [user] solver. I have not gone in depth about this solver but it is very powerful. The following 25 symbol cipher is aperiodically polyalphabetic and has 2 keys with a 168/172 distribution. That is to say, key 1 takes up 168 characters and key 2 takes up 172 characters. Even with only 25 symbols the amount of total combinations to consider is astonishing. Per symbol it are 2^frequency unique 2 key combinations multiplied by 26*25 unique alphabet states. And then multiply these products of each symbol by eachother.
!"/#$#3+2/%&'.('8
.!1"#$%43&535)'$"
()$,71!32-*9)$064
06#/"+3%*+52,&#'.
7,7(1)-9*158!1"0$
%42#0!3&49'(51,0,
&$9)$3#0/208))#"+
6(#3285)'17(56*&7
-4%'984$2-38&(*!"
"/%*..'194,"9/135
$-.0!1674914#6&96
736*/($*9)"#%())+
58(0&7*+&4$!.31'#
97))!8/5&(01+41%3
,547+!2+!9*$!-9,/
0'#*0,3".#6,0286(
154#-4#7"+9,+528!
$"('.2/%"0-137+!"
"%)7*/-4/-$'/,029
!$"#$%./($+3+279/
To solve it open the cipher in AZdecrypt and load the reddit 6-grams. Open the symbols menu under functions and use "set plaintext letters for all symbols/polyphones" to set the number of letters per symbol to 2. Go to solver options under options and set the multiplicity weight to 1 and click solve in the main window. I was lucky enough to get the following solve in 3 minutes. Ciphers with up to 40 symbols can be attempted with 6-grams, I have not tried to push it any further.
Score: 23928.40 Ioc: 0.06310 Symbols: 50 Ngrams: 1092 PC-cycles: 9238 BLIKEKILLINGPEOPL EBECAUSEITISSOMUC HFUNITISMOREFUNTH ANKILLINGWILDGAME INTHEFORRESTBECAU SEMANISTHEMOSTDAN GEROUSANIMALOFALL TOKILLSOMETHINGGI VESMETHEMOSTTHRIL LINGEXPERENCEITIS EVENBETTERTHANGET TINGYOURROCKSOFFW ITHAGIRLTHEBESTPA RTOFITISTHATWHENI DIETWILLBEREBORNI NPARADICEANDALLTH ESHAVEKILLEDWILLB ECOMEMYSLAVESTWIL LNOTGIVEYOUMYNAME BECAUSEYOUWILLTRY
The new solver Substitution + polyphones [auto] uses the same internal solver as the [user] one but hill climbs the extra letters (can be changed under solver options) over the symbols automatically. As said before, I recommend using 6-grams and a multiplicity weight of 1 with the these solvers.
Jarlve,
I just run a very, very long test with many permutations with AZDecrypt. The batchfiles I create are averaging 230 MB and contain between 0,5 and one million ciphers. I haven’t noticed any problems so far, but I wanted to ask: Is this recommended or do you suggest a maximum size?
By the way, if you find some time: May you implement an automatic PC shutdown as soon as a batch file has been run through? I leave the PC on overnight, but it doesn’t have to run until morning. This would make sure that not so many polar bears melt and it also saves electricity;)
I just run a very, very long test with many permutations with AZDecrypt. The batchfiles I create are averaging 230 MB and contain between 0,5 and one million ciphers. I haven’t noticed any problems so far, but I wanted to ask: Is this recommended or do you suggest a maximum size?
No worries about maximum size since AZdecrypt does not keep the whole file in memory.
If you want to trim the output a bit, under options, solver, you can set (General) Output scores over: to 20500 or so. Then AZdecrypt will only output the ciphers that scored over 20500. Another option is to set (General) Output to batch: to 1. Then AZdecrypt will output all ciphers in a single file. These options can be combined.
By the way, if you find some time: May you implement an automatic PC shutdown as soon as a batch file has been run through? I leave the PC on overnight, but it doesn’t have to run until morning. This would make sure that not so many polar bears melt and it also saves electricity;)
I am not sure if a program is allowed such access.
Thank you very much for the explanation!
Shutdown should work by calling a shell-command. I have no free basic compiler installed (you are using freebasic, right?) but this may work:
SHELL ("SHUTDOWN /s /t 10 " )
10 means 10 seconds.
Thank you very much for the explanation!
Shutdown should work by calling a shell-command. I have no free basic compiler installed (you are using freebasic, right?) but this may work:
SHELL ("SHUTDOWN /s /t 10 " )10 means 10 seconds.
Thank you for the tip. I should be able to include the shutdown feature for the next release.
A new AZdecrypt update (1.09) has been added to the main page.
What is new?
– Slightly improved substitution solver.
– Batch ciphers (substitution) is faster when processing ciphers with a reasonably low number of iterations and restarts.
– The vigenère solver can be set to solve by rows under the options, solver menu by changing by columns to 0.
– Fixed a bug where the 7-gram substitution solver was erroneously linked to a polyalphabetic solver.
– Fixed a bug with the 6-gram vigenère solver.
– Added some stats and various other bugfixes.
Largo, I just realized I forgot about your shutdown feature.
Thank you very much for the update Jarlve! I especially like the faster batch solver.
Largo, I just realized I forgot about your shutdown feature.
Never mind, thank you for considering implementing this feature!
