Merge lp:~harlowja/cloud-init/fix-passwd into lp:~cloud-init-dev/cloud-init/trunk
Proposed by
Joshua Harlow
Status: | Merged |
---|---|
Merged at revision: | 756 |
Proposed branch: | lp:~harlowja/cloud-init/fix-passwd |
Merge into: | lp:~cloud-init-dev/cloud-init/trunk |
Diff against target: |
17 lines (+4/-3) 1 file modified
cloudinit/distros/__init__.py (+4/-3) |
To merge this branch: | bzr merge lp:~harlowja/cloud-init/fix-passwd |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
cloud-init Commiters | Pending | ||
Review via email:
|
To post a comment you must log in.
I dont have a good explanation for why system accounts would differ from non-system accounts with reguard to 'lock_passwd'. So, I'm just going to simplify this to: get('lock_ passwd' , True):
+ # Default locking down the account. 'lock_passwd' defaults to True.
+ # lock account unless lock_password is False.
+ if kwargs.
My simple test on 12.04 shows that 'passwd -l USER' works fine even if user's entry in /etc/shadow has '*' (which means 'no password').