Talk:Secure Hash Algorithms
![]() | Cryptography: Computer science Start‑class Mid‑importance | ||||||||||||
|
Could use some editing, but maybe some people will think some of this is a good way to explain secure hash to the nontechnical person.
A good secure hash algorithm is defined as, in the worst case of the hacker looking at your worst hashes that give away the most knowledge about what they are hashes of (the input), the hacker must do more calculations, even with good statistics and estimations, to figure out anything at all about what went into the algorithm. It is to remove all except the most meaningless pseudorandomness that would take the smartest supercomputer maximum time to learn anything about. The hacker can not use the algorithm to, even while seeing its entire source code and being able to play with it and variations of it and hook it into his best tools, find any possible input which outputs the same hash as any other input, and part of that is to not be able to duplicate the hashes that I've already given him (they give these as separate conditions since they are different difficulty). It is nonsensical, pure stupidity with extreme strategy to be the most pointless of all time, having no measurable pattern. In a word, secure hash is religion in binary. — Preceding unsigned comment added by 97.89.104.85 (talk) 02:05, 8 June 2014 (UTC)
Proposed merge with Secure Hash Standard
This article is a non-stub article, and also give brief descriptions to each algorithm, in contrast to the article to be merged/redirected here. NasssaNser (talk/edits) 08:48, 3 April 2017 (UTC)