Need help with your computer or device? Want to learn new tech skills? You're in the right place!
Geeks to Go is a friendly community of tech experts who can solve any problem you have. Just create a free account and post your question. Our volunteers will reply quickly and guide you through the steps. Don't let tech troubles stop you. Join Geeks to Go now and get the support you need!
New Member
New Member
Edited by troybolton, 05 September 2015 - 12:04 PM.
New Member
Most of the time they assume users know something about the product and will set a password.
When they do not require a specific type of password, this is often because the research suggests users will still set weak passwords.
They also know having a password policy will sometimes frustrate users who will then write it down, might forget it, or use a "strong" (upper and lower case letter, at least one number, 8-char) password, but these policies still churn out weak passwords, as evidenced by the use of deprecated hash functions and the number of cracked passwords using this type of policy.
Enforcing a policy is often a bad idea; very occasionally users might have a better policy and know what they need, and sometimes it's easier/better to take a head-in-the-sand approach, by making assumptions that the user has read the documentation. The hope is that this makes for a flexible and easy to install product, offloading the more difficult task of particular requirements and policy to users.
0 members, 0 guests, 0 anonymous users
Community Forum Software by IP.Board
Licensed to: Geeks to Go, Inc.
Sign In
Create Account
