rfc:mcrypt-viking-funeral
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
rfc:mcrypt-viking-funeral [2016/03/15 16:36] – sarciszewski | rfc:mcrypt-viking-funeral [2016/03/15 17:22] – sarciszewski | ||
---|---|---|---|
Line 3: | Line 3: | ||
* Date: 2016-01-09 | * Date: 2016-01-09 | ||
* Author: Scott Arciszewski, | * Author: Scott Arciszewski, | ||
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
Line 33: | Line 33: | ||
* XTEA | * XTEA | ||
* Enigma | * Enigma | ||
+ | |||
+ | This is an acceptable loss: Most of the ciphers in the list above should not be used in new software anyway. Most cryptography experts would consider their inclusion in any software written in 2016 to be a code smell and indicative of a bad protocol design. Some of thme (e.g. Enigma) are outright insecure. | ||
===== Proposed PHP Version(s) ===== | ===== Proposed PHP Version(s) ===== |
rfc/mcrypt-viking-funeral.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1