<?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: Telnet to the browser?</title>
	<atom:link href="http://www.shiningsilence.com/dbsdlog/2008/04/19/2795.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.shiningsilence.com/dbsdlog/2008/04/19/2795.html</link>
	<description>A running description of activity related to DragonFly BSD.</description>
	<pubDate>Fri, 21 Nov 2008 13:47:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Anonymous</title>
		<link>http://www.shiningsilence.com/dbsdlog/2008/04/19/2795.html#comment-22469</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Tue, 22 Apr 2008 13:54:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=2795#comment-22469</guid>
		<description>@Anonymous

The source snippets don't detail how the port is bound. It could be fairly securely bound just to localhost, like XAMPP does, or it could be bound to INADDR_ANY (that people outside the computer could telnet to).</description>
		<content:encoded><![CDATA[<p>@Anonymous</p>
<p>The source snippets don&#8217;t detail how the port is bound. It could be fairly securely bound just to localhost, like XAMPP does, or it could be bound to INADDR_ANY (that people outside the computer could telnet to).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://www.shiningsilence.com/dbsdlog/2008/04/19/2795.html#comment-22286</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Sun, 20 Apr 2008 15:11:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.shiningsilence.com/dbsdlog/?p=2795#comment-22286</guid>
		<description>This seems like a keen idea -  but .. the example shows leaving an open port that anyone can telnet to.

While great for the application it appears to leave the client wide-open to be exploited.  Am I missing something?</description>
		<content:encoded><![CDATA[<p>This seems like a keen idea -  but .. the example shows leaving an open port that anyone can telnet to.</p>
<p>While great for the application it appears to leave the client wide-open to be exploited.  Am I missing something?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
