<?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: Hold On to Your Wallet: Another Huge VoIP Phone Bill May Be Lurking	</title>
	<atom:link href="https://nerdvittles.com/hold-on-to-your-wallet-another-huge-voip-phone-bill-may-be-lurking/feed/" rel="self" type="application/rss+xml" />
	<link>https://nerdvittles.com/hold-on-to-your-wallet-another-huge-voip-phone-bill-may-be-lurking/</link>
	<description>Ward Mundy&#039;s Technobabblelog</description>
	<lastBuildDate>Wed, 06 Apr 2016 15:03:17 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Greg		</title>
		<link>https://nerdvittles.com/hold-on-to-your-wallet-another-huge-voip-phone-bill-may-be-lurking/comment-page-1/#comment-170853</link>

		<dc:creator><![CDATA[Greg]]></dc:creator>
		<pubDate>Sun, 02 Nov 2014 03:33:26 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=10779#comment-170853</guid>

					<description><![CDATA[Your advice is sensible but, for people who are willing to keep their system updated, i think it is too conservative.  Running ssh on port 22 and apache on port 80 is something numerous people do, and which is not all that risky so long as you keep your system updated and take reasonable security precautions (like using strong passwords).  Without letting these ports remain accessible, it is impossible to run some important and useful services, such as a web site.

&lt;i&gt;[WM: A telephony server is NOT the appropriate place to host a public web site! There are plenty of web hosting options which cost next to nothing to implement without jeopardizing your telephony server. All of the services you mention can be utilized on a telephony server with implementation of a WhiteList-enhanced IPtables firewall. In this way, you don&#039;t jeopardize the overall security of your server.]&lt;/i&gt;]]></description>
			<content:encoded><![CDATA[<p>Your advice is sensible but, for people who are willing to keep their system updated, i think it is too conservative.  Running ssh on port 22 and apache on port 80 is something numerous people do, and which is not all that risky so long as you keep your system updated and take reasonable security precautions (like using strong passwords).  Without letting these ports remain accessible, it is impossible to run some important and useful services, such as a web site.</p>
<p><i>[WM: A telephony server is NOT the appropriate place to host a public web site! There are plenty of web hosting options which cost next to nothing to implement without jeopardizing your telephony server. All of the services you mention can be utilized on a telephony server with implementation of a WhiteList-enhanced IPtables firewall. In this way, you don&#8217;t jeopardize the overall security of your server.]</i></p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
