Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 139372
Summary: | ssh-agent left running after gnome window manger closes | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Thaddeus Nielsen <paroikos> |
Component: | gnome-desktop | Assignee: | Mark McLoughlin <markmc> |
Status: | CLOSED DUPLICATE | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | pri.rhl1, sitsofe |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-02-21 19:07:02 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Thaddeus Nielsen
2004-11-15 17:02:36 UTC
This looks like a dup of bug 138747 Yes, I would agree that these report the same problem. Your report says that this is limited only to GNOME. I shall try and test that tomorrow and add that information to my report... I can add that this also occurs with KDE (my wife uses KDE). But not with icewm (which is my preference because it is lighter and faster). Sorry, but I don't know much about the configuration of window managers. I suspect you don't see this in icewm because unlike the other environments its start up scripts have not been told to start ssh-agent. On KDE, GNOME, XFCE I can start a shell and type "echo $SSH_AGENT_PID" and see that an ssh-agent has been started for me. I suspect because icewm is a third party package echo $SSH_AGENT_PID will not show anything... This is a good point, I think. Your testing shows this is not limited to Gnome but that the ssh-agent is also started by Kde and Xfce. I wonder what exactly starts the ssh-agent: is it each of those three or something else that is common to them all? I seems reasonable that once the process is found which starts the ssh-agent, then it should be fairly easy to add a way to close the ssh-agent when the window manager closes. Thanks for pursuing this. I have answered some of your questions over in bug 138747 I can't seem to find it, but I seem to remember an xinitrc bug that this bug should really be marked a duplicate of, in addition to bug 138747. Anyhow, the change that causes this problem was required due to a bad security configuration that was fixed in openssh. The ssh-agent binary now has its sgid bit set to eliminate the strace-ability (I believe) of the process. The problem is that glibc (or is it ld-linux.so?) strips TMPDIR from the environment when running suid/sgid binaries. This caused problems with either gnome itself or dbus-launch, I forgot which. I think I have a possible solution to this, but would like feedback. It so simple that there *must* be something I'm missing. Try this: ssh-agent /bin/env TMPDIR=$TMPDIR /bin/bash echo $TMPDIR This basically sets the TMPDIR in defiance of glibc unsetting it when launching ssh-agent ;-) I don't know if this has any security implications, or even if it solves the problems mentioned in the bug on xinitrc (sorry, I don't have the bug number), which is what I'm looking for feedback on. Basically what I'm saying is that it may be possible to revert the xinitrc-common changes (well, not all of them as there were some cleanups) to at least prepend "/usr/bin/ssh-agent /bin/env TMPDIR=$TMPDIR" before the dbus-launch invocation. Hmm interesting stuff. After lots of scouring I think the changes began in bug #134494 Um, skip that 'solution' I suggested. Tried it. Doesn't work. I'll see if I can come up with something that works. Seems like a hairier problem than I thought. Marking as a dup of bug #138747 which I'll move to xinitrc where the changes in bug #134494 were originally made *** This bug has been marked as a duplicate of 138747 *** Changed to 'CLOSED' state since 'RESOLVED' has been deprecated. |