LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

HTTPS Client with TLS1.2 for LV2012sp1 in Windows XP

Highlighted

Ok anyone who can manage to contain their laughter for a minute, help me out with this.

I need exactly what's in the title. Due to the deprecation of TLS1.0 and SSL3, we're disabling both on our web server that receives status information from hundreds of systems across the country via HTTPS. Some of the systems run Windows 7, some Windows XP. All of them run applications built in LV 2012sp1.

In the past we've used the NI HTTP client VIs, which work well, and still work for some (?) Win7 systems. They don't work for the Windows XP systems. Are these VI's just a wrapper for the OS's HTTP client (IE)?

We've also been down the .net WebRequest path, but from what I can tell the webclient class doesn't support any security protocols past TLS1.0, at least not in .net 2.0, and the HTTPClient class wasn't introduced until .net 4.5, which LV doesn't support, at least not in 2012 sp1.

Lastly, we're considering the Encryption Compendium being offered in the JKI package manager, but it's 629 pounds, and if there's a way to do this without it, it would be preferred.  Also we're not sure it would work with the given constraints.  Has anyone used it/know anything about it?

Any help is appreciated.

0 Kudos
Message 1 of 3
(1,407 Views)
Highlighted

In doing some research on your issue, I noticed that you were able to find a solution on Lava. I wanted to check with you and see if the answer from their forum (using wget) was sufficient or if there is anything else you were looking for! Including the link to the other forum below if anyone else finds this and is looking for a solution.

 

https://lavag.org/topic/19894-https-client-with-tls12-for-lv2012sp1-in-windows-xp/

 

Best,

 

Chris D. | Applications Engineer | National Instruments

0 Kudos
Message 2 of 3
(1,348 Views)
Highlighted

It was a sufficient push in the right direction.  I ended up writing wrappers to execute wget using the built in command line executor to do http(s) gets and posts (files).  I also wrote a http(s) downloader to execute wget using .net process classes to parse standard error using a standarderrorreceived callback event which then feeds download status information into a queue to let the caller know how the download is going.  This is useful for large downloads.  The implementations are still being tested, but they look promising.

0 Kudos
Message 3 of 3
(1,340 Views)