How can I enable trusted X11 forwarding on Putty (with Xming) or otherwise get rid of one second delay when starting X11 aplication?

up vote
5
down vote

favorite

I've noticed one second delay before Midnight Commander or mcedit starts in Putty. It took me a while before I realized it is caused by X11 forwarding enabled. mc -X start immediately.

Unfortunately starting any X11 application has same delay. Maybe I'm nitpicking but it drives me crazy. Especially because some users mentioned cause and solution for this: xming does not support X11 security, so Linux must wait for network timeout. It is on second for me, but 30 seconds for others according to some discussions.

The solution is trusted X11 forwarding enabled by -Y commandline option for ssh. Unfortunately Putty doesn't have this option. Is there any other way to enable trusted forwarding on Putty ?

edited Mar 17 '16 at 6:07

asked Mar 16 '16 at 10:44

martins

263

add a commentÂ |Â

up vote
5
down vote

favorite

I've noticed one second delay before Midnight Commander or mcedit starts in Putty. It took me a while before I realized it is caused by X11 forwarding enabled. mc -X start immediately.

The solution is trusted X11 forwarding enabled by -Y commandline option for ssh. Unfortunately Putty doesn't have this option. Is there any other way to enable trusted forwarding on Putty ?

edited Mar 17 '16 at 6:07

asked Mar 16 '16 at 10:44

martins

263

add a commentÂ |Â

up vote
5
down vote

favorite

I've noticed one second delay before Midnight Commander or mcedit starts in Putty. It took me a while before I realized it is caused by X11 forwarding enabled. mc -X start immediately.

The solution is trusted X11 forwarding enabled by -Y commandline option for ssh. Unfortunately Putty doesn't have this option. Is there any other way to enable trusted forwarding on Putty ?

edited Mar 17 '16 at 6:07

asked Mar 16 '16 at 10:44

martins

263

I've noticed one second delay before Midnight Commander or mcedit starts in Putty. It took me a while before I realized it is caused by X11 forwarding enabled. mc -X start immediately.

The solution is trusted X11 forwarding enabled by -Y commandline option for ssh. Unfortunately Putty doesn't have this option. Is there any other way to enable trusted forwarding on Putty ?

ssh putty xming

edited Mar 17 '16 at 6:07

asked Mar 16 '16 at 10:44

martins

263

edited Mar 17 '16 at 6:07

asked Mar 16 '16 at 10:44

martins

263

edited Mar 17 '16 at 6:07

asked Mar 16 '16 at 10:44

martins

263

asked Mar 16 '16 at 10:44

martins

263

asked Mar 16 '16 at 10:44

martins

263

add a commentÂ |Â

2 Answers
2

active

oldest

votes

up vote
0
down vote

The -Y or ForwardX11Trusted for ssh client disables access control for remote X clients. Putty does not propose it but Xming started with -ac disables access control as well.

This xming tips page describes 2 ways to disable access control when Xming starts: using -ac parameter or modifying a file.

Is it better after Xming restart with access control disabled?

----

This first answer is left for reference.

-C might slow down communication on fast network (see ssh manual page), so I think it will not help in your situation.

putty 0.67 has both -X (turns on X11 forwarding in SSH) and -C (enable compression) see 3.8.3 Standard command-line options in the documentation.

Compression improves performance when used with ssh.
The line below has been tested with a server far far away:

PUTTY.EXE -X -C -ssh 10.0.0.2

Let me know if it is better with both -X and -C in your environment?

edited Mar 18 '16 at 9:27

answered Mar 16 '16 at 18:24

Jay jargot

80125

Thanks for your suggestion. I'll try compression, but I did not mentioned I was working on localhost in virtual machine. Unfortunately -X in putty means X11 on, while in linux/cygwin ssh command -X means untrusted and -Y trusted. I've corrected it in my answer.
â€“Â martins
Mar 17 '16 at 6:06

The ForwardX11Trusted for ssh client is disabling control for remote X client. Putty does not allow this but Xming shortcut can be modify to use -ac. It is also equivalent to xhost +.
â€“Â Jay jargot
Mar 18 '16 at 4:25

I have updated the answer. Could you give it a try and tell me if it is better?
â€“Â Jay jargot
Mar 18 '16 at 9:26

Thanks. I've tried both xming with commandline parameter and xlaunch with additional parameter for xming. There still was one second delay before mc or codeblocks started.
â€“Â martins
Mar 18 '16 at 12:30

What if it is not due to the X11 Trusted? I mean it is worth to sniff packets with wireshark in order to figure out what is going on?
â€“Â Jay jargot
Mar 18 '16 at 12:34

add a commentÂ |Â

up vote
0
down vote

PuTTY is safe enough with X11 forwarding. Please note that it may be necessary to install xauth on your Linux. After SSH login check if DISPLAY variable defined automatically. Its value should be localhost:... or similar. If not you should change to IPv4 only in your /etc/ssh/sshd_config and restart ssh service and try it again.

answered Sep 8 at 13:07

Afsin Toparlak

38114

