Re: Can you still believe aTriz words? Reopened, too many open questions
I sorta think I know the sha256 of this script.
Code:
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
Not funny, when I already posted that hash (the hash of stuff I downloaded from example.com):
An example of what a SHA-256 hash may look like (here represented in hex):
By posting a hash, you would be making a cryptographic commitment. As long as you can produce a file exactly matching whatever hash you post, nobody could later accuse you of changing the script, or substituting a different script. And yet, you would not be revealing the script.
Code:
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
By posting a hash, you would be making a cryptographic commitment. As long as you can produce a file exactly matching whatever hash you post, nobody could later accuse you of changing the script, or substituting a different script. And yet, you would not be revealing the script.
I sorta think I know the sha256 of this script.
Wait so I screwed up?Code:
e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855
@aTriz, that is the SHA-256 hash of the empty string. tspacepilot is joking that the script does not exist. Whereas you committed:
has = hex: e9474064aaeb4d07689d80952adb4d785d318fcd43947b90ec25c12450876f50. I'm not sure if I got it correct or not, I used just found one on the web.
Code:
e9474064aaeb4d07689d80952adb4d785d318fcd43947b90ec25c12450876f50
Nothing can be discerned about the script from its SHA-256 hash. (Nothing, including whether you got it correct or not. I sincerely hope you did.)