7 Cryptography Concepts EVERY Developer Should Know

Thanks for the awesome overview. This is what I'll be teaching in my computer science courses, and I'll try to implement your node code in python together with my students.

Cryptography not for developers it's for programmer 😂

I LOVED that HMAC breakdown. I am studying for the CISSP and I like..."understood" it theoretically but I wasn't really able to connect it to an actual use case. Thanks so much for your content <3

I can’t thank you enough for this!

SHA ~ MD5

Thanks for making this easy to follow.

2:29 Not quite, you just need to reproduce the hash. In the 90s we had rainbow tables where you could search for a hash value and use its input even if it was different to the original it didn't matter as the computer only checks the hash value

I've always thought of the public key as more of a lock rather than a key. "hey here's my lock (public key), whenever you send me something, put this thing on it first because I have the (private) key to unlock it - that's the thing I don't share". Key this key that, everything is a key and it makes it super confusing.

answer : superhacker

It's too bad there are no subtitles.

Amazing video. Liked the explanation...

It be like ■■■■ ■■■■ ■■ ■■■■■ ■■ ■■■ ■■■ ■■■■ ■■ ■■■ ■■ ■■■■■■■■■■ lol 4:21

No you can just write in plan text ... then the magic blow of 💋 😘 😗 change it beautiful 😍 🤩 👌 ✨️ lol 💯 3:47

superhacker

🇨🇦 VDO suggestion: explain if encryption can be used to safely mask a voice. If a YouTuber interviews someone who a gang wants to ID, many voice masking video editors wouldn't be safe because someone who can read the program could possibly reverse the voice masking.😮
I would just use a text to voice program or a paid actor to be 100% safe with peace of mind for person interviewed, like shows like Gangland.

you could HMAC passwords instead of salting them, and it's even better because hashing alone (even with salts) is "Integrity verification" which is not the exact tool you want. HMAC however, is Authentication, which is the exact purpose of a user-password combination.

ew why js😭🤮🤢

Me: Oh this looks interesting

Me 7 minutes in: Wtf is happening 😳

I love john the ripper, how password generate

ngomong apa jir

Yeah, like theft identity...like to not be stalked by human traffickers...what else? What happened with those donations, Google?

Couldn't find anyone else who already posted this, but u said "we can do that by just prepending it to the existing string seperated by a semicolon" but u're using a colon d:^)

"superhacker" is the hash

hacker all this is fine but you have no idea how tired is one of creepy ticks sticking on one online life and just to get their balls jumping so called deliberate passwords being thrown around by hacker in this clip but there are solutions and those are within this so called encryption and shall be created

😂😂cool bro

I've tried to get a angle off hours of your videos. I'm injured can't do what I used to so I'm homeless and just want to let you know I've got nothing out of this. I've tried no it's time to die thanks for the bs guy

Appreciate it for posting! Looking for guidance: My Trust Wallet has some USDT trx, and I have the seedphrase: clean party soccer advance audit clean evil finish -tonight involve whip -action-. How to handle moving them to Kraken?

regular hashing always produces the same output for the same input since the algorithm is a deterministic mathematical function.

this means the password "password" hashed with sha256 will always produce "5e884898 etc..."

this makes passwords especially weaker ones vulnerable to lookup attacks using precomputed hash databases like rainbow tables.

a rainbow table is a giant list of common or simple passwords and their corresponding hashes.

attackers can simply search for a known hash and find the original password.

salt prevents this by adding a unique, random value to each password before hashing.

with salt, even if two users have the same password, their hashes are different since their salts are different.

additionally, the system needs to verify passwords during login, so the salt must be stored alongside the hashed password.

when a user logs in, the system retrieves the stored salt, hashes the entered password with it, and checks if the result matches the stored hash.

authentication is only possible with both the salt and the hash, adding an extra layer of security.

however, because the salt is required for verification, it must still be stored securely to prevent attackers from using it in brute-force attacks.

so while salts don’t prevent brute-force attacks, they slow them down significantly by forcing attackers to compute hashes separately for each password attempt per user, making large-scale attacks impractical.

even with billions of hashes per second, brute-force attacks on strong passwords can take years, not just days, especially when combined with slow hashing algorithms like bcrypt, scrypt, or argon2.

as for quantum computing, while it poses a future risk, it won’t make salts or hashing obsolete overnight.

current quantum algorithms like grover’s algorithm speed up brute-force attacks, but only by a square root factor.

if breaking a hash today takes 1000 years, a quantum computer could reduce it to ~30 years.

while significantly faster, it would still take a very long time, making it infeasible especially for strong passwords and with slow hashing algorithms.

public-key cryptography however is at risk from quantum attacks as shor’s algorithm is an exponential speedup and can break pkc once quantum computers reach a sufficient scale.

How is that conforming

how did it say 2025? at 1:16

Can you please make an in-depth video about how end-to-end-encryption works in, for example, messaging apps?

THis is great

Well played bro!

1:17 who's here in 2025😂