add a commentÂ |Â

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f270160%2fhow-can-i-enable-trusted-x11-forwarding-on-putty-with-xming-or-otherwise-get-r%23new-answer', 'question_page');

);

Post as a guest

Name

2 Answers
2

active

oldest

votes

2 Answers
2

active

oldest

votes

up vote
0
down vote

The -Y or ForwardX11Trusted for ssh client disables access control for remote X clients. Putty does not propose it but Xming started with -ac disables access control as well.

This xming tips page describes 2 ways to disable access control when Xming starts: using -ac parameter or modifying a file.

Is it better after Xming restart with access control disabled?

----

This first answer is left for reference.

-C might slow down communication on fast network (see ssh manual page), so I think it will not help in your situation.

putty 0.67 has both -X (turns on X11 forwarding in SSH) and -C (enable compression) see 3.8.3 Standard command-line options in the documentation.

Compression improves performance when used with ssh.
The line below has been tested with a server far far away:

PUTTY.EXE -X -C -ssh 10.0.0.2

Let me know if it is better with both -X and -C in your environment?

edited Mar 18 '16 at 9:27

answered Mar 16 '16 at 18:24

Jay jargot

80125

Thanks for your suggestion. I'll try compression, but I did not mentioned I was working on localhost in virtual machine. Unfortunately -X in putty means X11 on, while in linux/cygwin ssh command -X means untrusted and -Y trusted. I've corrected it in my answer.
â€“Â martins
Mar 17 '16 at 6:06

The ForwardX11Trusted for ssh client is disabling control for remote X client. Putty does not allow this but Xming shortcut can be modify to use -ac. It is also equivalent to xhost +.
â€“Â Jay jargot
Mar 18 '16 at 4:25

I have updated the answer. Could you give it a try and tell me if it is better?
â€“Â Jay jargot
Mar 18 '16 at 9:26

Thanks. I've tried both xming with commandline parameter and xlaunch with additional parameter for xming. There still was one second delay before mc or codeblocks started.
â€“Â martins
Mar 18 '16 at 12:30

What if it is not due to the X11 Trusted? I mean it is worth to sniff packets with wireshark in order to figure out what is going on?
â€“Â Jay jargot
Mar 18 '16 at 12:34

add a commentÂ |Â

up vote
0
down vote

The -Y or ForwardX11Trusted for ssh client disables access control for remote X clients. Putty does not propose it but Xming started with -ac disables access control as well.

This xming tips page describes 2 ways to disable access control when Xming starts: using -ac parameter or modifying a file.

Is it better after Xming restart with access control disabled?

----

This first answer is left for reference.

-C might slow down communication on fast network (see ssh manual page), so I think it will not help in your situation.

putty 0.67 has both -X (turns on X11 forwarding in SSH) and -C (enable compression) see 3.8.3 Standard command-line options in the documentation.

Compression improves performance when used with ssh.
The line below has been tested with a server far far away:

PUTTY.EXE -X -C -ssh 10.0.0.2

Let me know if it is better with both -X and -C in your environment?

edited Mar 18 '16 at 9:27

answered Mar 16 '16 at 18:24

Jay jargot

80125

Thanks for your suggestion. I'll try compression, but I did not mentioned I was working on localhost in virtual machine. Unfortunately -X in putty means X11 on, while in linux/cygwin ssh command -X means untrusted and -Y trusted. I've corrected it in my answer.
â€“Â martins
Mar 17 '16 at 6:06

The ForwardX11Trusted for ssh client is disabling control for remote X client. Putty does not allow this but Xming shortcut can be modify to use -ac. It is also equivalent to xhost +.
â€“Â Jay jargot
Mar 18 '16 at 4:25

I have updated the answer. Could you give it a try and tell me if it is better?
â€“Â Jay jargot
Mar 18 '16 at 9:26

Thanks. I've tried both xming with commandline parameter and xlaunch with additional parameter for xming. There still was one second delay before mc or codeblocks started.
â€“Â martins
Mar 18 '16 at 12:30

What if it is not due to the X11 Trusted? I mean it is worth to sniff packets with wireshark in order to figure out what is going on?
â€“Â Jay jargot
Mar 18 '16 at 12:34

add a commentÂ |Â

up vote
0
down vote

The -Y or ForwardX11Trusted for ssh client disables access control for remote X clients. Putty does not propose it but Xming started with -ac disables access control as well.

This xming tips page describes 2 ways to disable access control when Xming starts: using -ac parameter or modifying a file.

Is it better after Xming restart with access control disabled?

----

This first answer is left for reference.

-C might slow down communication on fast network (see ssh manual page), so I think it will not help in your situation.

putty 0.67 has both -X (turns on X11 forwarding in SSH) and -C (enable compression) see 3.8.3 Standard command-line options in the documentation.

Compression improves performance when used with ssh.
The line below has been tested with a server far far away:

PUTTY.EXE -X -C -ssh 10.0.0.2

Let me know if it is better with both -X and -C in your environment?

edited Mar 18 '16 at 9:27

answered Mar 16 '16 at 18:24

Jay jargot

80125

