[Tutorial] on making a Password Checker (Easy,Fast!)

[Reapism]

Steps:
1.) Open Visual Basics/Studio 2010
2.) Make a new Windows Form Application..
3.) Drag in a Textbox and a Button into the form.
4.) Double Click the button to open it's coding and write this below.

If Textbox1.Text = "YourPasswordHere" Then
Form2.Show() 
Else MsgBox("Incorrect Password.") 

'Where form2 is you can make anything happen when the password is entered. Form2 should be your main form
'This Else statement means anything other then the password will result in this messagebox appearing when the user clicks the button.

Tips: Textbox1 is the default name of the textbox. You can change it and common Abbreviation for it is Txt
The button Abbreviation is Btn


It's really just the shortening!

I am making this tutorial dedicated to the wonderful community on this website, and I wish to pursue in helping people like they helped me. Starting my first tutorial here.

I have only tested this on Visual Studio 2010, This may work on visual basics 2008


If you like this tutorial, and you like my work Please leave your support! If you want more simple tutorials, I will be willing to make them for those who request them. Please remember! Making these tutorials is a Hobby and is done at school. I may not get too all if it gets really full. Don't hesitate to ask below!

[jmcilhinney]

Code examples and the like should be posted in the VB.NET CodeBank forum, with this forum used for asking questions.

[Reapism]

Could someone move it, Or I have to do it manually.

[jmcilhinney]

Use the Report Post icon on your post to send a message the mods requesting that it be moved.

[ThomasJohnsen]

A word of warning though: as you may have read, including a password in program-code, can be a bad idea. A person determined to get your password, can decompile your code and read it pretty easily. Thus it is costumary never to save passwords, but rather to save for instance a hash-code of the passwords.
Your code can easily be made to accomodate this practise though, should you choose to investigate it further in the future.

[Half]

Leave the password in the code but don't use it. In fact add an array of millions of passwords and call it OneOfMany. It will also make the exe more C++ish by being several hundred kilobytes large instead of the typical puny several Ks - yeah, users are impressed by size.

Making things look easy (to hack) is like smiling - the more you do it, the more people get confused.

[Reapism]

Lol! This is supposed to be the most simplistic I really really like your idea though.

[Reapism]

Is it really that bad?? I mean people could Decompile the .exe or what. What would be your suggestion?

[ThomasJohnsen]

Is it really that bad?? I mean people could Decompile the .exe or what. What would be your suggestion?

There is no golden solution. People can decompile an .exe and find out what stored data contains, but in many cases, there is no reason for a hacker to try and circumvent your password, unless the software contains access to something of value to her/him. And there aren't that many hackers out there anyways - at least that's my impression.
Keep using what you feel comfortable with and when/if you start creating something that may grant access to sensitive/valuable information, start looking into added safety. There are links here on how to encrypt information with passwords or how to store passwords using hash-codes to avoid storing actual damaging information, that could be used by gain access (when you feel like it, hashing passwords is a good place to start - encrypting data is a much bigger area with lots of information on various algorithms, and it is a big area to investigate).

[dunfiddlin]

And there aren't that many hackers out there anyways - at least that's my impression.

That's kinda what they want you to think though, ain't it? There are huge numbers of hacking attempts made every minute but their targets are financial institutions, Governments and law enforcers from whom there is something worthwhile to gain, not individual applications on individual PCs.

Having said that, passwords are ridiculously overused which merely makes them easier to hack. If you've got a hundred passwords to remember just to visit your favourite websites, for example, it's inevitable that you'll fall into the habit of using the same one multiple times or storing them in plain sight.

And the truth is that any well-equipped hacker will break through any single level system in a matter of moments if they are so minded, whether or not you've given them the additional help of including the password in the code. There is little real difference between a single level password and no password at all.

[jmcilhinney]

Is it really that bad?? I mean people could Decompile the .exe or what. What would be your suggestion?

I wasn't going to comment but now that we're going down that road, your solution over-simplistic. Follow the CodeBank link in my signature and check out my WinForms Login thread to see what I would consider about the simplest option viable. Even then, it doesn't include hashing of the passwords stored in the database, which would be pretty much obligatory. There's also nothing about how to create the credentials in the first place, but registration would be a slightly different matter.

[Joacim Andersson]

Moved to the CodeBank forum.