Great video! Btw, in the beginning you said that whatever bit length your input has, the padded message length would be the next 512 multiple. That is actually not fully true. That would only be true if the length of the input is smaller or equal to n*512 - 65 (if equal then k = 0). so if e.g. the input length is 960, the padded message will not be 1024 bits long, bc we would then have negative solution for k. But we cannot have a negative solution for k, so that’s why we would need to go with 1536.
Thank you so much for this video, for going through the trouble of understanding how it works and breaking it down into something meaningful! Having the example is SUPER helpful. Exactly what I was looking for.
Oh my dear god, thanks for going through this insanity :D You're making it so much better than having to go through the whole paper itself. Same goes for Chaum's video! And I do enjoy the music and the humor! :)
Brilliantly explained and illustrated ... it really is the SHA256 hash of RedBlockBlue Command: echo -n "RedBlockBlue" | sha256sum Output: f8f05f79fe0c0f876d26368bd12c08ef31617039ae3104c34f22db9c0afd3bd9
Thanks very much for the video!! I had to pause several times but I now understand better the algorithm. I also like that you show screenshots of the standard, it is a gentle introduction. I have some suggestions: - Use namespaced fonts. This avoid the misalignment of 10:34 - Do you make the animations using Manim? In this case would be great that you share the source code :)
Thanks for making this video. It was nice to see all the steps actually laid out and what a crazy series of mathematical knots the algorithm ties the input data up in. (Also, for future videos, it would be worth normalizing audio volume up, mastering up, or running some different compression).
If you do the bitwise addition of Sigma0 shown at 07:24 then the result I found is 00000011100011111110100110110000. Would you please explain if there is sth wrong ?
Yep, you're correct. I believe I used the correct sum going forward though so the error doesn't carry forward through the rest of the steps. Good spot.
Not to be "that guy" but in your initial values for RedBlockBlue, you have different values for the two capital Bs. Do you remember if you used the values as shown for your calculations or were the correct values used?
7:24 when making addition modulo 2 for sigma0: Is the result shown correct? ("00000001 10001111 11101001 00000101") In my calculation it should be ("00000011 10001111 11101001 10110000")
Great explanation. The easiest to understand from what Ive seen on TH-cam so far. But I dont quite get how the looping works... Are all the iterations added to eachother at the end?
Why wouldn't you say modulo to 32nd? How would modulo prevent it from being greater than 32 bits? That is the only reason for the modulo portion, correct?
What will happen if the text we are trying to hash is 504 bits long? You don't have 64 bits to represent the length of the text in binary to be able to add to the end of the binary for it to be 512 bits in length. Your hash will instead be 568 bits long.
Yes, as a hashing function is many-to-one relationship, and involves a finite number of outputs given an infinite domain - if you are interested in this more, you might want to read up on hashing functions, hash maps and most importantly, how a function deals with "collisions" - which are what you outlined, hashes that are the same but given different outputs. :)
3:59 we still doing stuff allways same. we can reverse. we not even need calculate those if it allwats start 2 then 3 then 5. we allways have those "hashes"
Thanks for the explainations. However the music is very distracting. If I want to listen to music while learning I would just have a video in the background.
Question: at 7.23, how can you perform an xor on three inputs? There are only two bits available. I tried doing an xor function on the first two 32 byte numbers and then that output and the final input, and it still did not yield a correct answer??
what if some one uses the final hash and applies these all same operation in a reverse manner and get to the initial input?? (i know doing these operation in reverse will require hell lot of brains but this might be possible ?)
Imagine SHA-256 as a machine that takes your input, grinds it up into microscopic pieces, and produces a unique "dust pattern" (the hash). While you can see the dust pattern, it’s impossible to reconstruct the original object because: Pieces of the original were destroyed during the grinding process (irreversible steps like mixing and modular arithmetic). The dust pattern doesn’t retain enough information to rebuild the original.
Do you mean: Given a 256 bit output, find the input? No this is not possible, SHA256 (as with all cryptographic hash functions) is a 'one-way' function' meaning its impossible to invert (go google those terms and look at wiki if you're unfamiliar). To convince yourself this is true just look at the inner workings of the algorithm: it's composed of several 'mini' one-way functions such as bit-wise addition mod 2 (i.e. we pass the bits through an XOR gate) if the output is 1 then the input is either 01 or 10.. we can't even invert this function! Same goes for 'shift' function in the video, SHIFT3(11011100) = 00011011... those first 3 bits of the input could be anything and still give same output (b/c they're set to zero regardless) so we cannot invert this mini function either
@@redblockblue thank you for the response. I had a challenge to find a string that returns something with the substring b00da when passed through the Sha256. I'm no criptographer, I had to brute force it
10:18 well using prime number those are allways same and function ch result same thing or is efg change every step. hope fully. make no sende otherwise LOL
Yep, although that may sound dodgy it’s not an issue, the algorithm is completely described in detail and any ‘random’ numbers are generated in a natural way (fractional part of sqrt(2), etc.) and not just ‘hey, use *this* ‘random’ number. They have planted back doors into publicly used algorithms before though, watch the vid in description from computerphile
When it says (t-15) or (t-7) t is the loop from 16-63. t is going through the loop, when solving w16, t is 16 so w16 -15 = w1, if its w38 for example then its w38-15 = w23 if u get it?
If the n is number of blocks youre talking about then you have more than one block, follow the same steps just in the final when youre adding h0 = h0 +a Then you take h0 from the previous block and use the new a from the next block
Great video!
Btw, in the beginning you said that whatever bit length your input has, the padded message length would be the next 512 multiple. That is actually not fully true. That would only be true if the length of the input is smaller or equal to n*512 - 65 (if equal then k = 0). so if e.g. the input length is 960, the padded message will not be 1024 bits long, bc we would then have negative solution for k. But we cannot have a negative solution for k, so that’s why we would need to go with 1536.
Ah yes ofc, I'll pin your comment so others don't miss that. Thanks!
@@redblockblue
Alright, great. But really bro..your video was fantastic, good job brother! Keep it up!👍🔥
Btw, do you have Twitter or tg?
0:36
▶️⏯️🎦🆚◀️
@@redblockblue3:25
Love this type of video that goes into the meat of the algorithms instead of speaking abstractly. Thank you for this and well done!
Yep, that’s the style I’m going for with this channel, there are far too many channels using only analogies and never going deeper than that
Only Video of Real SHA 256 algorithm implementation. Thank you for this.❤
this is the best explanation you will find on youtube.
I searched this video thinking maybe I can reverse engineer this algorithm but turns out I have to give up on it😂😂
Why? Where was proble you ran in to
@@pranavsuthar16 - Because, wtf is this guy talking about?
@@borntosucceed1667 I am sure this guy saw sha256 on stake(online casino) and want to win it
Deep down, i started watching why cant we crack, EOD i just hardly understood the algo
@@pranavsuthar16 There is not a way to determine many of the bits dropped. Like in the maj() function, if the output is 1, it could be 101, 111, etc.
Thank you so much for this video, for going through the trouble of understanding how it works and breaking it down into something meaningful! Having the example is SUPER helpful. Exactly what I was looking for.
Oh my dear god, thanks for going through this insanity :D You're making it so much better than having to go through the whole paper itself. Same goes for Chaum's video! And I do enjoy the music and the humor! :)
Yes, really great vid! Maybe we could remove the music. Sometimes its a bit hard to listen to with headphones.
Great video, you're really underrated for the amount of effort you put into this.
Very good walk through to demonstrate SHA256 under the hood. Awesome mate.
Amazing video. I was able to fully code the algorithm with the help of this explanation. Thank you!
This guy deserves more subscribers!!
The most in depth video I’ve seen. Well done!
Thanks for using those book snippets, after reading them and watching your presentation made it very clear, thank you
Brilliantly explained and illustrated ... it really is the SHA256 hash of RedBlockBlue
Command:
echo -n "RedBlockBlue" | sha256sum
Output:
f8f05f79fe0c0f876d26368bd12c08ef31617039ae3104c34f22db9c0afd3bd9
Great video for sure! Very nice, simple explanation.
Good job!
Best one untill NOW..... Hats off
Thanks for the video, best explanation available on youtube
you teach in a better way i have seen anyone else, thank you so much when is the video on the ethereum white paper coming out?
Wow, Thank you so much. Truly no bs.
Thanks very much for the video!! I had to pause several times but I now understand better the algorithm.
I also like that you show screenshots of the standard, it is a gentle introduction.
I have some suggestions:
- Use namespaced fonts. This avoid the misalignment of 10:34
- Do you make the animations using Manim? In this case would be great that you share the source code :)
My head has just fallen off.. great work.
Thanks for making this video. It was nice to see all the steps actually laid out and what a crazy series of mathematical knots the algorithm ties the input data up in. (Also, for future videos, it would be worth normalizing audio volume up, mastering up, or running some different compression).
Amazing video.
Your pedagogy skills are off the charts.
... but the music man ..............
First 2 min of the video is already better than me reading for 30 min on wiki
hey why you stopped making videos ?
Amazing video, exactly what I was looking for.
the best explanation
If you do the bitwise addition of Sigma0 shown at 07:24 then the result I found is 00000011100011111110100110110000. Would you please explain if there is sth wrong ?
Yep, you're correct. I believe I used the correct sum going forward though so the error doesn't carry forward through the rest of the steps. Good spot.
I was having the same issue, appreciate this comment!
Encountered the same thing. Glad I'm not crazy
this man deserves the subscribe and the like
Great video!!!
hmm I don't get it, why creating initial hash values at 3:28 introduces randomness? if we know, which prime numbers we are taking?
Best explanation ever !!
very interesting, cant wait to implement it 😋
insane explanations thanks man!
Great video. Thank you for the content. Can you give the link to the paper you are referencing in the video?
Would you provide a resource to the pdf you keep referencing in the video?
Which editing software you used ?
OMG
this was the best
nice explanation i love it
Bro which editing software you used to edit this video ?
What is the source of the document you show screenshots of?
Not to be "that guy" but in your initial values for RedBlockBlue, you have different values for the two capital Bs. Do you remember if you used the values as shown for your calculations or were the correct values used?
7:24 when making addition modulo 2 for sigma0:
Is the result shown correct? ("00000001 10001111 11101001 00000101")
In my calculation it should be ("00000011 10001111 11101001 10110000")
I agree, I also got 00000011100011111110100110110000
Can you tell me the name of the book from which you have been explaining in the video?
Did you find it? I'm also looking for it
Thank you
could you mention the name of a book you follow
Great explanation. The easiest to understand from what Ive seen on TH-cam so far. But I dont quite get how the looping works... Are all the iterations added to eachother at the end?
This out of this world
thank you for existing
I appreciate that
Great video, Thank You
Why wouldn't you say modulo to 32nd? How would modulo prevent it from being greater than 32 bits? That is the only reason for the modulo portion, correct?
brain usage 100%, alert death imminent😂😂
This was perfect, thank you!
amazing video
Great video. At 7:18 the first 2 bytes of the sigma_0 result should be 03 not 01.
8:50 - why do we only go through that for loop once? What does t=0 to 63 repreent what is the 't' in this case?
when you're a not a programmer and tries to understand sha256
What's the name/link of the paper you used?
What will happen if the text we are trying to hash is 504 bits long? You don't have 64 bits to represent the length of the text in binary to be able to add to the end of the binary for it to be 512 bits in length. Your hash will instead be 568 bits long.
you will then need to extend it it 1024 I guess
@@kyrylopisariev9791yes exactly
Have you tried convert the text into shingles/ tokens? In that way, you avoid having text longer than 504 bits
@@diogocardoso265 How do you do that?
Can someone tell me what all I need to have a knowledge of in order to fully understand this video ?
really nice video. Thank you for creating it
One thing I dont get is, since every oitpit is the same lenght, can there be 2 strings with the same output?
Yes, as a hashing function is many-to-one relationship, and involves a finite number of outputs given an infinite domain - if you are interested in this more, you might want to read up on hashing functions, hash maps and most importantly, how a function deals with "collisions" - which are what you outlined, hashes that are the same but given different outputs. :)
yeah but there are so many gajillions of outputs, good luck finding two strings that give the same output
3:59 we still doing stuff allways same. we can reverse. we not even need calculate those if it allwats start 2 then 3 then 5. we allways have those "hashes"
Love it, thank you for video!
Legend ❤
This is more complicated than anything I came across 😢
what paper are you using?
Wonderful video my dear friend
I urgently need the presentation file you used please
..
nvlpubs.nist.gov/nistpubs/FIPS/NIST.FIPS.180-4.pdf
Great Video!
Thanks for the explainations. However the music is very distracting. If I want to listen to music while learning I would just have a video in the background.
8:05 are those calculated all original values or with answer we got so order is important LOL. i bet original numbers
Where is the document that is referenced in this video?
Question: at 7.23, how can you perform an xor on three inputs? There are only two bits available. I tried doing an xor function on the first two 32 byte numbers and then that output and the final input, and it still did not yield a correct answer??
I found you could do xor in python using the ^ symbol, but it produced the answer: 00000011100011111110100110110000, which is incorrect
@@EwarRobI think the content in the video is wrong, I get the same result as you in a different programming language!!!
I have a question, Can you explain this to me? I have the character "耀". What are the steps to encode this character? It's not in the ascii encoding.
yes it is
if it wasnt then we couldnt see it
man the audio is very low, but amazing video
what if some one uses the final hash and applies these all same operation in a reverse manner and get to the initial input?? (i know doing these operation in reverse will require hell lot of brains but this might be possible ?)
Knowing all the steps why can't people work backwords to get the original string?
Imagine SHA-256 as a machine that takes your input, grinds it up into microscopic pieces, and produces a unique "dust pattern" (the hash). While you can see the dust pattern, it’s impossible to reconstruct the original object because:
Pieces of the original were destroyed during the grinding process (irreversible steps like mixing and modular arithmetic).
The dust pattern doesn’t retain enough information to rebuild the original.
can you show us how to reverse it?
10:50 how is he calculating this binary number. I still don’t quite understand
GOAT!!!!
I need a mathematics English teacher 😂
Can you do the reverse example? getting a string to get a determined value from the function?
Do you mean:
Given a 256 bit output, find the input?
No this is not possible, SHA256 (as with all cryptographic hash functions) is a 'one-way' function' meaning its impossible to invert (go google those terms and look at wiki if you're unfamiliar).
To convince yourself this is true just look at the inner workings of the algorithm: it's composed of several 'mini' one-way functions such as bit-wise addition mod 2 (i.e. we pass the bits through an XOR gate) if the output is 1 then the input is either 01 or 10.. we can't even invert this function! Same goes for 'shift' function in the video, SHIFT3(11011100) = 00011011... those first 3 bits of the input could be anything and still give same output (b/c they're set to zero regardless) so we cannot invert this mini function either
@@redblockblue thank you for the response. I had a challenge to find a string that returns something with the substring b00da when passed through the Sha256. I'm no criptographer, I had to brute force it
10:18 well using prime number those are allways same and function ch result same thing or is efg change every step. hope fully. make no sende otherwise LOL
great 😇
bạn có tài liệu như ở trong video không, tôi hiện đang rất cần nó, cảm ơn
3:25 ok i found myself solving Rubic's cube and thinking about what I can implement on my website 😅
why 03.51 play
6=0110 should 00110110
a=1010 should 01100001 give me guidance on where I need to study?
sha 256 not for crypto, only whitepaper, crypto using BLAKE-256 from Daniel J. Bernstein.
Can i use this for completing my school project
You can use it for whatever you’d like 👍
@@redblockblue thanks mate
3:46, why are the online decimal to binary tools inaccurate? They give me 0.00000010110100011001
What do you mean? Perhaps you calculated incorrectly.
Correct algorithm is: (**Psuedo code)
n = 2
nSqrt = sqrt(n) = 1.4142135623730950488016887242097 ..
nDecimals = 0.4142135623730950488016887242097..
nDecimals32Bits = nDecimals * (2^32)
hexValue = hex(nDecimals32Bits) = "0x6a09e667"
binaryValue = 01101010000010011110011001100111
Can u do one for ripemd160?
Nice vidéo !
SHA-256 algorithm designed by the US National Security Agency, is this correct??
Yep, although that may sound dodgy it’s not an issue, the algorithm is completely described in detail and any ‘random’ numbers are generated in a natural way (fractional part of sqrt(2), etc.) and not just ‘hey, use *this* ‘random’ number. They have planted back doors into publicly used algorithms before though, watch the vid in description from computerphile
can u do the sha3 please?
If I am calculating W(16), on which bit I will have to apply the sigma0 and sigma1?
Can anyone tell me?
When it says (t-15) or (t-7) t is the loop from 16-63. t is going through the loop, when solving w16, t is 16 so w16 -15 = w1, if its w38 for example then its w38-15 = w23 if u get it?
what would we do if our N was more than 1
If the n is number of blocks youre talking about then you have more than one block, follow the same steps just in the final when youre adding h0 = h0 +a
Then you take h0 from the previous block and use the new a from the next block
thanks@@hyxl3r254
only understood first 3 mins
Only problem this video has is the low volume even with headphone
I guess you need to change your headphones
you are probably going deaf
The frequencies carrying this recording are pretty low, could have used more mid/high, you should in any case try a better pair of headphones!
Your ears are dying
i now understand why its impossible to decode the output of hash256
This video is good, but the music is so distracting.I had to stop after a bit
Is anyone else unable to reproduce that T2 value? Following the steps up to it I instead get
11110100 01001111 01010010 00011001
Encryption built by the government in the NSA but Bitcoin totally wasn't sure
Impossible, even for quantum computers to crack SHA-256??