唯一可以工作的是(如果我们提到密码只是散列，没有添加任何类型的盐来防止重放攻击，如果是这样，你必须知道盐)顺便说一句，得到一个字典攻击工具，许多单词，数字等文件，然后创建两行，一行是单词，数字(在字典中)，另一个是单词的散列，并比较散列，如果匹配你得到它…

这是唯一的方法，不用进行密码分析。

MD5是一个加密(单向)哈希函数，因此没有直接的方法来解码它。加密哈希函数的全部目的就是你不能撤销它。

您可以做的一件事是使用蛮力策略，即猜测哈希了什么，然后使用相同的函数哈希它，看看它是否匹配。除非散列数据非常容易猜测，否则可能需要很长时间。

不。MD5不是加密(尽管它可能被用作一些加密算法的一部分)，它是一个单向哈希函数。作为转换的一部分，大部分原始数据实际上“丢失”了。

Think about this: An MD5 is always 128 bits long. That means that there are 2128 possible MD5 hashes. That is a reasonably large number, and yet it is most definitely finite. And yet, there are an infinite number of possible inputs to a given hash function (and most of them contain more than 128 bits, or a measly 16 bytes). So there are actually an infinite number of possibilities for data that would hash to the same value. The thing that makes hashes interesting is that it is incredibly difficult to find two pieces of data that hash to the same value, and the chances of it happening by accident are almost 0.

A simple example for a (very insecure) hash function (and this illustrates the general idea of it being one-way) would be to take all of the bits of a piece of data, and treat it as a large number. Next, perform integer division using some large (probably prime) number n and take the remainder (see: Modulus). You will be left with some number between 0 and n. If you were to perform the same calculation again (any time, on any computer, anywhere), using the exact same string, it will come up with the same value. And yet, there is no way to find out what the original value was, since there are an infinite number of numbers that have that exact remainder, when divided by n.

That said, MD5 has been found to have some weaknesses, such that with some complex mathematics, it may be possible to find a collision without trying out 2128 possible input strings. And the fact that most passwords are short, and people often use common values (like "password" or "secret") means that in some cases, you can make a reasonably good guess at someone's password by Googling for the hash or using a Rainbow table. That is one reason why you should always "salt" hashed passwords, so that two identical values, when hashed, will not hash to the same value.

一旦一段数据通过哈希函数运行，就没有回头路了。

不直接。由于鸽子洞原理，有(可能)不止一个值散列到任何给定的MD5输出。因此，你不能肯定地扭转它。此外，MD5是为了使查找任何这样的反向哈希变得困难(然而，已经有产生冲突的攻击-也就是说，产生两个哈希到相同结果的值，但您无法控制最终的MD5值是什么)。

但是，如果将搜索空间限制为长度小于N的普通密码，则可能不再具有不可逆性属性(因为MD5输出的数量远远大于感兴趣域中的字符串数量)。然后，您可以使用彩虹表或类似的反向哈希。

MD5有它的弱点(见维基百科)，所以有一些项目，试图预先计算哈希值。维基百科也暗示了其中一些项目。我所知道(并且尊敬)的一个是ophrack。您不能告诉用户他们自己的密码，但您可以告诉他们一个有效的密码。但我想:还是给他们寄个新密码吧，以防他们忘了。

在这里可以看到所有其他的答案，关于它如何以及为什么不可逆，以及为什么你不想这样做。

为了完整起见，这里有彩虹表，你可以在上面查找可能的匹配。不能保证彩虹表中的答案是用户选择的原始密码，这样会使用户非常困惑。

同样，这也不适用于咸散列。许多安全专家都建议用盐腌制。