Symmetrickey algorithm
This article needs additional citations for verification. (April 2012) (Learn how and when to remove this template message)

Symmetrickey algorithms^{[1]} are algorithms for cryptography that use the same cryptographic keys for both encryption of plaintext and decryption of ciphertext. The keys may be identical or there may be a simple transformation to go between the two keys.^{[2]} The keys, in practice, represent a shared secret between two or more parties that can be used to maintain a private information link.^{[3]} This requirement that both parties have access to the secret key is one of the main drawbacks of symmetric key encryption, in comparison to publickey encryption (also known as asymmetric key encryption).^{[4]}^{[5]}
Contents
Types
Symmetrickey encryption can use either stream ciphers or block ciphers.^{[6]}
 Stream ciphers encrypt the digits (typically bytes), or letters (in substitution ciphers) of a message one at a time. An example is the Vigenere Cipher.
 Block ciphers take a number of bits and encrypt them as a single unit, padding the plaintext so that it is a multiple of the block size. Blocks of 64 bits were commonly used. The Advanced Encryption Standard (AES) algorithm approved by NIST in December 2001, and the GCM block cipher mode of operation use 128bit blocks.
Implementations
Examples of popular symmetrickey algorithms include Twofish, Serpent, AES (Rijndael), Blowfish, CAST5, Kuznyechik, RC4, DES, 3DES, Skipjack, Safer+/++ (Bluetooth), and IDEA.^{[7]}^{[8]}
Cryptographic primitives based on symmetric ciphers
Symmetric ciphers are commonly used to achieve other cryptographic primitives than just encryption.^{[citation needed]}
Encrypting a message does not guarantee that this message is not changed while encrypted. Hence often a message authentication code is added to a ciphertext to ensure that changes to the ciphertext will be noted by the receiver. Message authentication codes can be constructed from symmetric ciphers (e.g. CBCMAC).^{[citation needed]}
However, symmetric ciphers cannot be used for nonrepudiation purposes except by involving additional parties.^{[citation needed]} See the ISO/IEC 138882 standard.
Another application is to build hash functions from block ciphers. See oneway compression function for descriptions of several such methods.
Construction of symmetric ciphers
Many modern block ciphers are based on a construction proposed by Horst Feistel. Feistel's construction makes it possible to build invertible functions from other functions that are themselves not invertible.^{[citation needed]}
Security of symmetric ciphers
Symmetric ciphers have historically been susceptible to knownplaintext attacks, chosenplaintext attacks, differential cryptanalysis and linear cryptanalysis. Careful construction of the functions for each round can greatly reduce the chances of a successful attack.^{[citation needed]}
Key management
Key establishment
Symmetrickey algorithms require both the sender and the recipient of a message to have the same secret key. All early cryptographic systems required one of those people to somehow receive a copy of that secret key over a physically secure channel.
Nearly all modern cryptographic systems still use symmetrickey algorithms internally to encrypt the bulk of the messages, but they eliminate the need for a physically secure channel by using Diffie–Hellman key exchange or some other publickey protocol to securely come to agreement on a fresh new secret key for each message (forward secrecy).
Key generation
When used with asymmetric ciphers for key transfer, pseudorandom key generators are nearly always used to generate the symmetric cipher session keys. However, lack of randomness in those generators or in their initialization vectors is disastrous and has led to cryptanalytic breaks in the past. Therefore, it is essential that an implementation uses a source of high entropy for its initialization.^{[9]}^{[10]}^{[11]}
Reciprocal cipher
This section needs additional citations for verification. (December 2015) (Learn how and when to remove this template message)

A reciprocal cipher is a cipher where, just as one enters the plaintext into the cryptography system to get the ciphertext, one could enter the ciphertext into the same place in the system to get the plaintext. A reciprocal cipher is also sometimes referred as selfreciprocal cipher. Examples of reciprocal ciphers include:
References
 ^ Other terms for symmetrickey encryption are secretkey, singlekey, sharedkey, onekey, and privatekey encryption. Use of the last and first terms can create ambiguity with similar terminology used in publickey cryptography. Symmetrickey cryptography is to be contrasted with asymmetrickey cryptography.
 ^ Kartit, Zaid (February 2016). "Applying Encryption Algorithms for Data Security in Cloud Storage, Kartit, et al". Advances in ubiquitous networking: proceedings of UNet15: 147.
 ^ Delfs, Hans & Knebl, Helmut (2007). "Symmetrickey encryption". Introduction to cryptography: principles and applications. Springer. ISBN 9783540492436.
 ^ Mullen, Gary & Mummert, Carl (2007). Finite fields and applications. American Mathematical Society. p. 112. ISBN 9780821844182.
 ^ "Demystifying symmetric and asymmetric methods of encryption". Cheap SSL Shop. 20170928.
 ^ Pelzl & Paar (2010). Understanding Cryptography. Berlin: SpringerVerlag. p. 30.
 ^ Ayushi (2010). "A Symmetric Key Cryptographic Algorithm" (PDF). International Journal of Computer Applications. 1No 15.
 ^ Roeder, Tom. "SymmetricKey Cryptography". www.cs.cornell.edu. Retrieved 20170205.
 ^ Ian Goldberg and David Wagner. "Randomness and the Netscape Browser". January 1996 Dr. Dobb's Journal. quote: "it is vital that the secret keys be generated from an unpredictable randomnumber source."
 ^ Thomas Ristenpart , Scott Yilek. "When Good Randomness Goes Bad: Virtual Machine Reset Vulnerabilities and Hedging Deployed Cryptography (2010)" CiteSeer^{x}: 10.1.1.183.3583 quote from abstract: "Random number generators (RNGs) are consistently a weak link in the secure use of cryptography."
 ^ "Symmetric Cryptography". James. 20060311.