On 09/13/2011 11:06 AM, Warp wrote:
> Invisible<voi### [at] devnull>  wrote:
>> On 13/09/2011 11:25 AM, Warp wrote:
>>> Invisible<voi### [at] devnull>   wrote:
>>>> Now I haven't tried it, but I'm told is approximately /impossible/ to
>>>> actually configure X so that you can access it remotely. Even though
>>>> that's its entire design goal.
>>>
>>>     I don't know what you mean.
>>>
>>>     For the sake of it, I just now tried to do a "ssh -X" to a friend's computer
>>> (who is also running linux) and ran xclock. It opened nicely on my screen,
>>> even though the program itself is running on my friend's computer (which is
>>> physically located something like 200 km from here).
>
>> Like I said, I haven't personally tried to run X remotely. (I wouldn't
>> know how.) I'm told it requires spending hours editing the X
>> configuration files to set up authentication and so forth, and then to
>> make sure the server is started, and then to tell the application you
>> want to run to open on the remote machine rather than the local one (by
>> using CLI options that vary for every individual program so you have to
>> look them up), and then...
>
>> And that's without encryption. If you want encryption, now you have to
>> also install and configure an ssh server and client, set up
>> authentication and encryption keys and god-knows what else.
>
>    Didn't you read what I wrote above?
>
>    Short answer: No, you don't. (I didn't have to do any configuration to get
> that test working. I just did it, and it worked. The only thing I had to
> know was that you have to give ssh the parameter -X to enable X forwarding,
> which is disabled by default for safety reasons. And the connection is,
> obviously fully encrypted because it happens through ssh.)
>
>> So you're seriously telling me that with a default Linux install, not
>> only is an ssh server installed, but it's actually configured to allow
>> incoming connections and service them? And that X will actually work in
>> this configuration?
>
>    I don't remember if sshd is enabled by default on OpenSuse, but it's
> as easy to enable as doing a couple of mouse clicks (and typing the root
> password, so that yast can perform the system modifications). IIRC it even
> offers you to automatically open the ssh port on the firewall.
>
confirm this last part as I'm on OpenSuse as well ... t'was a piece of 
cake from Yast, but if you know the process the command-line method is 
not /that/ cumbersome either

Post a reply to this message