This bug was fixed in the package adsys - 0.8.5
---------------
adsys (0.8.5) kinetic; urgency=medium
[ Jean-Baptiste Lallement ]
[ Didier Roche ]
* Rename chapters to be in correct ascii order when viewed online.
Thanks to Anton Drastrup-Fjordbak.
* Include 22.04 in admx/adml for lts only releases. (LP: #1973745)
* Bump embedeed dependencies minor versions for both bug fixes and minor
security enhancements.
* Fix dconf keys not being readable by user after applying policy.
(LP: #1973748)
* Ensure we can execute machine and user scripts:
/run is now noexec on Ubuntu. Ensure that we can execute the scripts in
/run/adsys subdirectories. The scripts mecanism has been reviewed by the
security team, so we can reset them as executable. (LP: #1973751)
* Move integration tests under cmd/adsysd and admxgen binary to cmd/admxgen
to prepare future adwatchd daemon under cmd/ which will be SRUed with an
exception in next update. This is a no-op in the finale deploy binaries,
apart from admxgen which is now using Cobra. This binary though is not
shipped in any package and only used in CI.
* Fix privilege permission which can not be set to disabled. (LP: #1973752)
* Adaptation or new tests for all above changes.
* Add fuzz tests and include new potential crash fixes on invalid files
generated by Windows AD.
* CI fixes and changes (not impacting finale package):
- Move CI to Go 1.18 (package is already building with 1.18 in jammy).
- Fixes due to new github.
- Fix to generate all LTS releases in admx/adml (see above).
-- Didier Roche <didro...@ubuntu.com> Mon, 16 May 2022 14:09:36 +0200
** Changed in: adsys (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to adsys in Ubuntu.
https://bugs.launchpad.net/bugs/1973748
Title:
Updating any gsettings key makes user dconf database unreadable
Status in adsys package in Ubuntu:
Fix Released
Status in adsys source package in Jammy:
New
Bug description:
[Impact]
Changing any gsettings key in AD resulted in user databases under /etc/dconf,
owned by root, with 0600 as permissions. This change was done late in the cycle
after passing some permissions checkers to harden the binaries.
However, in that case, the user databases needs to be readable by the users
so that they can apply those values, so we need to align with ibus profile and
makes them 644.
[Test case]
* Change a gsettings key under AD, like picture-uri one.
* Login on the Ubuntu laptop connected with AD by adsys
* The background should now be changed to the set value.
[Where problems could occur]
This code is located in the dconf policy application manager and restricted
to it. The negative impact in case of a new bug will be seen by gsettings key
not being applied as it is already nowdays.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adsys/+bug/1973748/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
