home.social

#polkit — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #polkit, aggregated by home.social.

  1. Fedora retired all Deepin packages after unresolved security issues, broken builds, and months of maintainer inactivity. ⚠️
    FESCo said Deepin packages cannot return without a full review, following concerns over unsafe Polkit and D-Bus implementations. 🐧

    🔗 itsfoss.com/news/fedora-ditche

    #TechNews #Fedora #Deepin #Linux #OpenSource #Cybersecurity #FOSS #Polkit #DBus #DesktopLinux #SoftwareMaintenance #Privacy #Infosec #GNU #LinuxDesktop #OperatingSystem #OS #Kernel

  2. Fedora retired all Deepin packages after unresolved security issues, broken builds, and months of maintainer inactivity. ⚠️
    FESCo said Deepin packages cannot return without a full review, following concerns over unsafe Polkit and D-Bus implementations. 🐧

    🔗 itsfoss.com/news/fedora-ditche

    #TechNews #Fedora #Deepin #Linux #OpenSource #Cybersecurity #FOSS #Polkit #DBus #DesktopLinux #SoftwareMaintenance #Privacy #Infosec #GNU #LinuxDesktop #OperatingSystem #OS #Kernel

  3. Fedora retired all Deepin packages after unresolved security issues, broken builds, and months of maintainer inactivity. ⚠️
    FESCo said Deepin packages cannot return without a full review, following concerns over unsafe Polkit and D-Bus implementations. 🐧

    🔗 itsfoss.com/news/fedora-ditche

    #TechNews #Fedora #Deepin #Linux #OpenSource #Cybersecurity #FOSS #Polkit #DBus #DesktopLinux #SoftwareMaintenance #Privacy #Infosec #GNU #LinuxDesktop #OperatingSystem #OS #Kernel

  4. Fedora retired all Deepin packages after unresolved security issues, broken builds, and months of maintainer inactivity. ⚠️
    FESCo said Deepin packages cannot return without a full review, following concerns over unsafe Polkit and D-Bus implementations. 🐧

    🔗 itsfoss.com/news/fedora-ditche

    #TechNews #Fedora #Deepin #Linux #OpenSource #Cybersecurity #FOSS #Polkit #DBus #DesktopLinux #SoftwareMaintenance #Privacy #Infosec #GNU #LinuxDesktop #OperatingSystem #OS #Kernel

  5. Fedora retired all Deepin packages after unresolved security issues, broken builds, and months of maintainer inactivity. ⚠️
    FESCo said Deepin packages cannot return without a full review, following concerns over unsafe Polkit and D-Bus implementations. 🐧

    🔗 itsfoss.com/news/fedora-ditche

    #TechNews #Fedora #Deepin #Linux #OpenSource #Cybersecurity #FOSS #Polkit #DBus #DesktopLinux #SoftwareMaintenance #Privacy #Infosec #GNU #LinuxDesktop #OperatingSystem #OS #Kernel

  6. I patched to #zerotier to support its DNS setting via #systemd #resolved but I could use some input on the use of #polkit rules to authorize DNS changes (right now I'm making assumptions about #fedora ).

    github.com/zerotier/ZeroTierOn

  7. I patched to #zerotier to support its DNS setting via #systemd #resolved but I could use some input on the use of #polkit rules to authorize DNS changes (right now I'm making assumptions about #fedora ).

    github.com/zerotier/ZeroTierOn

  8. I patched to #zerotier to support its DNS setting via #systemd #resolved but I could use some input on the use of #polkit rules to authorize DNS changes (right now I'm making assumptions about #fedora ).

    github.com/zerotier/ZeroTierOn

  9. I patched to #zerotier to support its DNS setting via #systemd #resolved but I could use some input on the use of #polkit rules to authorize DNS changes (right now I'm making assumptions about #fedora ).

    github.com/zerotier/ZeroTierOn

  10. I patched to #zerotier to support its DNS setting via #systemd #resolved but I could use some input on the use of #polkit rules to authorize DNS changes (right now I'm making assumptions about #fedora ).

    github.com/zerotier/ZeroTierOn

  11. The #polkit prompt now shows more user data (by @arunmani ) like the users name and avator (or initials):

    3/x

  12. The #polkit prompt now shows more user data (by @arunmani ) like the users name and avator (or initials):

    3/x

  13. The #polkit prompt now shows more user data (by @arunmani ) like the users name and avator (or initials):

    3/x

  14. The #polkit prompt now shows more user data (by @arunmani ) like the users name and avator (or initials):

    3/x

  15. The #polkit prompt now shows more user data (by @arunmani ) like the users name and avator (or initials):

    3/x

  16. Critical vulnerabilities were disclosed in InputPlumber affecting Linux systems, including SteamOS.

    Impact highlights:
    • Insufficient D-Bus authorization
    • Potential keystroke injection via virtual devices
    • Local denial-of-service and information exposure

    The fixes emphasize secure Polkit usage, systemd hardening, and proper privilege boundaries.

    Share insights and follow @technadu for vendor-neutral security reporting.

    #InfoSec #LinuxHardening #VulnerabilityResearch #Polkit #D-Bus #OpenSourceSecurity

  17. Critical vulnerabilities were disclosed in InputPlumber affecting Linux systems, including SteamOS.

    Impact highlights:
    • Insufficient D-Bus authorization
    • Potential keystroke injection via virtual devices
    • Local denial-of-service and information exposure

    The fixes emphasize secure Polkit usage, systemd hardening, and proper privilege boundaries.

    Share insights and follow @technadu for vendor-neutral security reporting.

    #InfoSec #LinuxHardening #VulnerabilityResearch #Polkit #D-Bus #OpenSourceSecurity

  18. Critical vulnerabilities were disclosed in InputPlumber affecting Linux systems, including SteamOS.

    Impact highlights:
    • Insufficient D-Bus authorization
    • Potential keystroke injection via virtual devices
    • Local denial-of-service and information exposure

    The fixes emphasize secure Polkit usage, systemd hardening, and proper privilege boundaries.

    Share insights and follow @technadu for vendor-neutral security reporting.

    #InfoSec #LinuxHardening #VulnerabilityResearch #Polkit #D-Bus #OpenSourceSecurity

  19. Critical vulnerabilities were disclosed in InputPlumber affecting Linux systems, including SteamOS.

    Impact highlights:
    • Insufficient D-Bus authorization
    • Potential keystroke injection via virtual devices
    • Local denial-of-service and information exposure

    The fixes emphasize secure Polkit usage, systemd hardening, and proper privilege boundaries.

    Share insights and follow @technadu for vendor-neutral security reporting.

    #InfoSec #LinuxHardening #VulnerabilityResearch #Polkit #D-Bus #OpenSourceSecurity

  20. This is how to make the “Install pending software updates” checkbox go away in GNOME

    If you’re using GNOME, and when you tell it you want to shut down or reboot your system it pops up a confirmation dialog with an “Install pending software update” checkbox in it, and the checkbox is checked by default, and you want to make that checkbox go away or at least be unchecked by default, then you’ve come to the right place.

    There’s no perfect way to do this. Below I talk about two imperfect solutions that are available. If you think there should be an easier way, feel free to weigh in here. The GNOME developers are skeptical that anyone wants or needs this, but maybe if enough people ask for it they will reconsider.

    Imperfect solution one: Open the preferences for the GNOME Software app and change “Software Updates” there from “Automatic” to “Manual”. Caveats:

    • This may only work on systems, such as Fedora-based systems, where PackageKit uses a separate update cache from the system. On APT-based systems (Debian, Ubuntu, and the like), where it appears that PackageKit uses the same update cache as the underlying APT system (as it should!), then when the updates are downloaded outside of GNOME Software, you may still see the checkbox.
    • If there were already updates downloaded before you switched from Automatic to Manual, you will get the checkbox. You need to install those updates (either through GNOME Software or with DNF or APT or whatever) and then refresh the GNOME Software Updates tab to make them go away there.
    • If you check for updates in the GNOME Software app manually and then click the Download button, you will probably get the checkbox the next time you try to shut down or restart.

    Imperfect solution two: Create the file /etc/polkit-1/rules.d/99-disable-offline-update.rules, owned by user “root” and group “polkitd”, with the following contents:

    polkit.addRule(function(action, subject) {
     if ((action.id == "org.freedesktop.packagekit.trigger-offline-update")) {
      return polkit.Result.NO;
     }
    });

    Caveat: This will disable all attempts to trigger offline updates, not just the checkbox that shows up when you try to shutdown or restart your system. This means, for example, that you won’t be able to trigger “Restart and install…” updates from inside the GNOME Software app either.

    #GNOME #PackageKit #Polkit
  21. This is how to make the “Install pending software updates” checkbox go away in GNOME

    If you’re using GNOME, and when you tell it you want to shut down or reboot your system it pops up a confirmation dialog with an “Install pending software update” checkbox in it, and the checkbox is checked by default, and you want to make that checkbox go away or at least be unchecked by default, then you’ve come to the right place.

    There’s no perfect way to do this. Below I talk about two imperfect solutions that are available. If you think there should be an easier way, feel free to weigh in here. The GNOME developers are skeptical that anyone wants or needs this, but maybe if enough people ask for it they will reconsider.

    Imperfect solution one: Open the preferences for the GNOME Software app and change “Software Updates” there from “Automatic” to “Manual”. Caveats:

    • This may only work on systems, such as Fedora-based systems, where PackageKit uses a separate update cache from the system. On APT-based systems (Debian, Ubuntu, and the like), where it appears that PackageKit uses the same update cache as the underlying APT system (as it should!), then when the updates are downloaded outside of GNOME Software, you may still see the checkbox.
    • If there were already updates downloaded before you switched from Automatic to Manual, you will get the checkbox. You need to install those updates (either through GNOME Software or with DNF or APT or whatever) and then refresh the GNOME Software Updates tab to make them go away there.
    • If you check for updates in the GNOME Software app manually and then click the Download button, you will probably get the checkbox the next time you try to shut down or restart.

    Imperfect solution two: Create the file /etc/polkit-1/rules.d/99-disable-offline-update.rules, owned by user “root” and group “polkitd”, with the following contents:

    polkit.addRule(function(action, subject) {
     if ((action.id == "org.freedesktop.packagekit.trigger-offline-update")) {
      return polkit.Result.NO;
     }
    });

    Caveat: This will disable all attempts to trigger offline updates, not just the checkbox that shows up when you try to shutdown or restart your system. This means, for example, that you won’t be able to trigger “Restart and install…” updates from inside the GNOME Software app either.

    #GNOME #PackageKit #Polkit
  22. This is how to make the “Install pending software updates” checkbox go away in GNOME

    If you’re using GNOME, and when you tell it you want to shut down or reboot your system it pops up a confirmation dialog with an “Install pending software update” checkbox in it, and the checkbox is checked by default, and you want to make that checkbox go away or at least be unchecked by default, then you’ve come to the right place.

    There’s no perfect way to do this. Below I talk about two imperfect solutions that are available. If you think there should be an easier way, feel free to weigh in here. The GNOME developers are skeptical that anyone wants or needs this, but maybe if enough people ask for it they will reconsider.

    Imperfect solution one: Open the preferences for the GNOME Software app and change “Software Updates” there from “Automatic” to “Manual”. Caveats:

    • This may only work on systems, such as Fedora-based systems, where PackageKit uses a separate update cache from the system. On APT-based systems (Debian, Ubuntu, and the like), where it appears that PackageKit uses the same update cache as the underlying APT system (as it should!), then when the updates are downloaded outside of GNOME Software, you may still see the checkbox.
    • If there were already updates downloaded before you switched from Automatic to Manual, you will get the checkbox. You need to install those updates (either through GNOME Software or with DNF or APT or whatever) and then refresh the GNOME Software Updates tab to make them go away there.
    • If you check for updates in the GNOME Software app manually and then click the Download button, you will probably get the checkbox the next time you try to shut down or restart.

    Imperfect solution two: Create the file /etc/polkit-1/rules.d/99-disable-offline-update.rules, owned by user “root” and group “polkitd”, with the following contents:

    polkit.addRule(function(action, subject) {
     if ((action.id == "org.freedesktop.packagekit.trigger-offline-update")) {
      return polkit.Result.NO;
     }
    });

    Caveat: This will disable all attempts to trigger offline updates, not just the checkbox that shows up when you try to shutdown or restart your system. This means, for example, that you won’t be able to trigger “Restart and install…” updates from inside the GNOME Software app either.

    #GNOME #PackageKit #Polkit
  23. This is how to make the “Install pending software updates” checkbox go away in GNOME

    If you’re using GNOME, and when you tell it you want to shut down or reboot your system it pops up a confirmation dialog with an “Install pending software update” checkbox in it, and the checkbox is checked by default, and you want to make that checkbox go away or at least be unchecked by default, then you’ve come to the right place.

    There’s no perfect way to do this. Below I talk about two imperfect solutions that are available. If you think there should be an easier way, feel free to weigh in here. The GNOME developers are skeptical that anyone wants or needs this, but maybe if enough people ask for it they will reconsider.

    Imperfect solution one: Open the preferences for the GNOME Software app and change “Software Updates” there from “Automatic” to “Manual”. Caveats:

    • This may only work on systems, such as Fedora-based systems, where PackageKit uses a separate update cache from the system. On APT-based systems (Debian, Ubuntu, and the like), where it appears that PackageKit uses the same update cache as the underlying APT system (as it should!), then when the updates are downloaded outside of GNOME Software, you may still see the checkbox.
    • If there were already updates downloaded before you switched from Automatic to Manual, you will get the checkbox. You need to install those updates (either through GNOME Software or with DNF or APT or whatever) and then refresh the GNOME Software Updates tab to make them go away there.
    • If you check for updates in the GNOME Software app manually and then click the Download button, you will probably get the checkbox the next time you try to shut down or restart.

    Imperfect solution two: Create the file /etc/polkit-1/rules.d/99-disable-offline-update.rules, owned by user “root” and group “polkitd”, with the following contents:

    polkit.addRule(function(action, subject) {
     if ((action.id == "org.freedesktop.packagekit.trigger-offline-update")) {
      return polkit.Result.NO;
     }
    });

    Caveat: This will disable all attempts to trigger offline updates, not just the checkbox that shows up when you try to shutdown or restart your system. This means, for example, that you won’t be able to trigger “Restart and install…” updates from inside the GNOME Software app either.

    #GNOME #PackageKit #Polkit
  24. This is how to make the “Install pending software updates” checkbox go away in GNOME

    If you’re using GNOME, and when you tell it you want to shut down or reboot your system it pops up a confirmation dialog with an “Install pending software update” checkbox in it, and the checkbox is checked by default, and you want to make that checkbox go away or at least be unchecked by default, then you’ve come to the right place.

    There’s no perfect way to do this. Below I talk about two imperfect solutions that are available. If you think there should be an easier way, feel free to weigh in here. The GNOME developers are skeptical that anyone wants or needs this, but maybe if enough people ask for it they will reconsider.

    Imperfect solution one: Open the preferences for the GNOME Software app and change “Software Updates” there from “Automatic” to “Manual”. Caveats:

    • This may only work on systems, such as Fedora-based systems, where PackageKit uses a separate update cache from the system. On APT-based systems (Debian, Ubuntu, and the like), where it appears that PackageKit uses the same update cache as the underlying APT system (as it should!), then when the updates are downloaded outside of GNOME Software, you may still see the checkbox.
    • If there were already updates downloaded before you switched from Automatic to Manual, you will get the checkbox. You need to install those updates (either through GNOME Software or with DNF or APT or whatever) and then refresh the GNOME Software Updates tab to make them go away there.
    • If you check for updates in the GNOME Software app manually and then click the Download button, you will probably get the checkbox the next time you try to shut down or restart.

    Imperfect solution two: Create the file /etc/polkit-1/rules.d/99-disable-offline-update.rules, owned by user “root” and group “polkitd”, with the following contents:

    polkit.addRule(function(action, subject) {
     if ((action.id == "org.freedesktop.packagekit.trigger-offline-update")) {
      return polkit.Result.NO;
     }
    });

    Caveat: This will disable all attempts to trigger offline updates, not just the checkbox that shows up when you try to shutdown or restart your system. This means, for example, that you won’t be able to trigger “Restart and install…” updates from inside the GNOME Software app either.

    #GNOME #PackageKit #Polkit
  25. Something changed with #Kubuntu 25.10 over the past week. Now all of a sudden I'm getting #prompted for my #sudo #password every time #PackageKit runs to update package sources (which is several times a day)!

    Fortunately, you can create a custom
    #PolKit #rule to let it run without prompting you!

    sudo nano /etc/polkit-1/rules.d/10-allow-packagekit-refresh.rules

    polkit.addRule(function(action, subject) {
        if (action.id == "org.freedesktop.packagekit.system-sources-refresh" &&
            subject.isInGroup("sudo")) {
            return polkit.Result.YES;
        }
    });

    And that seems to work.

    #Linux #Ubuntu #KDE #KDE6 #Plasma6 #KDEPlasma6 #Discover #updates

  26. Something changed with #Kubuntu 25.10 over the past week. Now all of a sudden I'm getting #prompted for my #sudo #password every time #PackageKit runs to update package sources (which is several times a day)!

    Fortunately, you can create a custom
    #PolKit #rule to let it run without prompting you!

    sudo nano /etc/polkit-1/rules.d/10-allow-packagekit-refresh.rules

    polkit.addRule(function(action, subject) {
        if (action.id == "org.freedesktop.packagekit.system-sources-refresh" &&
            subject.isInGroup("sudo")) {
            return polkit.Result.YES;
        }
    });

    And that seems to work.

    #Linux #Ubuntu #KDE #KDE6 #Plasma6 #KDEPlasma6 #Discover #updates

  27. Something changed with #Kubuntu 25.10 over the past week. Now all of a sudden I'm getting #prompted for my #sudo #password every time #PackageKit runs to update package sources (which is several times a day)!

    Fortunately, you can create a custom
    #PolKit #rule to let it run without prompting you!

    sudo nano /etc/polkit-1/rules.d/10-allow-packagekit-refresh.rules

    polkit.addRule(function(action, subject) {
        if (action.id == "org.freedesktop.packagekit.system-sources-refresh" &&
            subject.isInGroup("sudo")) {
            return polkit.Result.YES;
        }
    });

    And that seems to work.

    #Linux #Ubuntu #KDE #KDE6 #Plasma6 #KDEPlasma6 #Discover #updates

  28. Something changed with #Kubuntu 25.10 over the past week. Now all of a sudden I'm getting #prompted for my #sudo #password every time #PackageKit runs to update package sources (which is several times a day)!

    Fortunately, you can create a custom
    #PolKit #rule to let it run without prompting you!

    sudo nano /etc/polkit-1/rules.d/10-allow-packagekit-refresh.rules

    polkit.addRule(function(action, subject) {
        if (action.id == "org.freedesktop.packagekit.system-sources-refresh" &&
            subject.isInGroup("sudo")) {
            return polkit.Result.YES;
        }
    });

    And that seems to work.

    #Linux #Ubuntu #KDE #KDE6 #Plasma6 #KDEPlasma6 #Discover #updates

  29. I hate debugging issues related to #polkit and #systemd. Neither of them generates logmessages when shit fails and for neither of them you get useful error messages.

    And you also can't just strace systemd without first setting up a minimalisting test system as otherwise you'll obviously never find what you're looking for in all of the output spam...

    It could be so easy if either of these would log more than just "Access denied" (when executed as root at least...)

  30. I hate debugging issues related to #polkit and #systemd. Neither of them generates logmessages when shit fails and for neither of them you get useful error messages.

    And you also can't just strace systemd without first setting up a minimalisting test system as otherwise you'll obviously never find what you're looking for in all of the output spam...

    It could be so easy if either of these would log more than just "Access denied" (when executed as root at least...)

  31. I hate debugging issues related to #polkit and #systemd. Neither of them generates logmessages when shit fails and for neither of them you get useful error messages.

    And you also can't just strace systemd without first setting up a minimalisting test system as otherwise you'll obviously never find what you're looking for in all of the output spam...

    It could be so easy if either of these would log more than just "Access denied" (when executed as root at least...)

  32. I hate debugging issues related to #polkit and #systemd. Neither of them generates logmessages when shit fails and for neither of them you get useful error messages.

    And you also can't just strace systemd without first setting up a minimalisting test system as otherwise you'll obviously never find what you're looking for in all of the output spam...

    It could be so easy if either of these would log more than just "Access denied" (when executed as root at least...)

  33. 🚀 quickshell-polkit-agent v2.0.0 is out!

    Major architectural overhaul: switched from proactive FIDO detection to a PAM-reactive model. The agent now responds to PAM prompts instead of trying to control auth flow.

    What's new:
    • GDM-inspired authentication state machine
    • 22 integration tests with 100% pass rate
    • Podman-based E2E testing infrastructure
    • Rich error handling & state tracking APIs
    • Performance optimizations (<2ms state transitions)

    🔧 Breaking changes:
    • Removed auto-FIDO logic (now handled by PAM/pam_u2f)
    • Simplified state machine (no more TRYING_FIDO states)
    • Cleaner authentication flow: IDLE → INITIATED → WAITING_FOR_PASSWORD → AUTHENTICATING → COMPLETED

    🐛 Fixed use-after-free bugs, race conditions, and timeout issues

    github.com/bennypowers/quickshell-polkit-agent/releases/tag/v2.0.0

    #Linux #Polkit #Qt6 #Authentication #FIDO2 #Quickshell #Gentoo

  34. Nutzt hier jemand einen kartenleser unter unbuntu linux?

    Und das funkzjoniert nach dist-upgrade nicht mehr? Das hier hilft vielleicht.

    #DirkHagedorn #Fail #Link #Linux #polkit #Ubuntu

  35. Nutzt hier jemand einen kartenleser unter unbuntu linux?

    Und das funkzjoniert nach dist-upgrade nicht mehr? Das hier hilft vielleicht.

    #DirkHagedorn #Fail #Link #Linux #polkit #Ubuntu

  36. Nutzt hier jemand einen kartenleser unter unbuntu linux?

    Und das funkzjoniert nach dist-upgrade nicht mehr? Das hier hilft vielleicht.

    #DirkHagedorn #Fail #Link #Linux #polkit #Ubuntu

  37. Nutzt hier jemand einen kartenleser unter unbuntu linux?

    Und das funkzjoniert nach dist-upgrade nicht mehr? Das hier hilft vielleicht.

    #DirkHagedorn #Fail #Link #Linux #polkit #Ubuntu