@moufpuncha How hard is that to guess though? Far more often than not I come across tables named "Customers", "Employees", "Payroll". Don't every rely on security through obscurity, I know a hundred people who will tell you a false sense of security is better than no security because it's easier to forget about it.
1:22 connect.oho
B1KMusic 3 weeks ago
your code is vunerable to sql injection attacks. just sayin.
123456789robbie 3 months ago
where did that passkey came from?
manasume 4 months ago
*Looks through 80 lines of code*
*1/2 hour later*
"OH! I put 'pass' not 'password'!"
JKTCGMV13 5 months ago
@SCARHExtendedMags Or you could name it something useful and sanitize the input, eliminating the risk altogether.
dandymcgee 7 months ago
@dandymcgee You could name the temp table someting stupidly long, then it would be unlikely to guess.
SCARHExtendedMags 7 months ago
@moufpuncha How hard is that to guess though? Far more often than not I come across tables named "Customers", "Employees", "Payroll". Don't every rely on security through obscurity, I know a hundred people who will tell you a false sense of security is better than no security because it's easier to forget about it.
dandymcgee 8 months ago
@dandymcgee yeah but wouldn't you have to know the name of the table or database?
moufpuncha 9 months ago
First off, great beginner tutorial. You're really good at explaining tough concepts.
To anyone watching, just keep in mind what could happen if a user browses to:
?passkey=whocares'; DROP TABLE temp; --
ALL user input should be sanitized on arrival, and especially before performing a SQL query.
dandymcgee 10 months ago
$sql -> Lame query...
True query should be: INSERT INTO temp (code,username) values ('$confirm_code','$name')
LordOfCa 10 months ago