-
-
Notifications
You must be signed in to change notification settings - Fork 411
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
gpg-agent socket #2301
Comments
Creates a --socket flag that allows access to the host gpg-agent. Related to flatpak#2301
@BrainBlasted any plans to bring your changes towards upstream? |
@SISheogorath eventually. IIRC I didn't finish the work to get things working there, and time hasn't been very permitting. |
I took a look at the commit and it seems to be a matter of removing a prefix from grep output. If the socket bind is all that is required, getting things done should be quite in reach :-) |
This is needed for dino/dino#343, i.e. a release of the Dino XMPP client as a flatpak, because the Dino devs insist on having the feature of PGP-encrypting your chats. |
@rugk as a quick solution you might want to have a peek into evolution's build instructions. They get GnuPG support by mounting the keyring directory. (Of course not perfect, but at least workable and not less secure than running it outside of Flatpak on an average distro.) |
Hi, I'm the person who wrote the Flatpak manifest for Dino. 👋
We know, that's all explained behind the link provided by @rugk, including the decision not to do that. @rugk dino/dino#343 had already been linked to this issue previously by the OP, who in fact is the Dino maintainer. We know Dino needs this. 😉 (please do not respond here if you want to add something to the topic of Dino; this ticket is about the gpg-agent socket for Flatpak, let's not pollute it with side conversations) |
Creates a --socket flag that allows access to the host gpg-agent. Related to flatpak#2301
This is my first time modifying a flatpka, and I don't know if this is the best way to do this, but it seems to work! :) I got inspiration from the org.gnome.Evolution flatpak. If it looks like something you want, but would like me to change it in some way first, let me know. I found the following issues which may allow this to be done better in future: Portal for GPG encryption/decryption flatpak/xdg-desktop-portal#178 gpg-agent socket flatpak/flatpak#2301 To make use of this modification, you can install the "pinentry" emacs package (https://elpa.gnu.org/packages/pinentry.html), and add the following to your `.emacs` configuration: ```elisp (pinentry-start) ```
This is my first time modifying a flatpak, and I don't know if this is the best way to do this, but it seems to work! :) I got inspiration from the org.gnome.Evolution flatpak. If it looks like something you want, but would like me to change it in some way first, let me know. I found the following issues which may allow this to be done better in future: Portal for GPG encryption/decryption flatpak/xdg-desktop-portal#178 gpg-agent socket flatpak/flatpak#2301 To make use of this modification, you can install the "pinentry" emacs package (https://elpa.gnu.org/packages/pinentry.html), and add the following to your `.emacs` configuration: ```elisp (pinentry-start) ```
Any update regarding this issue? |
This reverts commit f7dda86. GPG is still not working properly. Some support from flatpak side is needed. See: flatpak/flatpak#2301
This reverts commit f7dda86. GPG is still not working properly. Some support from flatpak side is needed. See: flatpak/flatpak#2301
Hello. I would like to attract more attention to this issue. Would it be appropriate to open a bounty for it at bountysource? I ask in case there is any objection or advice against it. If not, I will proceed with opening a bounty by the next week. I looked though the project and didn't find anything against this. |
A bounty was opened for implementing this. It is currently at USD 254. |
Currently, the gpg-agent can't be properly used out of the sandbox. An
--socket=gpg-agent
option would be helpful.The text was updated successfully, but these errors were encountered: