|
|
Subscribe / Log in / New account

Deepin Desktop removed from openSUSE

The SUSE Security Team has announced the removal of the Deepin Desktop from openSUSE due to violations of the project's packaging policy.

The discovery of the bypass of the security whitelistings via the deepin-feature-enable package marks a turning point in our assessment of Deepin. We don't believe that the openSUSE Deepin packager acted with bad intent when he implemented the "license agreement" dialog to bypass our whitelisting restrictions. The dialog itself makes the security concerns we have transparent, so this does not happen in a sneaky way, at least not towards users. It was not discussed with us, however, and it violates openSUSE packaging policies. Beyond the security aspect, this also affects general packaging quality assurance: the D-Bus configuration files and Polkit policies installed by the deepin-feature-enable package are unknown to the package manager and won't be cleaned up upon package removal, for example. Such bypasses are not deemed acceptable by us.

The combination of these factors led us to the decision to remove the Deepin desktop completely from openSUSE Tumbleweed and from the future Leap 16.0 release. In openSUSE Leap 15.6 we will remove the offending deepin-feature-enable package only. It is a difficult decision given that the Deepin desktop has a considerable number of users. We firmly believe the Deepin packaging and security assessment in openSUSE needs a reboot, however, ideally involving new people that can help get the Deepin packages into shape, establish a relationship with Deepin upstream and keep an eye on bugfixes, thus avoiding fruitless follow-up reviews that just waste our time. In such a new setup we would be willing to have a look at all the sensitive Deepin components again one by one.

The announcement goes into detail about the bypass of openSUSE packaging policy and the history of security reviews of Deepin components. It also offers guidance on continuing to use Deepin Desktop on openSUSE.



to post comments

D-Bus reviews

Posted May 8, 2025 16:49 UTC (Thu) by legoktm (subscriber, #111994) [Link] (2 responses)

Are there other distros that take a similar approach to heavily auditing and controlling D-Bus access? It seems great openSUSE is doing these reviews, but I haven't heard of anyone else doing the same.

D-Bus reviews

Posted May 10, 2025 15:48 UTC (Sat) by clump (subscriber, #27801) [Link]

Arch Linux packages Deepin, and I fear they don't have nearly the same rigor shown by the openSUSE security team. Arch's wiki mentions openSUSE's Deepin findings but lets the user decide.

D-Bus reviews

Posted May 11, 2025 11:44 UTC (Sun) by smcv (subscriber, #53363) [Link]

I think openSUSE's security team is the outlier here (and I'm grateful that they do this). I've reported bugs about insecure system bus policies found in Debian in the past, but not in any particularly systematic way, and mainly looking at situations where package A's policy file opens unintended holes in package B's security model while installed (like CVE-2014-8156) rather than at whether package A is, itself, insecure.


Copyright © 2025, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds