Nothing! this is very interesting though :)

I don't think I quite get why an extremely slow hashing algorithm would help increase security? Could you review that one more time?

For our projects, we have password as varchar(50). Should we switch our passwords to be char(60) ? Can you explain why this number is important with respect to the hashing

Why does bcrypt store the salt inside the hashed password?

Are there other effective ways of handling the little snippet of concurrency issue? Or would doing something like a mutex, for example, be unnecessary for this handling?

How can we make sure a user doesn't reuse a previously used password, even though bcrypt creates a new unique hash each time?

Would we place the code for hashing the passwords in gitignore?

none right now, walkthrough in class will help