Bug#658124: x11-common: Xsession should not start ssh-agent (should be a user-level choice)
Package: x11-common
Version: 1:7.6+11
Severity: normal
By default, due to use-ssh-agent in /etc/X11/Xsession.options and
/etc/X11/Xsession.d/90x11-common_ssh-agent, Xsession starts ssh-agent
(as a user process). However this may clash with the user settings[*]
and even not, it may be a useless process. Xsession should not start
ssh-agent, or this should be controlled by a user-level option, not
by an admin-level one such as in /etc/X11/Xsession.options. Anyway if
the user wants to start ssh-agent, this is already possible via his
.xsession file in a more flexible way.
Note: /etc/X11/Xsession.d/90x11-common_ssh-agent does some checks
e.g. by testing whether $SSH_AUTH_SOCK is set, but unfortunately it
is sourced before the user can get the control on the environment,
so that there is no good workaround.
[*] For instance, I have a system to share the ssh-agent between
sessions (X / ssh to the machine / screen). The fact that
$SSH_AUTH_SOCK is set makes it believe that ssh-agent was already
started with this system.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages x11-common depends on:
ii debconf [debconf-2.0] 1.5.41
ii lsb-base 3.2-28.1
x11-common recommends no packages.
x11-common suggests no packages.
-- debconf information:
x11-common/xwrapper/allowed_users: Console Users Only
x11-common/xwrapper/actual_allowed_users: console
Reply to: