Ignore:
Timestamp:
Sep 28, 2009, 5:15:19 PM (12 years ago)
Author:
Matthäus Wander
Message:

incorporated feedback from Christian Meyer:

  • fixed description of Caesar and Vigenere
  • changed NumberInput to allow changes during execution
File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/CrypPlugins/Vigenere/DetailedDescription/Description.xaml

    r175 r595  
    8080    <Span xml:lang="en-gb">In the literature, the Vigen&#232;re encryption algorithm is often described in terms of the Vigen&#232;re tableau rather than as a multiple appliance of the Caesar encryption algorithm, since this tableau was used as a manual tool for encryption and decryption in earlier times.</Span>
    8181  </Paragraph>
    82   <Paragraph Margin="0,6.67,0,6.67" TextAlignment="Left" FontFamily="Times New Roman" FontSize="16">
    83     <Span xml:lang="en-gb">In the classical Caesar procedure, the letter "A" means a shift of 1 character position, the letter "B" a shift of 2. In the Vigen&#232;re system on the other hand, the shift is always one character less, i.e. no character for "A", one character for "B", two characters for "C", ... , 25 characters for "Z". Therefore, using the Vigen&#232;re method the plaintext and the encrypted text are identical when the key is "A" (and not "Z", as with the Caesar encryption algorithm).</Span>
    84   </Paragraph>
    8582  <Paragraph Margin="0,0,0,0" TextAlignment="Left" FontFamily="Times New Roman" FontSize="16">
    8683    <Run xml:lang="en-gb">The Vigen&#232;re encryption algorithm can be broken relatively easy with a ciphertext-only attack.</Run>
Note: See TracChangeset for help on using the changeset viewer.