** Description changed:

  [ Impact ]
  
  When using cloud-init to add a local user with a specific password/hash
  to the system at first boot, and sssd-tools also happens to be installed
  but sssd itself is not configured yet, a sequence of events leads to
  that user having no password set:
  
  - the user is created with the specified password hash just fine
  - cloud-init calls[1] "passwd -u" on the user
  - that passwd call ends up also calling "sss_cache -UG"[2], to reset the sssd 
cache, since the src:shadow package (where bin:passwd comes from) is built with 
sssd support[3] by default. If sss_cache is not available (bin:sssd-tools not 
installed), the bug does not manifest itself.
  - calling "sss_cache -UG" on a system with no valid sssd configuration yet 
prints an error message to stderr about a missing config.ldb, but exits with 0. 
This is since commits [4][5]. Those commits also changed sss_cache so that it 
no longer generates the config.ldb database, hence why it now always complains.
  - cloud-init checks exit status, and stderr, of the "passwd -u" call. It sees 
that stderr has content[6], and assumes a failure, proceeding to calling 
"passwd -d" on that account. This is what deletes the password hash from the 
user.
  
  For this SRU, I had originally opted to silence the error from the
  caller's side (src:shadow) if there is no config.ldb database present.
  That call is a best effort attempt to be helpful and clear the sssd
  cache, and the result of the call is being ignored anyway.
  
  But that has a much wider impact: src:shadow is installed everywhere.
  Even users not affected by this bug would get the update.
  
  Fedora (which is the sssd upstream) opted to entirely disable[7] sssd
  support in src:shadow. That is an option to consider for devel releases
  of ubuntu, but not an SRU.
  
  Then I thought about silencing the error from within sss_cache instead.
  It's the same fix in principle, and only users affected by the bug will
  receive the update. But this changes behavior.
  
  It would make sss_cache silent when it doesn't find the config.ldb
  database, so users might not be immediately aware that no action was
  taken by the tool.
  
  In the end, the real fix should be in cloud-init, because that's the
  actor making the wrong decision.
  
  1. 
https://github.com/canonical/cloud-init/blob/6193b2a0d241bed305e28a7aced1bd5c8c09de9a/cloudinit/distros/__init__.py#L1059
  2. 
https://git.launchpad.net/ubuntu/+source/shadow/tree/src/passwd.c?h=applied/ubuntu/devel#n1175
  3. 
https://git.launchpad.net/ubuntu/+source/shadow/tree/configure.ac?h=applied/ubuntu/devel#n202
  4. 
https://github.com/SSSD/sssd/commit/a008accecd6d0b35e8d57d738ee3d05863aa7d0f
  5. 
https://github.com/SSSD/sssd/commit/50b4579413c1146a2fced5ced19977e13790731c
  6. 
https://github.com/canonical/cloud-init/blob/6193b2a0d241bed305e28a7aced1bd5c8c09de9a/cloudinit/distros/__init__.py#L1063
  7. 
https://src.fedoraproject.org/rpms/shadow-utils/c/1820858d26f633482d3679d1c97324e25e3c1df8?branch=rawhide
  
  [ Test Plan ]
  
  There is a script attached to this bug which will reproduce the issue.
  It assumes a working lxd setup, and that "lxc launch ubuntu-
  daily:<ubuntu-release-name>" produces a working container.
  
  The script will exercise the following aspects of this bug:
  - provide the necessary cloud-init user-data to trigger the bug
  - check that the user has a password set or not in the end
  - check that "passwd -u" produces or not the stderr output that triggers the 
bug
  - check that "sss_cache -UG" is *always* silent, i.e., no stderr noise about 
the missing config.ldb
  
  To run the test, download the script to some directory and make it
  executable:
  
  wget 
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2153951/+attachment/6016710/+files/lp2153951-test.sh
  chmod +x lp2153951-test.sh
  
  Then run it targeting the ubuntu release under test. For example, for
  resolute:
  
