Bug 270901

Summary: mock useradd should set a null password
Product: [Retired] Fedora Hosted Projects Reporter: Simon <number.cruncher>
Component: mockAssignee: Clark Williams <williams>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: unspecifiedCC: dcantrell, michael_e_brown
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: 0.9.7-1 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-03-07 21:24:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Set null password for mockbuild user none

Description Simon 2007-08-31 11:19:27 UTC 
Description of problem:
Some distributions (e.g. SUSE 10) will lock an account newly created with
useradd, unless a null password is explicitly set.

This leads to "Password:" prompts whenever mock uses "su - mockbuild" or equivalent.

Version-Release number of selected component (if applicable):
mock-0.7.2

Actual results:
Password prompts

Expected results:
No password prompts

Additional info:
I think it would be a sensible default to explicitly set a null password. See patch.
Comment 1 Simon 2007-08-31 11:19:27 UTC 
Created attachment 183101 [details]
Set null password for mockbuild user
Comment 2 Clark Williams 2008-03-07 21:24:03 UTC 
we've had a big code reorg and this problem has been addressed multiple ways,
since we no longer call 'su - mockbuild' and we edit the passwd file after useradd.

I'll close this for now.