Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

nixos/physlock: add allowAnyUser option #34524

Merged
merged 1 commit into from Feb 10, 2018

Conversation

infinisil
Copy link
Member

Motivation for this change

physlock required root permissions to run. This PR adds the allowAnyUser option, which adds a setuid wrapper for physlock, allowing any user to lock the screen by calling the binary physlock.

Things done
  • Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Fits CONTRIBUTING.md.

@infinisil infinisil changed the title physlock: add allowAnyUser option nixos/physlock: add allowAnyUser option Feb 3, 2018
@Mic92 Mic92 merged commit 9fab083 into NixOS:master Feb 10, 2018
@oxij
Copy link
Member

oxij commented Feb 10, 2018 via email

@fritz-k
Copy link

fritz-k commented Jun 14, 2019

@oxij If you're still interested in this, the polkit rule

/* Allow any user to lock the session/screen */
polkit.addRule(function(action, subject) {
  if (action.id == "org.freedesktop.systemd1.manage-units" &&
      action.lookup("unit") == "physlock.service" &&
      action.lookup("verb") == "start")
    { return polkit.Result.YES; }
});

allows every user to run systemctl start physlock.service. You could easily add this to the security.polkit.extraConfig if physlock.allowAnyUser was set.

@oxij
Copy link
Member

oxij commented Jun 17, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants