On Thu May 2, 2024 at 3:55 PM CEST, Ming Kuang via Gnupg-users wrote:
> https://lists.gnupg.org/pipermail/gnupg-users/2024-March/066957.html
> https://lists.gnupg.org/pipermail/gnupg-users/2024-March/066960.html
Just for the record, I find the explanation in the later email
rather dubious:
On Wed Mar 6, 2024 at 1:20 PM CET, Vladimir Nikishkin via Gnupg-users wrote:
> Dear All,
>
> I would like to try the GnuPG Password Manager
> (https://dev.gnupg.org/source/gpgpass/)
https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gpgpass.git;a=summary
And it has ability to download a snapshot of each
On Mon Mar 4, 2024 at 9:13 AM CET, Werner Koch wrote:
> Because all components of gnupg will start gpg-agent and the other
> daemons oin the fly and make sure that only one is started.
Do I understand it correctly that gnupg contains smaller version
of systemd (dependency activation) inside of
On Mon Mar 4, 2024 at 2:19 PM CET, gnupg-users-owner wrote:
> Your mail to 'Gnupg-users' with the subject
>
> Re: [gpg-agent] Empty OPTION xauthority=
>
> Is being held until the list moderator can review it for approval.
>
> The reason it is being held:
>
> Message body is too big: 63276
On Sun Mar 3, 2024 at 10:05 AM CET, Werner Koch wrote:
> > am running it on host with systemd --user services (configuration
>
> Take care, the use of systemd is racy and support will be removed in
> 2.6.
1. Could you please explain why it is racy? Why from all services
only gpg is unsuitable
On Sun Mar 3, 2024 at 10:05 AM CET, Werner Koch wrote:
> > am running it on host with systemd --user services (configuration
>
> Take care, the use of systemd is racy and support will be removed in
> 2.6.
1. Could you please explain why it is racy? Why from all services
only gpg is unsuitable