- ./lp2153951-test.sh --release resolute
+ $ ./lp2153951-test.sh --release resolute
  
  That should reproduce the error, i.e., the script must indicate the test
  as having failed.
  
  To test the fixed packages, pass the "--pocket proposed" parameter.
  Again with the resolute example:
  
  ./lp2153951-test.sh --release resolute --pocket proposed
  
  This time the script should indicate that all checks have passed, and
  that completes the verification for this SRU.
  
  Here is run that shows the bug being reproduced:
  
  $ ./lp2153951-test.sh --release stonking
  Launching stonking container lp2153951-174927 (phase 1: repositories + 
packages)
  Launching lp2153951-174927
  .........................................................status: done
  Resetting cloud-init state and rebooting (phase 2: user configuration)
  status: done
  
  === apt-cache policy cloud-init (package source used in this test) ===
  cloud-init:
    Installed: 26.2-0ubuntu2
    Candidate: 26.2-0ubuntu2
    Version table:
   *** 26.2-0ubuntu2 500
          500 http://archive.ubuntu.com/ubuntu stonking/main amd64 Packages
          100 /var/lib/dpkg/status
  
  === Checks ===
  FAIL: tuser has no hashed password in /etc/shadow (got: '<empty>')
  
  RESULT: FAIL
  Destroying container lp2153951-174927
  
  And here is a run showing the tests passing (I used a PPA for this
  example, but the real SRU verification must use "--pocket proposed"):
  
  $ ./lp2153951-test.sh --release stonking --pocket ppa:nryanl/lp2153951
  Launching stonking container lp2153951-194622 (phase 1: repositories + 
packages)
  Launching lp2153951-194622
  
..........................................................................................................................................................................................status:
 done
  Resetting cloud-init state and rebooting (phase 2: user configuration)
  status: done
  
  === apt-cache policy cloud-init (package source used in this test) ===
  cloud-init:
    Installed: 26.2-0ubuntu3
    Candidate: 26.2-0ubuntu3
    Version table:
   *** 26.2-0ubuntu3 500
          500 https://ppa.launchpadcontent.net/nryanl/lp2153951/ubuntu 
stonking/main amd64 Packages
          100 /var/lib/dpkg/status
       26.2-0ubuntu2 500
          500 http://archive.ubuntu.com/ubuntu stonking/main amd64 Packages
  
  === Checks ===
  PASS: tuser has a hashed password in /etc/shadow (got: 
'$6$lp2153951$Iq7BfvEAR8qyz9eKAKs5sAGBBtyDoSRW0D2FnBJdG3Xy5.rLbSh29Hrds0VXSNzIx/1PNNmATPReqLjginX7/.')
  
  RESULT: PASS
  Destroying container lp2153951-194622
  
  [ Where problems could occur ]
  
  TODO by cloud-init team
  
  cloud-init is used by many linux distributions, not just ubuntu. While
- we can verify via the test plan that
+ we can verify via the test plan that this specific case is fixed for
+ ubuntu, it is possible that it might regress other linux distributions.
+ The cloud-init test suite itself should cover those cases.
+ 
  
  [ Other Info ]
  
  See "Original Description" below for the original scenario where this
  bug appeared.
  
  [ Original Description ]
  
  Installed ubuntu-desktop in 26.04 server, and it didn't generate
  config.ldb file which kept deleting the password configured by cloud-
  init user data.
  
  ubuntu@ip-10-0-1-145:~$ sudo passwd -u ubuntu 2>&1
  [sss_cache] [sss_tool_confdb_init] (0x0010): Can't access 
'/var/lib/sss/db/config.ldb', probably SSSD isn't configured
  Can't find configuration db, was SSSD configured and run?
  [sss_cache] [sss_tool_confdb_init] (0x0010): Can't access 
'/var/lib/sss/db/config.ldb', probably SSSD isn't configured
  Can't find configuration db, was SSSD configured and run?
  passwd: password changed.
  ubuntu@ip-10-0-1-145:~$ echo "exit: $?"
  exit: 0
  
  there are output even though exit code 0 which triggers passwd -d in
  cloud-init script

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2153951

Title:
  unconfigured sssd leads to cloud-init removing a password from a user

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2153951/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to