| Users re-use passwords for multiple services. |
用户为多项服务重复使用密码。 |
| If an attacker gains access to one server and can gain a list of passwords, he may be able to use this password to attack other services. |
如果攻击者获得了对一台服务器的访问权并可以获得密码列表，他就可以使用此密码来攻击其他服务。 |
| Therefore, only password hashes may be stored. |
因此，只能存储密码哈希。 |
| Secure hashing algorithms are easy to use in most languages and ensure the original password cannot be easily recovered and that wrong passwords are not falsely accepted. |
安全散列算法在大多数语言中都易于使用，并确保原始密码无法轻易恢复，并且不会错误地接受错误的密码。 |
| Adding salts to the password hashes prevents the use of rainbow tables and significantly slows down brute-force attempts. |
向密码散列添加盐可以防止使用彩虹表并显着减慢蛮力尝试。 |
| Strengthening slows both off-line brute-force attacks against stolen hashes and on-line brute-force in case the rate limiting fails. |
加强会减慢针对被盗哈希的离线暴力攻击和在速率限制失败的情况下的在线暴力攻击。 |
| However, it increases CPU load on the server and would open a vector for DDoS attacks if not prevented with login attempt limiting. |
但是，它会增加服务器上的 CPU 负载，并且如果不通过登录尝试限制加以阻止，则会为 DDoS 攻击打开一个载体。 |
| A good strengthening can slow down off-line brute-force attacks down by a factor of 10000 or more. |
良好的强化可以将离线蛮力攻击减慢 10000 倍或更多。 |
| Limiting login attempts is necessary to prevent on-line brute-force attacks and DoS via the CPU usage of the password strengthening procedure. |
限制登录尝试是必要的，以防止通过密码强化程序的 CPU 使用率进行在线暴力攻击和 DoS。 |
| Without a limit, an attacker can try a very large number of passwords directly against the server. |
没有限制，攻击者可以直接针对服务器尝试大量密码。 |
| Assuming 100 attempts per second, which is reasonable for a normal web server, no significant strengthening and an attacker working with multiple threads, this would result in 259,200,000 passwords tried in a single month! |
假设每秒尝试 100 次，这对于普通的 Web 服务器来说是合理的，没有显着的加强并且攻击者使用多个线程，这将导致在一个月内尝试 259,200,000 个密码！ |
| Not enforcing any password policies will lead to too many users choosing “123456”, “qwerty” or “password” as their password, opening the system up for attack. |
不执行任何密码策略将导致过多用户选择“123456”、“qwerty”或“password”作为密码，从而使系统容易受到攻击。 |
| Enforcing too strict password policies will force users to save passwords or write them down, generally annoy them and foster re-using the same password for all services. |
实施过于严格的密码策略将迫使用户保存密码或写下密码，通常会惹恼他们并促进对所有服务重复使用相同的密码。 |
| Furthermore, users using secure passwords not matching the policies may be forced to use passwords which are harder to remember, but not necessarily secure. |
此外，使用与策略不匹配的安全密码的用户可能被迫使用更难记住但不一定安全的密码。 |
| A password consisting of 5 concatenated, randomly (!) chosen lowercase dictionary words is significantly more secure than an eight-character password consisting of mixed case letters, numbers and punctuation. |
由 5 个串联、随机 (!) 选择的小写字典单词组成的密码比由混合大小写字母、数字和标点符号组成的八字符密码明显更安全。 |
| Take this into account if you do not get a password policy to implement, but have to design your own. |
如果您没有要实施的密码策略，但必须设计自己的密码策略，请考虑这一点。 |
