[PURE_CY] Why always Rijndael (AES)? And "only" SHA-256 hashing? Why not Serpent and Twofish as an option? Or better, a Rijndael-Serpent-Twofish cascade (...future proof)? Why not SHA-512 and/or Whirlpool hashing? But the app looks great! Cool graphics! // From the Serpent homepage: (www.cl.cam.ac.uk/~rja14/serpent.html): "It was a finalist in the AES competition. The winner, Rijndael, got 86 votes at the last AES conference while Serpent got 59 votes, Twofish 31 votes, RC6 23 votes and MARS 13 votes. So NIST's choice of Rijndael as the AES was not surprising, and we had to content ourselves with silver in the `encryption olympics'. Serpent and Rijndael are somewhat similar; the main difference is that Rijndael is faster (having fewer rounds) but Serpent is more secure." "...The XSL attack, if effective, would weaken Serpent (though not as much as it would weaken Rijndael, which became AES). However, many cryptanalysts believe that once implementation considerations are taken into account the XSL attack would be more expensive than a brute force attack." (Version 1.0b3) |