Summary: | OpenSSH 3.8_p1 seems to break X forwarding | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jonathan Hitchcock <vhata-gentoo> |
Component: | Current packages | Assignee: | Daniel Ahlberg (RETIRED) <aliz> |
Status: | VERIFIED TEST-REQUEST | ||
Severity: | normal | CC: | ben |
Priority: | High | ||
Version: | 1.4 | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jonathan Hitchcock
2004-03-03 02:09:17 UTC
Something else that I've just realised it broke: When I leave my machine, I use 'xtrlock' to lock it. I have set up my shortcut keys to run "xtrlock" when I press Super-L. It behaves oddly, though, I have to press Super-L about seventeen times before it actually runs xtrlock. But I digress. I changed the shortcut to run "ssh -X localhost xtrlock" (i.e. run xtrlock with X forwarding, should be identical), and this works perfectly, strangely enough. But when I upgraded openssh, it stopped working again, presumably for the same reason x2x broke. xtrlock fiddles with your keyboard (locking it, yeah?), so is fairly similar in certain respects to x2x. And they were the only things that seemed to break. Ja. The releasenotes has this entry, could you try the ForwardX11Trusted thingie? * ssh(1) now uses untrusted cookies for X11-Forwarding. Some X11 applications might need full access to the X11 server, see ForwardX11Trusted in ssh(1) and xauth(1) for more information. Status? adding '-Y' to the ssh command fixes this Sorry for the delay - work got the better of me. You were dead right, I needed trusted forwarding. It might be nice to have the option in ssh_config, but I see that we use openssh's default configs, so maybe a dosed, or else forget it? Daniel Ahlberg is right that this is because of the X11ForwardTrusted not being defaulted to yes. I had the same problem and just found out what the problem was and X11Forwardtrusted fixed it. Debian enables this by default, so Gentoo should consider doing the same IMHO. |