Skip to main content
CharDSon
May 1, 2024 7:49 AM UTC
Question

Implement SSH Agent Functionality in 1Password for Flatpak

The SSH agent functionality is currently not available in the Flatpak environment for 1Password. Although Flatpak has a portal that allows access to SSH authentication, I'm not sure if this would be sufficient to enable the SSH agent in 1Password.

Therefore, I formally request that the development team evaluate the possibility of implementing this functionality by taking advantage of Flatpak's SSH authentication portal. It would greatly facilitate the workflow of developers using 1Password in Flatpak who require SSH authentication.

If there are technical limitations that prevent its implementation, I would appreciate an explanation. Thank you in advance for considering this request.

  • https://docs.flatpak.org/en/latest/sandbox-permissions.html#standard-permissions
  • https://github.com/flatpak/flatpak/issues/1438
  • https://github.com/flatpak/flatpak/pull/1764

1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Fedora Linux 40
Browser: Not Provided

4 replies

May 14, 2024 3:42 PM UTC

I’d also be interested in this, and am curious if it’s possible to implement using the SSH portal.

Jun 12, 2024 12:25 PM UTC

This would be very helpful, especially considering the new and interesting "immutable" distros out there that heavily rely on Flatpak for GUI applications. (https://projectbluefin.io/ and https://getaurora.dev/ for two)

I don't think there is anything technical preventing this now. KeePassXC https://github.com/flathub/org.keepassxc.KeePassXC/issues/117 this with Flatpak.

Thank you for your consideration!

Mar 28, 2025 2:01 AM UTC

Bumping this. I've yet to see a technical reason why 1Password wouldn't be able to implement this. Just a confirmation that it is or isn't on the roadmap would be nice!

Oct 22, 2026 10:02 PM UTC

Bumping this again. Bitwarden already supports the same functionality within a flatpak environment and there is no technical reason 1Password could not use the same method.

Bitwarden creates a socket file within its sandbox, and clients outside of the sandbox can access it by setting SSH_AUTH_SOCK=”/home/<user>/.var/app/com.bitwarden.desktop/.bitwarden-ssh-agent.sock”

Instead of disabling this feature completely within a flatpak environment, 1Password can create their socket file within the flatpak sandbox and provide instructions on setting a similar SSH_AUTH_SOCK environment variable.