<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: How To Remote Access Ubuntu Desktop</title>
	<atom:link href="http://techvirgin.com/2009/03/how-to-remote-access-ubuntu-desktop/feed/" rel="self" type="application/rss+xml" />
	<link>http://techvirgin.com/2009/03/how-to-remote-access-ubuntu-desktop/</link>
	<description>where technology is simplified</description>
	<lastBuildDate>Sun, 10 Jul 2011 06:02:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Tweets that mention How To Remote Access Ubuntu Desktop &#124; TechVirgin.com -- Topsy.com</title>
		<link>http://techvirgin.com/2009/03/how-to-remote-access-ubuntu-desktop/#comment-725</link>
		<dc:creator>Tweets that mention How To Remote Access Ubuntu Desktop &#124; TechVirgin.com -- Topsy.com</dc:creator>
		<pubDate>Tue, 06 Jul 2010 15:40:58 +0000</pubDate>
		<guid isPermaLink="false">http://techvirgin.com/?p=499#comment-725</guid>
		<description>[...] This post was mentioned on Twitter by AF Gavito. AF Gavito said: How To Remote Access Ubuntu Desktop &#124; TechVirgin.com: http://bit.ly/9BqkxE via @addthis [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by AF Gavito. AF Gavito said: How To Remote Access Ubuntu Desktop | TechVirgin.com: <a href="http://bit.ly/9BqkxE" rel="nofollow">http://bit.ly/9BqkxE</a> via @addthis [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: louis vuitton shoes</title>
		<link>http://techvirgin.com/2009/03/how-to-remote-access-ubuntu-desktop/#comment-723</link>
		<dc:creator>louis vuitton shoes</dc:creator>
		<pubDate>Tue, 01 Jun 2010 04:07:20 +0000</pubDate>
		<guid isPermaLink="false">http://techvirgin.com/?p=499#comment-723</guid>
		<description>I belive in fairy tales, the prince and the princess were living in the golden castle blissfully and guarding their love. Elfs in the world was watching us form the darkness, I standed in the rye, violent sneezed, golden poppled.&lt;br&gt;&lt;a href=&quot;http://www.correctalittle.com/&quot; rel=&quot;nofollow&quot;&gt;http://www.correctalittle.com/&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>I belive in fairy tales, the prince and the princess were living in the golden castle blissfully and guarding their love. Elfs in the world was watching us form the darkness, I standed in the rye, violent sneezed, golden poppled.<br /><a href="http://www.correctalittle.com/" rel="nofollow">http://www.correctalittle.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: louis vuitton shoes</title>
		<link>http://techvirgin.com/2009/03/how-to-remote-access-ubuntu-desktop/#comment-724</link>
		<dc:creator>louis vuitton shoes</dc:creator>
		<pubDate>Tue, 01 Jun 2010 04:06:37 +0000</pubDate>
		<guid isPermaLink="false">http://techvirgin.com/?p=499#comment-724</guid>
		<description>The first visit, feel this blog is very good&lt;br&gt;&lt;a href=&quot;http://www.correctalittle.com/&quot; rel=&quot;nofollow&quot;&gt;http://www.correctalittle.com/&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>The first visit, feel this blog is very good<br /><a href="http://www.correctalittle.com/" rel="nofollow">http://www.correctalittle.com/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: techvirgin</title>
		<link>http://techvirgin.com/2009/03/how-to-remote-access-ubuntu-desktop/#comment-722</link>
		<dc:creator>techvirgin</dc:creator>
		<pubDate>Wed, 13 May 2009 16:04:29 +0000</pubDate>
		<guid isPermaLink="false">http://techvirgin.com/?p=499#comment-722</guid>
		<description>The last sentence sums up quite nicely - if you want to lazily access the Ubuntu desktop without typing much then VNC is the way to go. Otherwise, as you said, SSH would be a better option. Thanks for sharing Chris.</description>
		<content:encoded><![CDATA[<p>The last sentence sums up quite nicely &#8211; if you want to lazily access the Ubuntu desktop without typing much then VNC is the way to go. Otherwise, as you said, SSH would be a better option. Thanks for sharing Chris.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Browne</title>
		<link>http://techvirgin.com/2009/03/how-to-remote-access-ubuntu-desktop/#comment-721</link>
		<dc:creator>Chris Browne</dc:creator>
		<pubDate>Sun, 10 May 2009 11:31:29 +0000</pubDate>
		<guid isPermaLink="false">http://techvirgin.com/?p=499#comment-721</guid>
		<description>Firstly, this has been available for Linux more or less since X began, so it&#039;s nothing new and nothing exciting and it predates LogMeIn by about 20 years or so.  It is also much, much less secure than LogMeIn but I will explain why in a moment.

This is not the best way to access your own computer.  This is the best way for other users to access your computer on a view-only basis.  If you want to access your own computer, use another linux/unix/bsd host and use the command &quot;ssh -X&quot;.  You will need to enable the remote terminal (ssh) service using the system&gt;administration&gt;services dialogue.

X over SSH is, as you should already know, encrypted.  It also only allows much greater control over user rights, should you want other (less trustworthy, and believe me - everyone is less trustworthy than you with your computer) users to use the service you should use the useradd command and give them their own UNIX account which you can then set up to allow them to use what you want them to use and disallow everything else.

VNC is, by default, unencrypted and does not require a user account (and only optionally requires a password).  It is a good idea to set a password, but we&#039;ll move on to why that isn&#039;t strictly necessary in a moment.  The reason for its lack of security is because VNC is intended for use only on trusted networks - not over the internet.  You should set up VNC without that third (UPnP) option, unless you want the entire world to have access to your computer.  You can set a password, but you should rather avoid the port forwarding and simply tunnel VNC over a VPN should you want to connect from elsewhere.  Since you are always connecting from a trusted host, it is ok not to set a password.  However, should you be connected to (for example) a University network, it is advisable to set one anyway.  That is if you are even ballsy enough to use VNC on a Uni network - it seems a bit silly to &quot;trust&quot; a network which is literally full of students (some of which, presumably, are studying computer science).

So, to sum up:
XoSSH (ssh -X) is for remote access.
VNC (vinagre) is for remote viewing.

On one final note, anybody who has actually compared the two technologies will agree on more than just a security standpoint - the remote control features of VNC leave a lot to be desired (as do the remote viewing features of XoSSH, for that matter, which is oddly how I came across this article - I was looking for information on setting up VNC to remotely view my computer from a laptop, because I&#039;m lazy like that)</description>
		<content:encoded><![CDATA[<p>Firstly, this has been available for Linux more or less since X began, so it&#039;s nothing new and nothing exciting and it predates LogMeIn by about 20 years or so.  It is also much, much less secure than LogMeIn but I will explain why in a moment.</p>
<p>This is not the best way to access your own computer.  This is the best way for other users to access your computer on a view-only basis.  If you want to access your own computer, use another linux/unix/bsd host and use the command &quot;ssh -X&quot;.  You will need to enable the remote terminal (ssh) service using the system&gt;administration&gt;services dialogue.</p>
<p>X over SSH is, as you should already know, encrypted.  It also only allows much greater control over user rights, should you want other (less trustworthy, and believe me &#8211; everyone is less trustworthy than you with your computer) users to use the service you should use the useradd command and give them their own UNIX account which you can then set up to allow them to use what you want them to use and disallow everything else.</p>
<p>VNC is, by default, unencrypted and does not require a user account (and only optionally requires a password).  It is a good idea to set a password, but we&#039;ll move on to why that isn&#039;t strictly necessary in a moment.  The reason for its lack of security is because VNC is intended for use only on trusted networks &#8211; not over the internet.  You should set up VNC without that third (UPnP) option, unless you want the entire world to have access to your computer.  You can set a password, but you should rather avoid the port forwarding and simply tunnel VNC over a VPN should you want to connect from elsewhere.  Since you are always connecting from a trusted host, it is ok not to set a password.  However, should you be connected to (for example) a University network, it is advisable to set one anyway.  That is if you are even ballsy enough to use VNC on a Uni network &#8211; it seems a bit silly to &quot;trust&quot; a network which is literally full of students (some of which, presumably, are studying computer science).</p>
<p>So, to sum up:<br />
XoSSH (ssh -X) is for remote access.<br />
VNC (vinagre) is for remote viewing.</p>
<p>On one final note, anybody who has actually compared the two technologies will agree on more than just a security standpoint &#8211; the remote control features of VNC leave a lot to be desired (as do the remote viewing features of XoSSH, for that matter, which is oddly how I came across this article &#8211; I was looking for information on setting up VNC to remotely view my computer from a laptop, because I&#039;m lazy like that)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

