<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<tt>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.<br>
<br>
-Ben<br>
</tt><br>
<div class="moz-cite-prefix">On 07/28/2016 06:19 AM, R-D intern
wrote:<br>
</div>
<blockquote cite="mid:1469704795494-67595.post@n7.nabble.com"
type="cite">
<pre wrap="">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: <a class="moz-txt-link-freetext" href="http://openssl.6102.n7.nabble.com/different-encrypted-text-for-the-same-plain-text-message-tp67595.html">http://openssl.6102.n7.nabble.com/different-encrypted-text-for-the-same-plain-text-message-tp67595.html</a>
Sent from the OpenSSL - User mailing list archive at Nabble.com.
</pre>
</blockquote>
<br>
</body>
</html>