The -Y or ForwardX11Trusted for ssh client disables access control for remote X clients. Putty does not propose it but Xming started with -ac disables access control as well.

This xming tips page describes 2 ways to disable access control when Xming starts: using -ac parameter or modifying a file.

Is it better after Xming restart with access control disabled?

----

This first answer is left for reference.

-C might slow down communication on fast network (see ssh manual page), so I think it will not help in your situation.

putty 0.67 has both -X (turns on X11 forwarding in SSH) and -C (enable compression) see 3.8.3 Standard command-line options in the documentation.

Compression improves performance when used with ssh.
The line below has been tested with a server far far away:

PUTTY.EXE -X -C -ssh 10.0.0.2

Let me know if it is better with both -X and -C in your environment?

edited Mar 18 '16 at 9:27

answered Mar 16 '16 at 18:24

Jay jargot

80125

edited Mar 18 '16 at 9:27

answered Mar 16 '16 at 18:24

Jay jargot

80125

answered Mar 16 '16 at 18:24

Jay jargot

80125

answered Mar 16 '16 at 18:24

Jay jargot

80125

Thanks for your suggestion. I'll try compression, but I did not mentioned I was working on localhost in virtual machine. Unfortunately -X in putty means X11 on, while in linux/cygwin ssh command -X means untrusted and -Y trusted. I've corrected it in my answer.
â€“Â martins
Mar 17 '16 at 6:06

The ForwardX11Trusted for ssh client is disabling control for remote X client. Putty does not allow this but Xming shortcut can be modify to use -ac. It is also equivalent to xhost +.
â€“Â Jay jargot
Mar 18 '16 at 4:25

I have updated the answer. Could you give it a try and tell me if it is better?
â€“Â Jay jargot
Mar 18 '16 at 9:26

Thanks. I've tried both xming with commandline parameter and xlaunch with additional parameter for xming. There still was one second delay before mc or codeblocks started.
â€“Â martins
Mar 18 '16 at 12:30

What if it is not due to the X11 Trusted? I mean it is worth to sniff packets with wireshark in order to figure out what is going on?
â€“Â Jay jargot
Mar 18 '16 at 12:34

add a commentÂ |Â

Thanks for your suggestion. I'll try compression, but I did not mentioned I was working on localhost in virtual machine. Unfortunately -X in putty means X11 on, while in linux/cygwin ssh command -X means untrusted and -Y trusted. I've corrected it in my answer.
â€“Â martins
Mar 17 '16 at 6:06

The ForwardX11Trusted for ssh client is disabling control for remote X client. Putty does not allow this but Xming shortcut can be modify to use -ac. It is also equivalent to xhost +.
â€“Â Jay jargot
Mar 18 '16 at 4:25

I have updated the answer. Could you give it a try and tell me if it is better?
â€“Â Jay jargot
Mar 18 '16 at 9:26

Thanks. I've tried both xming with commandline parameter and xlaunch with additional parameter for xming. There still was one second delay before mc or codeblocks started.
â€“Â martins
Mar 18 '16 at 12:30

What if it is not due to the X11 Trusted? I mean it is worth to sniff packets with wireshark in order to figure out what is going on?
â€“Â Jay jargot
Mar 18 '16 at 12:34

Thanks for your suggestion. I'll try compression, but I did not mentioned I was working on localhost in virtual machine. Unfortunately -X in putty means X11 on, while in linux/cygwin ssh command -X means untrusted and -Y trusted. I've corrected it in my answer.
â€“Â martins
Mar 17 '16 at 6:06

The ForwardX11Trusted for ssh client is disabling control for remote X client. Putty does not allow this but Xming shortcut can be modify to use -ac. It is also equivalent to xhost +.
â€“Â Jay jargot
Mar 18 '16 at 4:25

I have updated the answer. Could you give it a try and tell me if it is better?
â€“Â Jay jargot
Mar 18 '16 at 9:26

Thanks. I've tried both xming with commandline parameter and xlaunch with additional parameter for xming. There still was one second delay before mc or codeblocks started.
â€“Â martins
Mar 18 '16 at 12:30

What if it is not due to the X11 Trusted? I mean it is worth to sniff packets with wireshark in order to figure out what is going on?
â€“Â Jay jargot
Mar 18 '16 at 12:34

add a commentÂ |Â

up vote
0
down vote

answered Sep 8 at 13:07

Afsin Toparlak

38114

add a commentÂ |Â

up vote
0
down vote

answered Sep 8 at 13:07

Afsin Toparlak

38114

add a commentÂ |Â

up vote
0
down vote

answered Sep 8 at 13:07

Afsin Toparlak

38114

answered Sep 8 at 13:07

Afsin Toparlak

38114

answered Sep 8 at 13:07

Afsin Toparlak

38114

answered Sep 8 at 13:07

Afsin Toparlak

38114

answered Sep 8 at 13:07

Afsin Toparlak

38114

add a commentÂ |Â

draft saved

draft discarded

draft saved

draft discarded

Post as a guest

Name

搜尋此網誌

mjhjmtu