Bug 98820 - ssh pollutes xauthority file.
Summary: ssh pollutes xauthority file.
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: unspecified
Hardware: All All
: P5 - None : Normal
Target Milestone: ---
Assignee: Dr. Werner Fink
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-27 07:36 UTC by Egbert Eich
Modified: 2007-06-06 17:17 UTC (History)
2 users (show)

See Also:
Found By: Development
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Egbert Eich 2005-07-27 07:36:12 UTC
People have complained that the authority list of X growes over time since stale
credentials don't get removed. Apart from crashing login managers there used to
be two sources that left entrires behind even under normal circumstances: startx
and ssh. startx has been fixed a while back already and should remove all
credentials now. With #98627 this should even work when the hostname has changed
due to dynamic host name setting.
ssh still remains a problem. I've looked into it and it doesn't seem to be too
easy to fix: 
The ssh server forks, the child sets up the environment for the user session
calls  either sshrc or xauth to set up the credentials and then execve()s the
user shell or command. From then on it has no more control over the process,
thus the child that has set up the credentials can no longer remove them.
This would have to be done in the father process which waits until the child
exits. The changes necessary there however go beyond what I feel comfortable to
do with my limited knowledge of ssh server internals from my casual review.
All this takes place in session.c.
A possible (kludgy!) workaround would be to use some bash logout script to do
this task. It would have to detect if an ssh session was running and remove the
local display of this was the case.
Comment 1 Egbert Eich 2005-07-27 07:54:47 UTC
Duplicate posting.
Surprising what a reload on a 'Bug Processed' page can do.
Maybe a bug in bugzilla?