-
Notifications
You must be signed in to change notification settings - Fork 17
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
Unable to connect to Browser Plugin or SSH Agent #19
Comments
This is partly a duplicate of #13. See that issue for a great deal of detail about the browser extension. The short version is that its not as simple as just allowing access to the required files & sockets. At the moment it is either very difficult or impossible to make this work. This is especially true when the app relies on external resources, or running services. Be assured that I am always exploring ways to make these features work and I do take suggestions. To be clear, I am not ignoring these issues due to some security concern. |
thank you for your response. |
Flatpak 0.99.1 introduced the ability to use Since you probably have more experience than I with the KeePassXC ssh-agent feature, I would very much appreciate if you could test this with:
If this does not work, could you share more information on how things should look and behave when it does work? |
Looks like fedora 28 is running an older version:
|
Yeah it does not surprise me, since the 0.99.1 release is a pre-release for the stable 1.0. For some reason Arch Linux happens to use it. In either case I suppose I cannot rely upon it until 1.0 then. On the bright side I finally fixed the browser integration. Just about to force a rebuild due to some Flathub issues earlier. |
I can confirm |
Excelent! Thank you for testing. Now we just need various distributions to catch up. Or at least it would make sense to wait for the next LTS (stable) release of flatpak. Then I can add this by default in the manifest. |
Title says it all. The application is unable to connect to the Browser Plugin or SSH Agent.
I suspect this is by design as it is a containerised application but it should be considered that the security in this instance is affecting core (optional) functionality.
The text was updated successfully, but these errors were encountered: