Mi Mi haaru haaru haaru kihineh adhives I have never ate thag saan i hope so too so too much yoh can you deliver a big big big big answers are are we gonna do you know know know know how many pounds in a business question and i i saw that you get a chance to make vanilla ice cream is a language and its
I completely agree, I watched so many videos trying to understand why SHA would even be used, and none of them answered it until I watched yours. And you had fantastic content through the whole video as well, so thank you.
You earned a sub. I really love the way you explain what hashing is and even gave an example on how to use it for storing passwords. I didn't even notice that it was almost 20 minutes that I was listening to your lecture. 10/10 would recommend this channel to other people again.
I had the same thing. At first I thought that this video is veeeery long. But the end come much sooner that I had hope for. Very useful information without any stupid nonsense and intros
Showing how the birthday problem is a hashing algorithm computation more directly allowed me to finally make the connection I needed. I've almost finished my applied math undergrad and com sci undergrad and no one explained these concepts so clearly! Maybe I just needed to see it presented differently, but this worked wonders for me to link my math to it.
Great explanation, Professor Sluiter. I am studying for CISSP and this saved me a lot of time and cleared up confusion from the useless study guides. Thank you!
This is a great video! Your explanation is very to the point without any fluff and presented in a way that doesn't make me wander to the next video. Thank you for the information in such a presentable way!
@@shadsluiter Nothing in particular. I know about using check sums to verify a file's integrity, and I was curious how it works. You also give a lot of contextual additional information, such as what rainbow tables are and why md5 is to be avoided, which was really helpful.
Thanks for the video Professor. Very clear explanation to follow. Hashing technique was particularly useful for us in de-duplicating big data sets. Have shared it in a video.
@@shadsluiter Well, I am a Network Engineer and Linux Engineer, I am currently exploring blockchain infrastructures, cryptocurrencies and IPv6, all of them require security. Do you broadcast live via RU-vid from time to time?
@@5gun1 here is the process of SHA256 (hashing technique used for mining bitcoins and ethereum) ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-f9EbD6iY9zI.html The complexity of it makes it nearly impossible to reverse.
@16:35 I would like to disagree about "salt" Salt is technically speaking a compound that can bind either positively charged ion or negatively charged ion except hydroxide ion (OH-) and hydrogen ion(H+). In some field salt is used as a mode of transport through bonding with adjacent ions. When the condition is right, the bonding will broken down and release the appropriate content. One example is calcium carbonate. When dissolved with hydrochloric acid, calcium is released from carbonate ions. So imagine this analogy to the hashing it is quite similar.
So in other words, whenever a service tells me that my new password is “too similar” to my old password, they aren’t hashing my passwords and basically fucking me over?
@@weltrepublik But if a password is changed by even a single letter and the hashes come out completely different, then they should have no way of knowing that's it is similar. Thus they must be saving my plain text password in order to compare. Doesn't sound like they are defending me at all.
@@Applest2oApples it's not that they're neccessarily saving it as plain text, but to make it harder to brute for hackers. fx. most people use the same password on every site, so say a hacker gets your password from another not so secure site, but doesn't exploit it in a way you notice, he now has access to everything you have. now X time later, your pasword gets "expired" on a site, and you change it to something similar, then the next time the hacker tries to login to that site, he will be denied. Now instead of starting to brute force your new password from scratch (A-Z), almost all hackers will start brute forcing through variations of the old password instead, because most people are lazy, so there's a high propability, that only 1 or 2 letters have been capitalised, or changed and etc.... so just changing a few letters will make the hackers use relative short time to brute your "new" password" (from minutes to a few days), where a totally new password will force them to start from scratch, which means the hacker basically have to be incredibly lucky to crack you new password, as long as you use somewhat secure passwords (upper and lower case, numbers and special chars, and a good lenght) the above example is also why it's important to use different passwords for each "important" site you use, and not just variations... hope it made it somewhat clearer :)
@@jankastbjerg4017 the fact that a password is similar to a previous one is besides the point, the point is the website knows what your password is, and doesn’t only have it’s hash saved
the common practical way: 1) encrypt+hash+salter 2) Data send through encrypted package 3) Unencrypt the received data 4) Check on the hash and token should return valid/true. 5) do the things... Regarding MD5, shouldn't really use it, if still insisted, must merge with add-on unique hashing algorithm to generate the only unique result. In reality, there are still tons of systems still using the MD5 hashing basis but they modified with other unique hashing algorithm.
