<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">AES256 ? Maybe some of the stronger
SHA algorithms?<br>
<br>
<br>
<br>
<br>
<br>
On 04/24/17 13:42, Jeff Archer wrote:<br>
</div>
<blockquote
cite="mid:CAB1rkZBLe8yJv+qBAPN5fNjCuG_OFxwLcx2kW5PB3vGxcZ4jQQ@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_default">I think this is a silly question but
I still would like to get a knowledgeable and experienced
confirmation of my thinking.</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">My client is a custom application and
as such only needs to communicate with specific servers for
specific purposes. I think it makes sense for my client to
only support the specific protocol that my server will use,
ECDHE-RSA-AES128-GCM-SHA256. Does this sound reasonable or
should I also include others as well?</div>
<div class="gmail_default"><br>
</div>
<div class="gmail_default">My thinking is that if the servers
are changed one day, it would only be for increasing security
and thus I will probably need to update to latest OpenSSL and
so will be updating my app at this time anyway. Also, since
they are my companies servers, I will be notified ahead of
time that change is coming.</div>
<div>
<div class="gmail_signature">
<div dir="ltr">
<div>
<div dir="ltr">
<div>
<div dir="ltr">
<div><span><br>
</span></div>
<div><span>T
<div class="gmail_default">hanks,</div>
</span></div>
<div><span>
<div class="gmail_default"></div>
Jeff </span><br>
<br>
<br>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
<p><br>
</p>
</body>
</html>