Bug#350208: sshd can't keep track of which DISPLAYs are in use

2006-02-06 Thread Greg Norris
Unfortunately, I seem to be unable to reproduce your issue... even when using the exact configuration you provided. Any chance you could strace the ssh daemon, and capture a pair of connections which exhibit the problem? $ strace -fF -o sshd.strace /usr/sbin/sshd -D signature.asc

Bug#350208: sshd can't keep track of which DISPLAYs are in use

2006-02-01 Thread Terran Melconian
This seems to be working as expected here (same version of ssh on a fully up-to-date sarge box), regardless of the X11UseLocalhost setting. If you'd be so kind as to post a copy of /etc/ssh/sshd_config, I'll Certainly; thanks for looking at this. In addition to the configuration files, here

Bug#350208: sshd can't keep track of which DISPLAYs are in use

2006-01-28 Thread Greg Norris
This seems to be working as expected here (same version of ssh on a fully up-to-date sarge box), regardless of the X11UseLocalhost setting. If you'd be so kind as to post a copy of /etc/ssh/sshd_config, I'll compare it against mine and try to determine if there are any relevant differences.

Bug#350208: sshd can't keep track of which DISPLAYs are in use

2006-01-27 Thread Terran Melconian
Package: ssh Version: 3.8.1p1-8.sarge.4 When connecting to sshd, it appears that sshd fails to keep track of which displays are already in use, and reassigns these to new connections even though they are not actually available. When I SSH into the machine, the first connection is given display