Verified on jammy and noble.

Environment: fresh LXD containers, umask 027. Per the test plan, registration 
was run as:
    landscape-config --computer-title test --account-name standalone --url 
https://test.net/message-system --ping-url http://test.net/ping
(with --silent and a dummy --registration-key to run non-interactively; 
test.net is the placeholder URL from the test plan, so registration necessarily 
stops at TLS verification against that non-Landscape host. The permissions 
failure this bug is about happens before that point.)

jammy:
- Pre-proposed (23.02-0ubuntu1~22.04.7), umask 027: 
/var/lib/landscape/client/broker.bpickle created root:root mode 640, unreadable 
by the landscape user. Bug reproduced.
- 26.02.2-0ubuntu1~22.04.1 from jammy-proposed, umask 027: all files under 
/var/lib/landscape/client/ (broker.bpickle, monitor.bpickle) owned 
landscape:landscape, matching the expected ls -l output in the test plan; 
/var/lib/landscape itself is landscape:landscape. The config run proceeds past 
the permissions stage to the expected TLS failure against the test-plan 
placeholder URL.

noble:
- Pre-proposed (24.02-0ubuntu5.7), umask 027: same root:root 640 broker.bpickle 
reproduced.
- 26.02.2-0ubuntu1~24.04.1 from noble-proposed, umask 027: 
/var/lib/landscape/client/* all landscape:landscape as expected.

** Tags removed: verification-needed-jammy verification-needed-noble
** Tags added: verification-done-jammy verification-done-noble

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

Title:
  [SRU] landscape-config problem with hardened umask 027

To manage notifications about this bug go to:
https://bugs.launchpad.net/landscape-client/+bug/2065879/+subscriptions


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

Reply via email to