There are several places where a per-connection random input is introduced, with a specific goal of making encryptions of the same plaintext produce different ciphertexts (as well as other benefits). If a plaintext always produced the same ciphertext, then an attacker could make a dictionary of different observed ciphertexts and know when the same plaintext was being repeated, which violates the confidentiality property desired from the protocol. -Ben On 07/28/2016 06:19 AM, R-D intern wrote: > Hello, > I am using ECDSA-ECDHE-AES-SHA cipher suite for client -server security.I > tried understanding the mechanism handshake mechanism. What still quizzes me > is ; communication between a specific client -server for a specific session > generates different encrypted text for the same plain text message. What > leads to this? Can anybody elaborate? > Please reply. > Thanks and regards, > Suman > > > > -- > View this message in context: http://openssl.6102.n7.nabble.com/different-encrypted-text-for-the-same-plain-text-message-tp67595.html > Sent from the OpenSSL - User mailing list archive at Nabble.com. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mta.openssl.org/pipermail/openssl-users/attachments/20160728/68d2f497/attachment.html>
