Bug 144723

Summary: password check in yast user administration tool is badly working
Product: [openSUSE] SUSE LINUX 10.0 Reporter: Tim Fechtner <timmi>
Component: YaST2Assignee: Jiří Suchomel <jsuchome>
Status: RESOLVED DUPLICATE QA Contact: Klaus Kämpf <kkaempf>
Severity: Normal    
Priority: P5 - None    
Version: Final   
Target Milestone: ---   
Hardware: PC   
OS: Other   
Whiteboard:
Found By: Other Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Tim Fechtner 2006-01-23 07:57:34 UTC
When creating a new user with yast and assigning a password, it is checked if it has at least 5 letters - and not if it has at least the number of letters specified in "security options".
Comment 1 Martin Lasarsch 2006-01-23 15:55:23 UTC
seems to be fixed in 10.1 beta1. changed to 8 characters in security options and added after that a user with 5 chars -> error messages that i need 8.
Comment 2 Tim Fechtner 2006-04-10 13:37:56 UTC
Working quit well. Tested in 10.1 beta 9.

However when you choose 0 as minimal password length, yast want to have at least 5 characters. (With other password lenght, also 1 to 4, it works fine.)

Comment 3 Michael Gross 2006-04-10 16:02:06 UTC
This might be intentional, reassigning to Jiri.
Comment 4 Jiří Suchomel 2006-04-11 07:59:40 UTC
yast2-users currently doesn't have the option to create user without a password.

*** This bug has been marked as a duplicate of 144724 ***
Comment 5 Tim Fechtner 2006-04-11 10:09:09 UTC
-- yast2-users currently doesn't have the option to
-- create user without a password.

I don't mean that. I mean the following: You have choosed "0" as minimal password length and than you enter a password with for example 4 characters. You will get a warning. (But when you have choosed "2" as minimal password length, you don't get a warning.)
Comment 6 Jiří Suchomel 2006-04-11 10:28:47 UTC
But this is exactly that problem - 0 is not valid password length and if it would, it would mean no password. It will be solved LATER.

*** This bug has been marked as a duplicate of 144724 ***