bugzilla-daemon at mindrot.org
2014-Oct-16 19:20 UTC
[Bug 2295] New: clarify the effect of ForwardX11Timeout=0 in ssh config
https://bugzilla.mindrot.org/show_bug.cgi?id=2295 Bug ID: 2295 Summary: clarify the effect of ForwardX11Timeout=0 in ssh config Product: Portable OpenSSH Version: 6.7p1 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 Component: Documentation Assignee: unassigned-bugs at mindrot.org Reporter: calestyo at scientia.net Hi. This is a follow-up to https://github.com/openssh/openssh-portable/pull/9 I've tried what happens when I set ForwardX11Timeout=0(s|w|m...) It seems that after having logged into a session, one can not longer start any X client (or better said, the program starts, but it cannot connect to the X server on the local end of my ssh). But apparently something like ssh host xman still works. So I've expected that it would mean "direct execution of an X client allows it's connection". So I've tried echo "xman &" | ssh host which I've expected to be just like normal session login,... but "immediately" starting the client... thus I guess it wouldn't work. However, it also allows connection. So what exactly is ForwardX11Timeout=0? I can adapt my pull request to include this information, once I have it. Cheers, Chris. -- You are receiving this mail because: You are watching the assignee of the bug.
Seemingly Similar Threads
- [Bug 2291] New: ssh -Q kex lists diffie-hellman-group1-sha1 twice
- [Bug 2303] New: ssh (and perhaps even sshd) should allow to specify the minimum DH group sizes for DH GEX
- [Bug 2293] New: ssh should have an option to automatically trust a local sshd's host key for a given set of names
- [Bug 1993] ssh tries to add keys to ~/.ssh/known_hosts though StrictHostKeyChecking yes is set
- [Bug 2354] New: please document that PermitRootLogin really checks for uid=0