From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: sshd interaction with desktop not working
Date: Tue, 09 Feb 2016 12:56:00 -0000 [thread overview]
Message-ID: <56B9E1F1.9080503@cygwin.com> (raw)
In-Reply-To: <CAHB2L+ct03oQVgQ27m=oPC41qMvXvwrO0Zm63SDidmujUJd47Q@mail.gmail.com>
On 2/9/2016 4:49 AM, Aijaz Baig wrote:
> Hello
>
> I am SSH'ing into a windows 10 box from a Linux box. I've configured
> sshd on the windows box and I can properly SSH into it.
>
> X11 forwarding also works perfectly after having installed Xming on
> windows (not that it matters with this problem anyways).
>
> However I am unable to open any windows application from the Linux
> box. I would like to open the windows app locally in the windows box
> (or to rephrase it, I do not need the UI windows to be opened on the
> Linux box)
>
> I am unable to figure out why it is not working even after selecting
> "Allow service to interact with desktop". My goal is to invoke windows
> app from ssh (Linux to Windows). Similar problems earlier were solved
> by selecting this option but apparently they were on earlier version
> of windows.
>
> Or should I take a different approach? Am I barking at the wrong tree here??
>
> I am keen to hear from input(s)
Wrong tree, yes. Microsoft chopped down the tree you want and planted a new
one in its place. In short, the restriction was introduced post-XP as it
is considered a security hole. There have been sporadic subsequent reports
of success to this list but never a clear recipe for getting this to work
reliably. And given that this is perceived as a security hole, I doubt
you'll find one that doesn't include some significant effort and/or
restrictions. If you search around for "Windows station" and "Allow
service to interact with desktop", I think you'll find some relevant
information.
--
Larry
_____________________________________________________________________
A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2016-02-09 12:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-09 9:49 Aijaz Baig
2016-02-09 12:56 ` Larry Hall (Cygwin) [this message]
2016-02-11 7:00 ` Aijaz Baig
2016-02-11 12:05 ` Andrey Repin
2018-03-16 18:00 ` mhallnh
2018-03-17 6:16 ` Andrey Repin
2018-03-17 20:05 ` mhallnh
2018-03-17 20:21 ` R0b0t1
2018-03-18 15:34 ` mhallnh
2018-03-18 16:19 ` R0b0t1
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56B9E1F1.9080503@cygwin.com \
--to=reply-to-list-only-lh@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).