<?xml version="1.0" encoding="UTF-8" ?>
  <resource>
  <id>7709</id>
  <path>/www/nrich/html/content/id/7709/</path>
  <resourceTypeID>1</resourceTypeID>
  <last_published>2011-10-24T13:36:21</last_published>
  <indexXML>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;mdoxml version=&quot;1.0&quot;&gt;
&lt;p&gt;KVJZVZGDKYRZFLNRYEZJITYVVVCGECVJZKKFWYVKYTTYNKUVJVZWIGIYFRRVVUFJ NVFTVIKFNJJINVKNREEFHFYUVVVRZGYYJWFLLSZJMRJECVVVRFWIVRJFVGZUCEDI TCIJESZWIRWKXUZVRCFVTCEVKINYVZEKVFNIZPKEYKVVKETYJNJVVYYTZWLERXRV RVRKJVZIJIJRUFEPIUERFCJPZFVKZEPNJSUZWGTGJDRIWNFZYPTEVVRKEJMRWYLCZ RFJEUJZKFZEVZWCWKCKXPVFRDXJITZTKILYCFKECVVGVYEFFRDVZLYTNJEFEFUDW
EECJUVFRGVJKIRDJJJVYVKDPVIZIUELVGKKNTNDJTVKVVPKMFYKYZFLKZTZJITV &lt;/p&gt;
&lt;div&gt; &lt;/div&gt;

&lt;/mdoxml&gt;</indexXML>
  <solutionXML>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;mdoxml version=&quot;1.0&quot;&gt;&lt;p&gt;Have you managed to solve the entire &lt;a href=&quot;http://nrich.maths.org/7081&quot;&gt;Stage 5 Cipher Challenge&lt;/a&gt;? Solutions are now closed, but perhaps you want to take up the full challenge.&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p&gt;Successful solvers of this part were&lt;/p&gt;
&lt;p&gt;Patrick from Woodbridge School, England&lt;br&gt;&lt;/br&gt;
An Anonymous Solver from Somewhere in the US&lt;br&gt;&lt;/br&gt;
Joseph from Hong Kong&lt;/p&gt;
&lt;p&gt; &lt;/p&gt;
&lt;p&gt;The solution is:&lt;br&gt;&lt;/br&gt;
&lt;br&gt;&lt;/br&gt;
This was a Caesar shift of seventeen followed by a transposition of rows and columns. This of course retains the letter frequencies of English, which probably helped you decipher this. In this case, the two methods of encryption commute, however this isn&amp;#39;t always the case. Apart from some special cases, if we use a vigenere cipher and then a transposition, we will get a different result depending
on which order we do them in. Can you find any cases for which these will commute?&lt;/p&gt;&lt;/mdoxml&gt;</solutionXML>
  <noteXML>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;mdoxml version=&quot;1.0&quot;&gt;&lt;p&gt;This challenge cipher forms part of a very difficult &lt;a href=&quot;http://nrich.maths.org/7081&quot;&gt;sequence of ciphers&lt;/a&gt; suitable for keen groups or individuals, maths clubs and very optional homework challenges. Don&amp;#39;t try this in the classroom!&lt;/p&gt;&lt;/mdoxml&gt;</noteXML>
  <clueXML>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;mdoxml version=&quot;1.0&quot;&gt;&lt;p&gt;This is the sixth of our &lt;a href=&quot;https://nrich.maths.org/7081&quot;&gt;challenge ciphers&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;We recommend that you attempt them in order, as the solution of each challenge gives a small (and necessary!) hint for the next challenge.&lt;/p&gt;&lt;/mdoxml&gt;</clueXML>
  <canonXML>&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
&lt;mdoxml version=&quot;1.0&quot;&gt;
&lt;p&gt;This was a Caesar shift of seventeen followed by a transposition of rows and columns. This of course retains the letter frequencies of English, which probably helped you decipher this. In this case, the two methods of encryption commute, however this isn&amp;#39;t always the case. Apart from some special cases, if we use a vigenere cipher and then a transposition, we will get a different result
depending on which order we do them in. Can you find any cases for which these will commute?&lt;/p&gt;

&lt;/mdoxml&gt;</canonXML>
  <end_user_role>2</end_user_role>
  <difficulty>5</difficulty>
  <keystage1>0</keystage1>
  <keystage2>0</keystage2>
  <keystage3>0</keystage3>
  <keystage4>0</keystage4>
  <keystage4plus>1</keystage4plus>
  <title>Jluuis or even Asutguus?</title>
  <description>Sixth challenge cipher</description>
  <spec_group>Decision Mathematics and Combinatorics
    <specifier>Combinatorics</specifier>
  </spec_group>
  <spec_group>Decision Mathematics and Combinatorics
    <specifier>Algorithms</specifier>
  </spec_group>
  <spec_group>Applications
    <specifier>Codes and cryptography</specifier>
  </spec_group>
</resource>