nixos/goldwarden: init, goldwarden: package GUI

[SuperSandro2000]

Description of changes

Things done:

• packaged GUI
• made a module which installs polkit files, pinentry
• tested ssh agent functionality
• tested browser functionality

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[Kasper24]

I'm running into an issue with the systemd service not having pinentry in PATH. Works fine when I run goldwarden daemonize manually though.

Error: exec: "pinentry": executable file not found in $PATH

Adding this to the systemd service fixed it.

path = [ config.programs.gnupg.agent.pinentryPackage ];

[arthsmn]

LGTM. If possible, can you add a simple test just to check if there are any breaking changes in the service?

[SuperSandro2000]

Goldwarden is sometimes a bit brittle and fails for no apparent reason. Also we would need a running vaultwarden and probably create some entries in it which is a bit more involved.

[quexten]

Goldwarden is sometimes a bit brittle and fails for no apparent reason. Also we would need a running vaultwarden and probably create some entries in it which is a bit more involved.

@SuperSandro2000

On the GUI side, quexten/goldwarden#191 should fix a lot of the issues regarding stability. The daemon still needs some work, if you do encounter further issues please try to report them though, so they can be fixed :)