+- Hack Forums (https://hackforums.net)
+-- Forum: Tech (https://hackforums.net/forumdisplay.php?fid=444)
+--- Forum: Coding (https://hackforums.net/forumdisplay.php?fid=151)
+---- Forum: Software Development (https://hackforums.net/forumdisplay.php?fid=118)
+---- Thread: [.NET] VB.NET Login & Registration System PHP SQL [Semi beginner] (/showthread.php?tid=4609918)
VB.NET Login & Registration System PHP SQL [Semi beginner] - +Haze - Dec 30, 2014
The newest version of this tut.
https://hackforums.net/showthread.php?tid=4610630
because the thread is a shitstorm atm.
* - Known Alias - Dec 30, 2014
Nice tut bro! I'm totally gonna put time into reading this in a few minutes :)
* - Matt AH - Dec 30, 2014
Good tutorial for the beginners just picking up the basics. Easy to read and enjoyable with a powerful concept that can be widely used.
Great job 👍
* - +Haze - Dec 30, 2014
(Dec 30, 2014 01:16 AM)Known Alias Wrote: Nice tut bro! I'm totally gonna put time into reading this in a few minutes :)
Thanks m8
(Dec 30, 2014 01:21 AM)Matt AH Wrote: Good tutorial for the beginners just picking up the basics. Easy to read and enjoyable with a powerful concept that can be widely used.
Great job 👍
Thanks man, means a lot :) Hope some can learn from it.
* - Nikey646 - Dec 30, 2014
SQL Injection warning, always use Prepared Statements when handling user data of any time.
Example Injection Vuln:
Code
$sql = "Insert Into tblLogin(Username, Password) Values('$user', '$pass');";If enough people want me to, i can brush up on MySQLi (I learned C# from php, unlike Haze doing php from C#), and show a Prepared Statement example.
P.S Please don't make a tutorial then purposely give highly vulnerable code...Code which isn't 100% secure is fine, but this code can be injected simply by capping
Code
';*SQL Statement Here*--Otherwise, besides the bad habbits related to the web-side of the code, good tutorial~
* - +Haze - Dec 30, 2014
(Dec 30, 2014 01:41 AM)Nikey646 Wrote: SQL Injection warning, always use Prepared Statements when handling user data of any time.
Example Injection Vuln:
Code$sql = "Insert Into tblLogin(Username, Password) Values('$user', '$pass');";
If enough people want me to, i can brush up on MySQLi (I learned C# from php, unlike Haze doing php from C#), and show a Prepared Statement example.
P.S Please don't make a tutorial then purposely give highly vulnerable code...Code which isn't 100% secure is fine, but this code can be injected simply by cappingCode';*SQL Statement Here*--
Yes I'm very much aware of that. I said that in the beginning of the tutorial. I did this mainly for the newbies. For some this can be too much to take it all at once. I tried to keep it simple, and I feared using a prepared statement will only confuse the people trying to learn even more.
In the beginning of the thread I even recommend against using this, as it's just for learning purposes.
Apart from that my PHP is not as strong though, and yes I wouldn't mind you teaching me a thing or two. After I've had some sleep lol
* - LynS - Dec 30, 2014
thanks for the tutorial . Really help me out !
* - Tedd - Dec 30, 2014
Besides the obvious SQLi vulnerabilities, very good tutorial for starters wanting to use database logins (instead of a fucking MySQL api).
Bookmarked, will definitely link later.
* - +Haze - Dec 30, 2014
Thanks for the nice messages to the two people above me. Uhm, I might add a version that is not vulnerable to SQLi injection if the people this thread was aimed at request it.
* - Only3 - Dec 30, 2014
(Dec 30, 2014 01:41 AM)Nikey646 Wrote: SQL Injection warning, always use Prepared Statements when handling user data of any time.
Example Injection Vuln:
Code$sql = "Insert Into tblLogin(Username, Password) Values('$user', '$pass');";
If enough people want me to, i can brush up on MySQLi (I learned C# from php, unlike Haze doing php from C#), and show a Prepared Statement example.
P.S Please don't make a tutorial then purposely give highly vulnerable code...Code which isn't 100% secure is fine, but this code can be injected simply by cappingCode';*SQL Statement Here*--
Otherwise, besides the bad habbits related to the web-side of the code, good tutorial~
thats why ppl should use pdo over mysql\i
* - xNeaples - Dec 30, 2014
Just use PDO, more simple and secure for these things.
* - Marwix - Dec 30, 2014
Looks like a really good tutorial, good work +Haze.
Totally worth your night!
* - +Haze - Dec 30, 2014
(Dec 30, 2014 03:40 AM)xNeaples Wrote: Just use PDO, more simple and secure for these things.
I might add that in but I don't want to be confusing people.
(Dec 30, 2014 03:42 AM)Keiko Wrote: Looks like a really good tutorial, good work +Haze.
Totally worth your night!
Thanks there mate. I guess I can't sleep so I'll just post another tut requested by a member here.
* - Rhez - Dec 30, 2014
Thanks for taking the suggestion before :)
I'll gonna bookmark this tutorial . Thanks AGAIN
* - RandomUser123 - Dec 30, 2014
Thanks for this tut. You know how to structure a thread to make it clear. Even if its not so "secure" as login i may use it for something else..
Thank you for being so willing to help!