This of course assumes that any primitives you use are secure. The caveat being you need to have a solid handle on what buffer allocations are 'real' when you look at your code such that if you end up having to copy a password, you can be sure you're going to overwrite it. In principle, #1 seems easy because values are mutable. I've never had to create an application that requires any form of authentication but I've wondered about it for a while now as I find myself using LabVIEW for more and more as a platform where I wouldn't have previously considered it. There are likely other issues, I'm about as far from an expert in security as you can get. Keep the password out of any control/indicator such that other tasks can't use VI Server to get a refnum and generate copies of the password, register for value change events, etc.Need to make sure any temporary copies of password strings that are generated get properly 'cleaned' so the data doesn't stick around in memory.Some things come to mind that would worry me about having to handle authentication in LabVIEW. No, simply obscuring a password is not the answer. Specifically how do you secure a user interface in LabVIEW which is entering sensitive information such as a password? A recent topic on the idea exchange ( Allow 'Password' Data Type for Prompt User for Input Express VI) got me thinking about security in LabVIEW.

Labview vi password crack