- This topic has 2 replies, 3 voices, and was last updated Mar 5-4:52 am by dolphin_oracle.
-
Posts
-
wildstar84
Upgrading policykit-1 and it’s related libraries from v0.105-31.1.0nosystemd0 to v0.105-33 says that it will bring in “polkitd” (yet another daemon process I presume).
1) My question (before upgrading) is: After upgrading, is this a new daemon that is going to be required to be always running now in order to operate my system (or can it be terminated after bootup or disabled all together post-install?
2) Also, I see it forces in “pkexec”, which I know is part of the current policykit, and was patched to fix a serious vulnerability, but my understanding was that this is now separated out in order to make it optional going forward, but here, the package is requiring it to be installed?
Anyone who has already upgraded this, can you shed some light on these questions? (I’m on current bookworm/testing.
Thanks!
anticapitalista
I’ll answer number 2.
According to Debian packagers, both polkitd and pkexec are dependencies of policykit-1
https://packages.debian.org/bookworm/policykit-1
I don’t use policykit at all so I cannot answer question 1.
Philosophers have interpreted the world in many ways; the point is to change it.
antiX with runit - leaner and meaner.
dolphin_oracle
polkitd is part of the debain policykit-1 package on bullseye as well. I presume its been stripped out of the antiX policykit-1-nosystemd package, but when you update to bookwork you get debian’s again.
if you aren’t using it now, you probably won’t need it later. antiX still has gksu for root apps. It might matter for some apps that utilize policykit internally, like a lot of gnome and kde apps do, as well as pkexec, not sure. I’ve never run into a problem on antiX, so I suspect you’ll be fine.
- You must be logged in to reply to this topic.
