login - Really really need help..Please

[dnssetup]

The zip is a login vi. Can someone help me link the user account to a led. Example the first user account would be link to the 1st led. And the second user is link to the 2nd led, and goes on. Please, really need your help.

[altenbach]

(Who wrote this VI? Looks like all this could be done with 20% of the code. This has been written by a LabVIEW beginner who only knows text based programs. None of the controls are connected to anything and everything is done via property nodes.)

It is not clear what you want. You attached a VI with a fixed number of LEDs, but the program allows adding users for an unlimited amount of users. Something will not match up. Where, when, and how should the LEDs be shown? In a seperate VI?

Overall, the program is way too complicated for no good reason. Instead of a VI with all seperate LEDs, why not use a 2D array of a single LED and then light up the one you want?  This wold dramatically simplify the code and speed up the coding.

From a security standpoint, your program offers no security because the password file is in clear text for anyone to see. It should be encrypted. If the login fails, you should not give details (password too short, user not found, password incorrect, etc.). A simple "authentication failed" is all that's needed. Giving too much information allows partial information, i.e. the existence of a certain user name which is a security risk.

(Sorry, I no longer have access to LabVIEW 7.1.)

[dnssetup]

sry for that. Mr.Altenbach can u really please me then? By using that led, when the user keys the password, then 1st led would light up.  That led would only off when the  user keys in the password. If the 2nd user keys in password, then the 2nd led would be light up and able to see the 1st led if the 1st user dint log off. Its like and automated car park system.Can  you please help me?

[rex1030]

"Mr.Altenbach can u really please me then?"  <- I think that might be the quote of the week.

My first reaction is to create a hash table of the passwords, but I can't find a hash/encryption function anywhere in the labview libraries. Am I just looking in the wrong place?

dnssetup, its better to use local variables than write the values property of each control and indicator. Its faster. Also putting your VIs in a project makes everything a lot easier to manage. Altenbach is right, your program is way over complicated for what you are trying to do, especially the modify pass function. Also, just because you are storing things with the binary file function doesn't mean someone can't just open your "list" file in notepad and read all your passwords. I find it odd you arent using a username/password combination. You are only using a single text string. This is half the security of the other way. Also it prevents passwords from being able to be repeated. So if with your program I try to create a password it will tell me if it already exists! I just write it down and log into someone elses account. See the problem? You might want to read up on some common practices for user account authentication. Try to model your program after log ins you already use. What did it take to register? What happens when you type a password wrong once? What happens after too many incorrect passwords? Right now your security is a hackers dream... which is a bad thing 🙂

[altenbach]

As I said, I no longer have access to LabVIEW 7.1 or a version that can convert to 7.1.

What have you tried so far?

I would suggest to keep a boolean array in a shift register and switch the element corresponding to the currently logged in user to true. Switch it back to false if the user logs out. For display, you can reshape it to a 2D boolean array if you prefer that.

[dnssetup]

Can you please help in this VI? How can I improve security to it and also link to the leds?

[altenbach]

Where are the LEDs?

What is the mechanism of logging out?

What is the purpose of "ADD user (FILE).vi"?

You also should also familiarize yourself with dataflow. For example the diagram comment:

"To clean up Login and Password fields after each session"

is definitely incorrect, since there is no data dependency the control cleanup most likely happens the next time the VI runs. Code does not magically execute from left to right.

[dnssetup]

The led from the first post i meant.

You mean cancel?

The "ADD user (FILE).vi" would be for user to create account.

sorry for the trouble. Can you show me how to limit user from login registration? example; the system only accept 10 users.