Bug 2295 - clarify the effect of ForwardX11Timeout=0 in ssh config
Summary: clarify the effect of ForwardX11Timeout=0 in ssh config
Status: NEW
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: Documentation (show other bugs)
Version: 6.7p1
Hardware: All All
: P5 enhancement
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-10-17 06:20 AEDT by Christoph Anton Mitterer
Modified: 2014-10-17 06:20 AEDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Anton Mitterer 2014-10-17 06:20:43 AEDT 
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.