From 0c2ae04cdf82e2a132c4e831b807230dcf4a9e86 Mon Sep 17 00:00:00 2001 From: Daniel Fainberg Date: Wed, 8 Jul 2026 07:58:29 +0200 Subject: [PATCH] feat(home): enable ssh-agent user service MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit gnome-keyring 50 dropped its ssh component and gpg's ssh support is off, so there was no agent at all — SSH_AUTH_SOCK unset, `ssh-add` failed. Keys stay added-on-demand (`AddKeysToAgent = "no"` in the inventory). Co-Authored-By: Claude Opus 4.8 --- modules/home.nix | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/modules/home.nix b/modules/home.nix index 41e3b1f..33a19fd 100644 --- a/modules/home.nix +++ b/modules/home.nix @@ -547,6 +547,12 @@ in # session has none otherwise; apps using libsecret/qtkeychain need it. services.gnome-keyring.enable = true; + # ssh-agent user service; sets SSH_AUTH_SOCK so `ssh-add` works in any shell. + # gnome-keyring above no longer ships an ssh component (dropped upstream), and + # gpg's ssh support is off, so this is the only agent. Keys are added on + # demand — nothing here presumes a particular ssh config. + services.ssh-agent.enable = true; + services.mako = { enable = true; settings = {