MD5被认为是坏的，不是因为您可以从散列中获得原始内容，而是因为通过工作，您可以生成两个散列到相同散列的消息。

不能取消MD5哈希。

在寻找哈希函数的逆函数方面，没有办法“恢复”哈希函数。如前所述，这就是哈希函数的意义所在。它不应该是可逆的，它应该允许快速哈希值计算。因此，找到产生给定哈希值的输入字符串的唯一方法是尝试所有可能的组合。这就是所谓的蛮力攻击。

尝试所有可能的组合需要花费大量时间，这也是为什么使用哈希值以相对安全的方式存储密码的原因。如果攻击者能够访问您的数据库，其中包含所有用户密码，那么无论如何您都会失败。如果您有哈希值和(理想地说)强密码，那么攻击者将很难从哈希值中获取密码。

存储哈希值也没有性能问题，因为计算哈希值相对较快。因此，大多数系统所做的是计算用户输入的密码的哈希值(这很快)，然后将其与用户数据库中存储的哈希值进行比较。

要做到这一点并不容易。这就是首先对密码进行哈希的意义。:)

你应该做的一件事是手动为他们设置一个临时密码，并将其发送给他们。

我不愿提及这一点，因为这是一个坏主意(而且也不能保证一定有效)，但您可以尝试在彩虹表(如milw0rm)中查找散列，看看是否可以通过这种方式恢复旧密码。

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输出的数量远远大于感兴趣域中的字符串数量)。然后，您可以使用彩虹表或类似的反向哈希。