wyUpdate.exe fails to communicate with TLS 1.1+ server

We are using wyUpdate and has been working wonderfully well for the upgrades. Yesterday however, our server booted out the TLS 1.0 connections.

As a results, our updates started to fail.

We do not use the AutomaticUpdater dll. Instead, we start the wyUpdate.exe command with flags "/quickcheck /justcheck" to check if an update is available.

As per recommendations from some earlier threads, we did try to change the wyUpdate.exe to .NET 4.0 one. Plus, we have .NET 4.5 installed on the machine. However, we still see the TLS issue when wyUpdate is trying to connect with our server. Here is the message:"The underlying connection was closed: An unexpected error occurred on a send"

Request you to please guide on how we can configure wyUpdate.exe to use TLS 1.1 or TLS 1.2.

We have fixed this issue by building a custom wyUpdate.exe targetted for .NET 4.5 with below code change.

This is done in the GetRequest function of FileDownloader.cs

<code> if (request is HttpWebRequest) { request.Credentials = hasCredentials ? new NetworkCredential(uri.UserName, uri.Password) : CredentialCache.DefaultCredentials;

// Some servers explode if the user agent is missing. // Some servers explode if the user agent is "non-standard" (e.g. "wyUpdate / " + VersionTools.FromExecutingAssembly())

// Thus we're forced to mimic IE 9 User agent ((HttpWebRequest)request).UserAgent = "Mozilla/5.0 (Windows; U; MSIE 9.0; Windows NT 6.1; en-US; wyUpdate)";

+ if (uri.Scheme == Uri.UriSchemeHttps)+ {+ ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;+ }+ }

</code>

It is working now.

Reply
Discard post