FS#80238 - [gnupg] support service and socket file for keyboxd
Attached to Project:
Arch Linux
Opened by Celeste (Coelacanthus) - Sunday, 12 November 2023, 09:42 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:22 GMT
Opened by Celeste (Coelacanthus) - Sunday, 12 November 2023, 09:42 GMT
Last edited by Buggy McBugFace (bugbot) - Saturday, 25 November 2023, 20:22 GMT
|
Details
Description:
In gpg 2.4.3, gpg introduce a new service named keyboxd, it listen %t/gnupg/S.keyboxd. If no service and socket, and add use-keyboxd in commnon.conf, gpg will be broken. https://lwn.net/Articles/918269/ |
This task depends upon
Closed by Buggy McBugFace (bugbot)
Saturday, 25 November 2023, 20:22 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/gnupg/issues/2
Saturday, 25 November 2023, 20:22 GMT
Reason for closing: Moved
Additional comments about closing: https://gitlab.archlinux.org/archlinux/p ackaging/packages/gnupg/issues/2
https://github.com/gpg/gnupg/blob/gnupg-2.4.3/README#L119-L145
As upstream removed their systemd support (due to not understanding, or wanting to understand, how systemd works) we would have to create integration ourselves. Can you please try whether the two attached systemd user units fix your problem?
To test for your local user, you can move them to e.g. `~/.config/systemd/user/` and then enable the socket via `systemctl --user daemon-reload && systemctl --user enable --now keyboxd.socket`
You can still start the socket, but you can not enable it: `systemctl --user daemon-reload && systemctl --user start keyboxd.socket`
Probably needs a bit of investigation on how to do this right... -_-
And service need some modification to run, Type should be forking and arguments should be --daemon.
I can confirm there is no other keyboxd via pgrep.