Honestly, I've been watching your videos ironically because I will never be able to get a developer job due to my location and inability to complete a bachelors degree. That being said, I wanted to thank you for answering questions I've had since I started programming in a simple and entertaining way. When I was working on my associate degree, I made some programs that require logging in to an account. I always stored the passwords as plaintext. Teachers said it was bad, but they never talked about the actual way to do it. Everything I found online made it seem complicated. You didn't. So yeah, thank you and keep up the great work!
The way I usually explain hashing as a more real-life example is by using the Remainder function. It's a function that will output the same result each time, but you don't really know what the input was. The remainder of dividing 7 by 5 is 2. However, so is the remainder of dividing 12 by 5. So we don't know if 2 is the result of 7 or 12. This also helps cover the hash collisions case.
You make concepts so easy to understand! Quick question, hashing should always be done server side right? If so, should I be concerned about sending passwords in plain text from clients to server over a TCP connection?
Well, the password really isn’t sent in plain text… the password is encrypted as part of HTTPS. And if he did do a client side, you’re running the risk of advertising whatever algorithm you’re using for hashing. This video is really just an example of what you can do, what you should really do is use an existing password authentication framework. Don’t try to roll your own when plenty of good frameworks exist.
This is the best one so far, and that hash brown is a great example of a one way hash! Thanks.
So happy you liked it!
This video deserves the view count of the new video. This is fantastic for all in CS field to watch!
Honestly, I've been watching your videos ironically because I will never be able to get a developer job due to my location and inability to complete a bachelors degree. That being said, I wanted to thank you for answering questions I've had since I started programming in a simple and entertaining way. When I was working on my associate degree, I made some programs that require logging in to an account. I always stored the passwords as plaintext. Teachers said it was bad, but they never talked about the actual way to do it. Everything I found online made it seem complicated. You didn't. So yeah, thank you and keep up the great work!
I’m glad this helped you - You know you don’t need a bachelors degree. Connect with me on LinkedIn. Maybe I can get your résumé up to some people.
The way I usually explain hashing as a more real-life example is by using the Remainder function. It's a function that will output the same result each time, but you don't really know what the input was. The remainder of dividing 7 by 5 is 2. However, so is the remainder of dividing 12 by 5. So we don't know if 2 is the result of 7 or 12. This also helps cover the hash collisions case.
I like that!
Funny and informative videos thanks Ryan!
I’m glad you liked it! I hope it helps!
You make concepts so easy to understand! Quick question, hashing should always be done server side right? If so, should I be concerned about sending passwords in plain text from clients to server over a TCP connection?
Well, the password really isn’t sent in plain text… the password is encrypted as part of HTTPS. And if he did do a client side, you’re running the risk of advertising whatever algorithm you’re using for hashing. This video is really just an example of what you can do, what you should really do is use an existing password authentication framework. Don’t try to roll your own when plenty of good frameworks exist.