Jump to content


New Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Carlos1973

  • Rank
  1. Thanks (for the sarcasm) Barand - I got that bit, but what I didn't pick up was that verify works on hashed passwords only, not unhashed ones. Still, we aren't all lucky enough to pick it all up in one morning the way you did. Also - there's a manual? Thanks Requinix - that was my problem; (note to self: password_verify is verifying the hash - not the password behind it). Rookie mistake.
  2. Thanks again - I didn't realise that password_verify() was intrinsically linked to password_hash and thought that it would do the same regardless of hashing / salting. I'll switch it back and see how I get on,.
  3. Hi, I plan to use password_hash, but at the moment I'm just storing a varchar. I changed it as part of the troubleshooting when I started getting this error, but the format has made no difference, should I change it back? Thanks for the tip on prepared statements, I'll look at it now.
  4. Hi, I am trying to set up a useername / password validation log in for a website - code below. I'm fairly new to php, so my understanding of what I have done is: config and env pick up some basic info including the servername, username, password and dbname for the connection, $_POST["username"] and $_POST["pwd"] are the values entered by the user on a previous log in page. Users is queried to bring back the data in $sql where the posted username ($userid) matches the UserName in the table. This is then checked to ensure there is one row returned - if not we go to
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.