Paul Howarth wrote:
William Hooper wrote:
Paul Howarth wrote:
[snip]
Perhaps a -Y flag is required.
I'm not sure what "trusted X11 forwarding" means.
There's a brief mention of it in "man ssh_config". It's not normally
needed for the vast majority of apps
My experience is the complete opposite. Red Hat has even issued an
Errata
for RHEL 4 making trusted forwarding the default. I believe the only
apps
I have personally seen that work with untrusted forwarding are things
like
xeyes and xterm (as long as you don't want to copy and paste).
Take a look at this comment from Mike Harris:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=137685#c15
Interesting; just this morning I was remotely administering a SuSE box
running yast2 over an ssh -X connection, last night I used rdesktop over
one and I've definitely run firefox over one in the past. I wasn't doing
much (any?) copying and pasting though.
D'oh!
Reading further up the list of comments in the bug report above, I see
that the default configuration in the errata packages (which I have of
course) is to enable trusted forwarding by default, so ssh -X and ssh -Y
behave the same. So when I *thought* I was using untrusted mode by using
ssh -X, I was in fact using trusted mode anyway.
Apologies for any confusion caused...
Paul.
