From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
RichardJennings

SSL TLS Support

Status: Completed

Available in LabVIEW 2020 and later. The TLS functions are available in the Functions > Data Communication > Protocols > TCP > Transport Layer Security (TLS) palette.

LabVIEW needs native SSL/TLS support for the TCP primitives. The HTTP functions support it (see \vi.lib\httpClient\ConfigSSL.vi). There are several great LabVIEW native MQTT libraries that could be commercially usable if there was native SSL/TLS support. Not having this functionality for the TCP primitives makes LabVIEW a poor choice for an IoT platform.

32 Comments
Darren
Proven Zealot
Status changed to: Completed

Available in LabVIEW 2020 and later. The TLS functions are available in the Functions > Data Communication > Protocols > TCP > Transport Layer Security (TLS) palette.

ctennies
Member

Ok so now TLS is natively supported.  What about SSL?  I am not an expert on network comms so I hope I am just missing something obvious.  I have been using encryption compendium for labview to do my SSL but it is expensive.  If there is some way I can do SSL with the new TLS functions could someone point me in the right direction.  the 2 examples that ship with 2020 have not helped me thus far.

 

thanks

ctennies
Member

forgot to mention encryption compendium for labview does not support 2020 yet - they "LVS" expect that out in the august time frame.  I tried the version that does work for 2018 on 2020 and they are right - no go.  they claim to always be about 3 months behind the labview release

rtollert
Member

TLS is the new SSL. When SSLv3 was revised to fix security issues, the resulting protocol was not called SSLv4, it was TLSv1.0.

 

This is not a recent change, either. TLSv1.0 was released in 1999.

 

The term SSL is still used a lot, and it rolls off the tongue better than TLS. And OpenSSL never changed its name, etc. The fact remains that the literal SSL protocol is today considered highly insecure and should never be used except for legacy deployments where you can’t help it.

 

Accordingly, the LabVIEW 2020 documentation has been modified in places to refer to “TLS/SSL” where it previously referred to “SSL”.

ctennies
Member

thank you for that clarification.  for what I am doing I need to be doing SSL over raw tcp.  so I take it the new TLS functions wont help me and I need to stay with encryption compendium.  Is this something I could do with Open SSL instead ?  I will have to look at it.  thanks again

ctennies
Member

I get a bad cipher error at the "Start TLS Function.vi"and am using the same .PEM file I have always used with encryption compendium.  I realize this is not a troubleshooting venue here so if you or someone can point me to documentation to help me sort that out it may do the trick.  thanks again

rtollert
Member

Sight unseen, you might see that if your certificate uses MD5.

ctennies
Member

I believe it does - thank you

rtollert
Member

You probably already know this, but in the interests of full disclosure — MD5 has been considered insecure for certificate validation purposes since before 2005. You really should get new certificates with eg SHA2 if the peer supports it.

ctennies
Member

Thank you - I will talk to the people on the other side of the wire - this helps alot