** Description changed:
+ [Impact] ssh-agent startup via Upstart doesn't work if the user's shell is
[t]csh.
+ [Test Case] Create a guest account whose shell is tcsh and make sure that
they can start a session and get ssh-agent. Note that this may not work for
GNOME-flavoured sessions due to gnome-keyring taking precedence.
+ [Regression Potential] Confined to the ssh-agent started via Upstart, and in
any event should be trivial since -s is already the default for most (just not
all) users.
+
For X11/KDE sessions ssh-agent is started via upstart using configuration
file /usr/share/upstart/sessions/ssh-agent.conf with the instruction ``eval
"$(ssh-agent)" >/dev/null''.
If the user's login shell is tcsh or csh ssh-agent will return c-shell like
setenv commands which upstart/shell do not recognize. Thus environment
variables $SSH_* are not propagated into the user's desktop session and neither
ssh nor ssh-add are able to contact ssh-agent.
Solution: use ``eval "$(ssh-agent -s)"'' to force sh-like output of ssh-agent
(context diff included as attachment)
Addition information: Bug occures at least in 13.10 and 14.04 amd64
architecture. In 14.04 the affected openssh-client package version is
1:6.2p2-6ubuntu0.3
** Changed in: openssh (Ubuntu Trusty)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1312928
Title:
SSH-Agent not working in KDE/X-Session if user's login shell is a tcsh
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1312928/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
