<?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: SSH Port Forwarding &#8211; Local VS Remote</title>
	<atom:link href="http://www.walkernews.net/2007/07/22/ssh-port-forwarding-local-vs-remote/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.walkernews.net/2007/07/22/ssh-port-forwarding-local-vs-remote/</link>
	<description>A capsule of walker's experience in life...</description>
	<lastBuildDate>Mon, 06 Feb 2012 19:09:42 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: How To Allow Root Login To Telnet Server In Linux?</title>
		<link>http://www.walkernews.net/2007/07/22/ssh-port-forwarding-local-vs-remote/#comment-6976</link>
		<dc:creator>How To Allow Root Login To Telnet Server In Linux?</dc:creator>
		<pubDate>Tue, 17 Mar 2009 17:15:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.walkernews.net/2007/07/22/ssh-port-forwarding-local-vs-remote/#comment-6976</guid>
		<description>[...] at all.    So, I guess these people will only abandon telnet client when Microsoft start to bundle Secure Shell (SSH) clients with Windows OS :-( Now back to topic, if you really want to put the Linux host at risk by allowing [...]</description>
		<content:encoded><![CDATA[<p>[...] at all.    So, I guess these people will only abandon telnet client when Microsoft start to bundle Secure Shell (SSH) clients with Windows OS :-( Now back to topic, if you really want to put the Linux host at risk by allowing [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How To Fix Telnet Rejection Error of Name or Service Not Known: Illegal Seek - Walker News</title>
		<link>http://www.walkernews.net/2007/07/22/ssh-port-forwarding-local-vs-remote/#comment-6337</link>
		<dc:creator>How To Fix Telnet Rejection Error of Name or Service Not Known: Illegal Seek - Walker News</dc:creator>
		<pubDate>Wed, 19 Nov 2008 17:16:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.walkernews.net/2007/07/22/ssh-port-forwarding-local-vs-remote/#comment-6337</guid>
		<description>[...] all know that telnet is a good remote access protocol in the old days. Now, we prefer SSH protocol because SSH is a secure protocol, i.e. it’s not easy to hack.  However, for some reasons, telnet [...]</description>
		<content:encoded><![CDATA[<p>[...] all know that telnet is a good remote access protocol in the old days. Now, we prefer SSH protocol because SSH is a secure protocol, i.e. it’s not easy to hack.  However, for some reasons, telnet [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How To Fix Weird Character In Linux Man Page - Walker News</title>
		<link>http://www.walkernews.net/2007/07/22/ssh-port-forwarding-local-vs-remote/#comment-935</link>
		<dc:creator>How To Fix Weird Character In Linux Man Page - Walker News</dc:creator>
		<pubDate>Tue, 25 Sep 2007 16:19:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.walkernews.net/2007/07/22/ssh-port-forwarding-local-vs-remote/#comment-935</guid>
		<description>[...] you’re reading the Linux manual page over the remote session, either with SSH or Telnet protocol, you might notice that there are some weird characters display on some Linux man [...]</description>
		<content:encoded><![CDATA[<p>[...] you’re reading the Linux manual page over the remote session, either with SSH or Telnet protocol, you might notice that there are some weird characters display on some Linux man [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Walker</title>
		<link>http://www.walkernews.net/2007/07/22/ssh-port-forwarding-local-vs-remote/#comment-689</link>
		<dc:creator>Walker</dc:creator>
		<pubDate>Fri, 27 Jul 2007 14:25:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.walkernews.net/2007/07/22/ssh-port-forwarding-local-vs-remote/#comment-689</guid>
		<description>The Windows VNC Viewer connection string is wrong in this post too. The correct connection string with specific connection port should be

&lt;code&gt;localhost::777&lt;/code&gt;</description>
		<content:encoded><![CDATA[<p>The Windows VNC Viewer connection string is wrong in this post too. The correct connection string with specific connection port should be</p>
<p><code>localhost::777</code></p>
]]></content:encoded>
	</item>
</channel>
</rss>

