On Sun 2025-04-13 15:21:43 +0200, Marc Haber wrote:
> On Wed, Apr 09, 2025 at 04:39:14PM -0400, Daniel Kahn Gillmor wrote:
>>Marc, what does this command show for you?
>>
>> gpgconf --list-options gpg-agent | grep ^enable-ssh-agent:
>
> Nothing.
sorry, this should have been:
gpgconf --list-o
On Sun, Apr 13, 2025 at 04:10:26PM +0200, Michael Biebl wrote:
Am 13.04.2025 um 15:24 schrieb Marc Haber:
On Sat, Apr 12, 2025 at 03:40:54PM +0200, Michael Biebl wrote:
Would
ConditionUser=!@system
be an option here for those user services?
my ansible user is not in the system user range, but
Am 13.04.2025 um 15:24 schrieb Marc Haber:
On Sat, Apr 12, 2025 at 03:40:54PM +0200, Michael Biebl wrote:
Would
ConditionUser=!@system
be an option here for those user services?
my ansible user is not in the system user range, but still a system
user, as it doesn't originate from a package.
On Sat, Apr 12, 2025 at 03:40:54PM +0200, Michael Biebl wrote:
Would
ConditionUser=!@system
be an option here for those user services?
my ansible user is not in the system user range, but still a system
user, as it doesn't originate from a package.
I'd really like the socket unit to be stopp
On Wed, Apr 09, 2025 at 04:39:14PM -0400, Daniel Kahn Gillmor wrote:
Marc, what does this command show for you?
gpgconf --list-options gpg-agent | grep ^enable-ssh-agent:
Nothing.
Can you see anything in the per-user journal for the system user related
to gpg-agent? as the system user in
Would
ConditionUser=!@system
be an option here for those user services?
https://www.freedesktop.org/software/systemd/man/latest/systemd.unit.html#ConditionUser=
OpenPGP_signature.asc
Description: OpenPGP digital signature
On Mon 2025-03-31 21:53:41 +0200, Marc Haber wrote:
> It is probably enough to have an ssh-agent running on the side of the
> ssh client to invoke a gpg agent on the server side? I am not using gpg
> in any way here.
If we were to remove the systemd sockets, then gpg would auto-launch the
daemon
On Mon, Mar 31, 2025 at 05:44:44PM +0200, Andreas Metzler wrote:
just to clarify: we are not starting gpg-agent automatically on login. We
are shipping systemd user session units to lauch gpg-agent under
systemd's monitoring when gpg *needs* an agent. The other way to do this
is to let gpg itself
On 2025-03-28 Marc Haber wrote:
> On Fri, Mar 28, 2025 at 07:22:22PM +0100, Andreas Metzler wrote:
>> On 2025-03-28 Marc Haber wrote:
>>> from the README:
>>> |Since 2.1.17, users on machines with systemd will have their gpg-agent
>>> |process launched automatically by systemd's user session, upo
On Fri, Mar 28, 2025 at 07:22:22PM +0100, Andreas Metzler wrote:
On 2025-03-28 Marc Haber wrote:
from the README:
|Since 2.1.17, users on machines with systemd will have their gpg-agent
|process launched automatically by systemd's user session, upon first
|access of any of the expected gpg-agen
On 2025-03-28 Marc Haber wrote:
> Package: gpg-agent
> Version: 2.2.46-6
> Severity: important
> Hi,
> from the README:
> |Since 2.1.17, users on machines with systemd will have their gpg-agent
> |process launched automatically by systemd's user session, upon first
> |access of any of the expect
Package: gpg-agent
Version: 2.2.46-6
Severity: important
Hi,
from the README:
|Since 2.1.17, users on machines with systemd will have their gpg-agent
|process launched automatically by systemd's user session, upon first
|access of any of the expected gpg-agent sockets (including the ssh
|socket).
12 matches
Mail list logo
