php - How to use & input Bcrypt into a database? -

So I have read this question a few times and have read all the answers. I got a semi-working system, but it broke. The problem for me is that in answer to those posts often give long, complex codes to make BCRTP - but then there is no example of how to use it, i.e., to answer the first answer -

"You can use this code like this:

  $ bcrypt = new binary (15); $ hash = $ bcrpt-> hash ('password'); $ IsGood = $ bcrypt- & Gt; Verify ('password', $ hash);   
 " 
 I input some form data How to go about (let's call it: $ user_password)  
 In addition, the following will help clarify - I'm a little unsure.  
 
 What happens inside the 15pt What do the binary function / what to do at the starting point? Does this mean round?  
 When 'good' test is done, I think $ Hood is turned into a boolean (1 = true), (0 = false). So you can continue working (or not) on login, whether it's 1 or 0, okay?  
 I'm assuming that there is a $ hash that you put in the database if so, why you can not use the same hash on the login, still use $ good quality?   
 I am very new to php and I had a sha $ password earlier) .. which is very easy to compare and comparison, if there is any relation between two (or link to conversion) Will give a more sensible answer to me or any other person who comes in the same situation.  
 
 
 
  15 means the power and 15 are very slow. Make    
 Make sure that you use this right or you will receive a serious performance penalty if you do verification or hashing often take the same time to complete both operations. Displaying a  microtime ()   15 is not favorable on your exact scenario.   
  I usually use 7 - 10. More Overkill ...   
  PS : You will find a few long posts about  SO  about  bcrypt  . Read them! In this way: Or it  
  PPS :  Local Trial: <15 Power takes approximately 3 seconds to imagine now on a shared host :) Probably will not leave under 1 second which is too long IMO.  
  Actual code :  
  // Is it available on the system? $ Availability = function_exists ('crypt') and defined ('CRYPT_BLOWFISH'); // And Now Code: $ MT = Microtim (True); // Talk of time, so we can get $ password = 'somepassword'; // password $ salt = 'pairs of pairs'; // Your salt should be valid, Docs $ Strength = 15; Calculate the formatted salt for // Strength (1-99) // Kraft $ CryptSalt = sprintf ('$ 2a $% 02d $% s $', $ power, $ salt); // $ hashed = crypt ($ password, $ crypt slot); $ password for storage; // user input $ password $ verified = verify it against copy ($ password, $ hashhead) === $ hashed; // Show the duration of this (2x as it is both in and out) echo number_ format (microgram (true) - $ MT, 6), PHP_EOL;   
  Use this document for testing.   
 Do not design your code just to test hash on each page load.  
 Verify while logged in to a user. In the rest, use some hashing system which is fast to test on every log-in page load.   
   
  
  
  
 When you have a hash with bluffish crypto, you need salt, strength and password. You add salt and strength because the glasses are required and you make a  crypt ()  compatible salt. This salt is translated by  crypt ()  and sale and strength is removed, plus hashing algorithm is based on letters 2 and 3.  
 In your database, you store the last hash value. You do not store soft softwares that you used to hash password because you must defeat the purpose. The hashpost value stores the store that requires reverse operation and check whether your plain password matches hashashad or not. Stored in the  salt , there is no need to store it.  
 When the user is registered, you have the hash password and save it. When they sign in, you confirm your password against the plain submitted in your form. There is no need to remember the hash used for hash  and it allows you to generate a random hash  It is on every hashing without taking into consideration what it is because it has returned in the hash See more on the bundle.  
  Let me know that it has come to understand.