You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In yast-users, bad password hashing advice is given, referencing MD5 and DES and how PW length relates to these hashes. This is very obsolete advice, where we know better today. Additionally, yast-users gives advice like:
# Help text for password expert dialog 2/5
help_text = Ops.add(
help_text,
_(
"<p>\n" +
"Choose a password encryption method for local and system users.\n" +
"<b>DES</b>, the Linux default method, works in all network environments, but it\n" +
"restricts passwords to eight characters or less.\n" +
"</p>\n"
)
)
# Help text for password expert dialog 3/5
help_text = Ops.add(
help_text,
_(
"<p>\n" +
"<b>MD5</b> allows longer passwords, so provides more security, but some\n" +
"network protocols do not support this and you may have problems with NIS.\n" +
"</p>"
)
)
And still offers these types as options. These should be removed or altered to point out these algorithms are thoroughly and completely broken and beyond repair. UI or UX hints should be provided to de-prioritise these types.
Finally, yast-users refers to password encyrption rather than hashing or kdf, because in 2022 passwords SHOULD be stored after processing with a time hard KDF rather than a cryptographic verification hash.
The text was updated successfully, but these errors were encountered:
In yast-users, bad password hashing advice is given, referencing MD5 and DES and how PW length relates to these hashes. This is very obsolete advice, where we know better today. Additionally, yast-users gives advice like:
And still offers these types as options. These should be removed or altered to point out these algorithms are thoroughly and completely broken and beyond repair. UI or UX hints should be provided to de-prioritise these types.
Finally, yast-users refers to password encyrption rather than hashing or kdf, because in 2022 passwords SHOULD be stored after processing with a time hard KDF rather than a cryptographic verification hash.
The text was updated successfully, but these errors were encountered: