Bug#1079246: gcr4: Environment variable SSH_AUTH_SOCK is hijacked by gcr-ssh-agent

[Antoine]

Package: gcr4
Version: 4.3.0-1
Severity: normal

Dear Maintainer,

With a recent update of gcr4 (or libgcr-4-4), my environment variable
SSH_AUTH_SOCK has been changed to the gcr-ssh-agent socket. I am using
the gpg agent as ssh agent.

I had to disable the gcr-ssh-agent.service/socket globally to recover
my original environment variable.

It is not clear why gcr4 is hijacking my SSH_AUTH_SOCK variable in a
non-gnome session (I am using sway).

Antoine

-- System Information:
Debian Release: trixie/sid
  APT prefers testing
  APT policy: (500, 'testing'), (250, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: arm64, i386

Kernel: Linux 6.10.4-amd64 (SMP w/12 CPU threads; PREEMPT)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gcr4 depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.14.10-4+b1
ii  dbus-x11 [dbus-session-bus]                   1.14.10-4+b1
ii  gcr                                           3.41.2-1+b1
ii  init-system-helpers                           1.66
ii  libc6                                         2.39-6
ii  libgck-2-2                                    4.3.0-1
ii  libgcr-4-4                                    4.3.0-1
ii  libglib2.0-0t64                               2.81.1-3
ii  libgtk-4-1                                    4.12.5+ds-6+b1
ii  libpango-1.0-0                                1.54.0+ds-1
ii  libsecret-1-0                                 0.21.4-1+b1
ii  libsystemd0                                   256.5-1

gcr4 recommends no packages.

gcr4 suggests no packages.

-- no debconf information