You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- $\begingroup$ With an array of $k$ quantum computers... you could find a single MD5 preimage in about $2^{64}/k$ time; is that true? I've looked for parallel versions of Grover's, and the best I could find is $2^{64}/\sqrt{k}$ time. Do you have a reference for an efficient parallelized version? $\endgroup$poncho– poncho ♦2017-07-26 15:08:45 +00:00Commented Jul 26, 2017 at 15:08
- 1$\begingroup$ Nope! I misquoted the paper I cited. Fixed now. $\endgroup$Squeamish Ossifrage– Squeamish Ossifrage2017-07-26 15:12:49 +00:00Commented Jul 26, 2017 at 15:12
- $\begingroup$ Thanks for the reference; I had thought that was the case, now I have proof... $\endgroup$poncho– poncho ♦2017-07-26 15:16:27 +00:00Commented Jul 26, 2017 at 15:16
- $\begingroup$ When it comes to breaking a hash algorithm, I wouldn't think that finding the original input is the goal. If, for example, a site is distributing an executable binary and publishes the size and an MD5 hash of the file, the attacker's goal wouldn't be to find the original input, but would rather be to create a malicious file of the same size that produces the same hash that they could trick users into downloading and executing. $\endgroup$martin– martin2017-07-27 07:00:14 +00:00Commented Jul 27, 2017 at 7:00
- $\begingroup$ @martin: That is certainly one application! The OP's question seemed to be about recovering what the original plaintexts were, so I focused on that goal. What you describe is similar to (a), except instead of learning what the original input was, we don't care and just fill it with garbage to match a target hash, like a Bitcoin block. $\endgroup$Squeamish Ossifrage– Squeamish Ossifrage2017-07-27 07:11:15 +00:00Commented Jul 27, 2017 at 7:11
| Show 3 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
- MathJax equations
$\sin^2 \theta$
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. public-key), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you