<?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"
	>
<channel>
	<title>Comments on: Secure Remote Desktop on Linux and Windows</title>
	<atom:link href="http://www.canerten.com/secure-remote-desktop-on-linux-and-windows/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.canerten.com/secure-remote-desktop-on-linux-and-windows/</link>
	<description>Adventures in Computing - Can Erten's Blog</description>
	<pubDate>Thu, 28 Aug 2008 19:33:17 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Bern</title>
		<link>http://www.canerten.com/secure-remote-desktop-on-linux-and-windows/#comment-27115</link>
		<dc:creator>Bern</dc:creator>
		<pubDate>Sat, 19 Jan 2008 23:50:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.canerten.com/secure-remote-desktop-on-linux-and-windows/#comment-27115</guid>
		<description>Tim is correct.  If you have an SSH server just sitting on the Internet with port 22 wide opened, you become a target for automated brute force attacks.  I noticed my server was being pounded with logins almost an hour every night.  I switched the port to 6667 and haven't had the problem since.  It is also a good idea to deny root login from ssh as that is the easiest way for an attacker to compromise your system.</description>
		<content:encoded><![CDATA[<p>Tim is correct.  If you have an SSH server just sitting on the Internet with port 22 wide opened, you become a target for automated brute force attacks.  I noticed my server was being pounded with logins almost an hour every night.  I switched the port to 6667 and haven&#8217;t had the problem since.  It is also a good idea to deny root login from ssh as that is the easiest way for an attacker to compromise your system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Can</title>
		<link>http://www.canerten.com/secure-remote-desktop-on-linux-and-windows/#comment-26329</link>
		<dc:creator>Can</dc:creator>
		<pubDate>Mon, 10 Dec 2007 09:33:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.canerten.com/secure-remote-desktop-on-linux-and-windows/#comment-26329</guid>
		<description>It is not the ssh port. It is the windows remote desktop port. The reason to change it windows doesn't allow to open the port because it is also hosting the server of remote desktop.</description>
		<content:encoded><![CDATA[<p>It is not the ssh port. It is the windows remote desktop port. The reason to change it windows doesn&#8217;t allow to open the port because it is also hosting the server of remote desktop.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Al</title>
		<link>http://www.canerten.com/secure-remote-desktop-on-linux-and-windows/#comment-26324</link>
		<dc:creator>Al</dc:creator>
		<pubDate>Mon, 10 Dec 2007 05:31:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.canerten.com/secure-remote-desktop-on-linux-and-windows/#comment-26324</guid>
		<description>Tim,
What's a reason of changing SSH port? Those who want to see you SSH port, no matter what U set up, will nmap you server.
:)</description>
		<content:encoded><![CDATA[<p>Tim,<br />
What&#8217;s a reason of changing SSH port? Those who want to see you SSH port, no matter what U set up, will nmap you server.<br />
 <img src='http://www.canerten.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Archer</title>
		<link>http://www.canerten.com/secure-remote-desktop-on-linux-and-windows/#comment-20685</link>
		<dc:creator>Tim Archer</dc:creator>
		<pubDate>Mon, 09 Apr 2007 23:47:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.canerten.com/secure-remote-desktop-on-linux-and-windows/#comment-20685</guid>
		<description>Agreed that the remote desktop connection is a great idea. I use it at work to centralize the development environment for all my developers.

If you're using SSH you may want to change the default port it runs on to discourage automated password crackers from finding your SSH service and running brute force password attacks on it. I did a small write on changing the port at:

&lt;a href="http://timarcher.com/?q=node/46" rel="nofollow"&gt;http://timarcher.com/?q=node/46&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>Agreed that the remote desktop connection is a great idea. I use it at work to centralize the development environment for all my developers.</p>
<p>If you&#8217;re using SSH you may want to change the default port it runs on to discourage automated password crackers from finding your SSH service and running brute force password attacks on it. I did a small write on changing the port at:</p>
<p><a href="http://timarcher.com/?q=node/46" rel="nofollow" onclick="javascript:pageTracker._trackPageview ('/outbound/timarcher.com');">http://timarcher.com/?q=node/46</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
