You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: inject keyring credentials for gh/glab profiles via secret-tool (#34)
On Linux, gh stores its OAuth token in gnome-keyring via libsecret.
Since the D-Bus session bus is blocked inside the sandbox, gh cannot
access the keyring directly. Instead, greywall reads the token on the
host (before sandboxing) using secret-tool and injects it as GH_TOKEN.
Changes:
- Add KeyringSecrets field to AgentDef for profile-driven credential
injection (envvar -> keyring service mapping)
- Add ResolveKeyringSecrets() to read from host keyring via secret-tool
- Wire up injection in main.go after env hardening, before exec
- Add ~/.gitconfig to gh/glab toolchain profile (needed by gh)
- Add secret-tool to greywall check with install suggestions
- Add libsecret-tools to CI and install docs
`xdg-dbus-proxy` is optional but recommended. It enables `notify-send` inside the sandbox while keeping the D-Bus session bus isolated.
35
+
`xdg-dbus-proxy` is optional but recommended (enables `notify-send` inside the sandbox). `libsecret-tools` provides `secret-tool` for injecting keyring credentials (e.g., gh OAuth token) into the sandbox.
0 commit comments