caused
2010-01-23 16:16:51
xxx
2010-01-23 16:16:51
2010-01-23 16:24:24
2010-01-23 16:24:26
2010-01-23 16:25:37
2010-01-23 16:28:02
end 175.333333333
2010-01-23 16:35:18
2010-01-23 16:50:15
2010-01-23 16:52:20
From: Frement
You got any idea what it should output?
2010-01-23 17:07:08
2010-01-23 17:11:00
From: Harry
We would need the key-word, else it would be almost impossible to decode.
ADFGVX was cryptanalysed by French Army Lieutenant Georges Painvin. The work was exceptionally difficult by the standards of classical cryptography, and Painvin became physically ill during it. His method of solution relied on finding messages with stereotyped beginnings, which would fractionate the same, then form similar patterns in the positions in the ciphertext that had corresponded to column headings in the transposition table. (Considerable statistical analysis was required after this step had been reached — all done by hand.)
This meant it was only effective during times of very high traffic — but, fortunately for the cryptanalysts, that was also when the most important messages were sent.
Painvin broke the ADFGX cipher in April 1918, a few weeks after the Germans launched their Spring Offensive. As a direct result, the French army discovered where Ludendorff intended to attack. The French concentrated their forces at that point and stopped the Spring Offensive.
The ADFGX and ADFGVX ciphers are now regarded as insecure for any purpose.
Note: the claim that Painvin's breaking of the ADFGX cipher stopped the German Spring Offensive of 1918, while frequently made,[1] is disputed by some. In his 2002 review of Sophie de Lastours' book on this subject, La France gagne la guerre des codes secrets 1914-1918, in the Journal of Intelligence History, (Journal of Intelligence History: volume 2, Number 2, Winter 2002) Hilmar-Detlef Brückner states:
Regrettably, Sophie de Lastours subscribes to the traditional French view that the solving of a German ADFGVX-telegram by Painvin at the beginning of June 1918 was decisive for the Allied victory in the First World War because it gave timely warning of a forthcoming German offensive meant to reach Paris and to inflict a critical defeat on the Allies. However, it has been known for many years, that the German Gneisenau attack of 11 June was staged to induce the French High Command to rush in reserves from the area up north, where the Germans intended to attack later on. To achieve this, its aim had to be grossly exaggerated. This the German High Command did by spreading rumors that the attack was heading for Paris and beyond; disinformation proved effective then - and apparently still does. But the German offensive was not successful because the French had a sufficient number of reserves at hand to stop the assault and did not need to bring in additional reinforcements. Moreover, it is usually overlooked that the basic version of the ADFGVX cipher had been particularly created for the German spring offensive in 1918, meant to deal the Allies a devastating blow. It was hoped that the cipher ADFGX would protect German communications against Allied cryptographers during the assault and this is what it indeed did. Telegrams in ADFGX appeared for the first time on 5 March, the German attack started on 21 March. When Painvin presented his first solution of the code on 5 April, the German offensive had already petered out.
2010-01-23 17:40:19
2010-01-23 19:09:19
2010-01-23 19:30:28
2010-01-23 20:51:40
2010-01-23 22:24:49
2010-01-23 22:38:39
From: Santa_Clause
Umm…does this have anything to do with maths? And someone want to explain what 'decrypt' means?
2010-01-24 03:19:42
2010-01-24 04:04:18
2010-01-24 09:10:17
From: Zyt3x
Encrypted text: SGHIHDGJLHRJHGJDS (example)
Clear text: Buy me apples.
To turn the encrypted text into text that you can read, you have to decrypt the text.
From: Zyt3x
To turn the encrypted text into text that you can read, you have to decrypt the text.
2010-01-24 09:42:40
2010-01-24 11:02:50
2010-01-24 11:05:34
2010-01-24 12:47:43
2010-01-24 14:05:25
From: mixster
Well, as you said you had "short" as the key, I assumed that was the transposition key. Using that and a bit of voodoo magic, I worked backwards to get the original, encrypted key. I've got a Scar script that does it, but it's just a bit of backwards working based on what the wiki article says - you still have to do the hard bit and produce the encryption alphabet.
2010-01-24 15:25:17
2010-01-24 15:26:51
From: mixster
If you don't know how long the transposition key is, then not only do you have to work out which of the possible squares it could be, you also have to go through all the possible transposition keys. The square itself is a 6x6 grid, so that's just about an unfeasible number as it is and so your only bet would be quite advanced compared to bruteforcing by combining the bruteforce with word recognition to find combinations that produce large amounts of legible words - cryptanalysis of some sorts.
2010-01-24 15:31:10
2010-01-24 19:43:34