On Tue, Oct 16, 2018 at 12:43:40PM -0400, Gene Heskett wrote: > #1 is ssh -Y has been killed from jessie on. No excuse for doing it and > bug filing is ignored.
I don't know what you mean by this. I just performed the following experiment on my stretch workstation (wooledg), in communications with a stretch server (arc3) elsewhere on our network. 1) Already logged into wooledg, I opened a new urxvt window. 2) In this window, I typed: ssh -Y arc3 3) After authenticating to arc3 with a password, at the shell prompt, I typed: xterm 4) After a moment, a new xterm window appeared on my display. 5) Inside this xterm, to confirm that the xterm was running on arc3, I typed: uname -a Terminal sessions shown without modification: ===================================================== wooledg:~$ ssh -Y arc3 wooledg@arc3's password: Linux arc3 4.9.0-8-686-pae #1 SMP Debian 4.9.110-3+deb9u5 (2018-09-30) i686 The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. Last login: Mon Oct 1 17:18:16 2018 from 10.76.172.97 $ xterm ===================================================== $ uname -a Linux arc3 4.9.0-8-686-pae #1 SMP Debian 4.9.110-3+deb9u5 (2018-09-30) i686 GNU/Linux $ ===================================================== So, I don't know why you believe that ssh's -Y option has been "killed". If you are having trouble with it, start a new thread and we can try to help you figure out what's wrong.
