<?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: Another Asterisk Security Hole to Plug in TrixBox Systems (updated)	</title>
	<atom:link href="https://nerdvittles.com/another-asterisk-security-hole-to-plug/feed/" rel="self" type="application/rss+xml" />
	<link>https://nerdvittles.com/another-asterisk-security-hole-to-plug/</link>
	<description>Ward Mundy&#039;s Technobabblelog</description>
	<lastBuildDate>Thu, 02 Jun 2011 13:54:32 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Joe		</title>
		<link>https://nerdvittles.com/another-asterisk-security-hole-to-plug/comment-page-1/#comment-2650</link>

		<dc:creator><![CDATA[Joe]]></dc:creator>
		<pubDate>Fri, 04 May 2007 01:33:46 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=178#comment-2650</guid>

					<description><![CDATA[I used zaptel-1.2.17.1 and Ward&#039;s instructions for upgrade with no problems whatsoever.]]></description>
			<content:encoded><![CDATA[<p>I used zaptel-1.2.17.1 and Ward&#8217;s instructions for upgrade with no problems whatsoever.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Costa		</title>
		<link>https://nerdvittles.com/another-asterisk-security-hole-to-plug/comment-page-1/#comment-2648</link>

		<dc:creator><![CDATA[Costa]]></dc:creator>
		<pubDate>Wed, 02 May 2007 09:46:14 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=178#comment-2648</guid>

					<description><![CDATA[Digium is only hosting zaptel-1.2.17.1 now, NOT zaptel-1.2.17.
With that and comment #6 (Michael) I&#039;m going to hold off due
to the phear phactor alone.

&lt;i&gt;[WM: Yeah, it&#039;s been a rough couple of weeks for the developers. Been there, done that.]&lt;/i&gt;]]></description>
			<content:encoded><![CDATA[<p>Digium is only hosting zaptel-1.2.17.1 now, NOT zaptel-1.2.17.<br />
With that and comment #6 (Michael) I&#8217;m going to hold off due<br />
to the phear phactor alone.</p>
<p><i>[WM: Yeah, it&#8217;s been a rough couple of weeks for the developers. Been there, done that.]</i></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: michael		</title>
		<link>https://nerdvittles.com/another-asterisk-security-hole-to-plug/comment-page-1/#comment-2643</link>

		<dc:creator><![CDATA[michael]]></dc:creator>
		<pubDate>Sun, 29 Apr 2007 20:17:00 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=178#comment-2643</guid>

					<description><![CDATA[Beware, I&#039;ve upgraded last weekend to zaptel-1.2.17.1, and the system totaly crashed with Kernel Panic. Even the Linux was stuck and I had to reinstall everything from scratch on a production sever. I use Trixbox 2.0 and Sangoma A200. FYI..]]></description>
			<content:encoded><![CDATA[<p>Beware, I&#8217;ve upgraded last weekend to zaptel-1.2.17.1, and the system totaly crashed with Kernel Panic. Even the Linux was stuck and I had to reinstall everything from scratch on a production sever. I use Trixbox 2.0 and Sangoma A200. FYI..</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Ed Lally		</title>
		<link>https://nerdvittles.com/another-asterisk-security-hole-to-plug/comment-page-1/#comment-2642</link>

		<dc:creator><![CDATA[Ed Lally]]></dc:creator>
		<pubDate>Fri, 27 Apr 2007 19:23:05 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=178#comment-2642</guid>

					<description><![CDATA[Ward,

Is there any particular reason not to update asterisk via yum?  It&#039;s installed on the Trixbox 1.2.3 systems by default, and a simple &quot;yum -y update asterisk&quot; took care of my upgrade rather nicely.

&lt;i&gt;[WM: The yum option wasn&#039;t available when the article was written.]&lt;/i&gt;]]></description>
			<content:encoded><![CDATA[<p>Ward,</p>
<p>Is there any particular reason not to update asterisk via yum?  It&#8217;s installed on the Trixbox 1.2.3 systems by default, and a simple &#8220;yum -y update asterisk&#8221; took care of my upgrade rather nicely.</p>
<p><i>[WM: The yum option wasn&#8217;t available when the article was written.]</i></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Dan		</title>
		<link>https://nerdvittles.com/another-asterisk-security-hole-to-plug/comment-page-1/#comment-2637</link>

		<dc:creator><![CDATA[Dan]]></dc:creator>
		<pubDate>Thu, 26 Apr 2007 06:51:37 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=178#comment-2637</guid>

					<description><![CDATA[Some of these versions are already out of date.  Is it safe to go with zaptel-1.2.17.1 and asterisk-addons-1.2.6?

&lt;i&gt;[WM: Beats me, but there&#039;s usually a very good reason for the new releases. So much for testing. Go for it! We&#039;ve updated the article as well.]&lt;/i&gt;]]></description>
			<content:encoded><![CDATA[<p>Some of these versions are already out of date.  Is it safe to go with zaptel-1.2.17.1 and asterisk-addons-1.2.6?</p>
<p><i>[WM: Beats me, but there&#8217;s usually a very good reason for the new releases. So much for testing. Go for it! We&#8217;ve updated the article as well.]</i></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Andrew		</title>
		<link>https://nerdvittles.com/another-asterisk-security-hole-to-plug/comment-page-1/#comment-2636</link>

		<dc:creator><![CDATA[Andrew]]></dc:creator>
		<pubDate>Thu, 26 Apr 2007 06:34:14 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=178#comment-2636</guid>

					<description><![CDATA[First off, thanks for all the great help &amp; tips - I have a working system despite being a complete newbie.

One of the pieces of advice you gave, I fully intended to follow - not rushing into upgrading, but of course I didn&#039;t...

I was going to wait a few days before applying these patches, in case anything changed.  The following two lines do not work:

wget http://ftp.digium.com/pub/telephony/zaptel/zaptel-1.2.16.tar.gz
wget http://ftp.digium.com/pub/telephony/asterisk/asterisk-addons-1.2.5.tar.gz

The current versions are now 1.2.17.1 &amp; 1.2.6 respectively.  I wasn&#039;t sure whether to go for &#039;bleeding edge&#039; or follow your instructions, I went with the latter and used:

wget http://ftp.digium.com/pub/telephony/zaptel/releases/zaptel-1.2.16.tar.gz
wget http://ftp.digium.com/pub/telephony/asterisk/releases/asterisk-addons-1.2.5.tar.gz

This appears to have worked for me, I now await your next telling me I should have gone with the other option!

Many thanks again.

&lt;i&gt;[WM: Thanks for the heads up. Didn&#039;t know we were going to have to update this article EACH DAY when we wrote it.]&lt;/i&gt;]]></description>
			<content:encoded><![CDATA[<p>First off, thanks for all the great help &#038; tips &#8211; I have a working system despite being a complete newbie.</p>
<p>One of the pieces of advice you gave, I fully intended to follow &#8211; not rushing into upgrading, but of course I didn&#8217;t&#8230;</p>
<p>I was going to wait a few days before applying these patches, in case anything changed.  The following two lines do not work:</p>
<p>wget <a href="http://ftp.digium.com/pub/telephony/zaptel/zaptel-1.2.16.tar.gz" rel="nofollow ugc">http://ftp.digium.com/pub/telephony/zaptel/zaptel-1.2.16.tar.gz</a><br />
wget <a href="http://ftp.digium.com/pub/telephony/asterisk/asterisk-addons-1.2.5.tar.gz" rel="nofollow ugc">http://ftp.digium.com/pub/telephony/asterisk/asterisk-addons-1.2.5.tar.gz</a></p>
<p>The current versions are now 1.2.17.1 &#038; 1.2.6 respectively.  I wasn&#8217;t sure whether to go for &#8216;bleeding edge&#8217; or follow your instructions, I went with the latter and used:</p>
<p>wget <a href="http://ftp.digium.com/pub/telephony/zaptel/releases/zaptel-1.2.16.tar.gz" rel="nofollow ugc">http://ftp.digium.com/pub/telephony/zaptel/releases/zaptel-1.2.16.tar.gz</a><br />
wget <a href="http://ftp.digium.com/pub/telephony/asterisk/releases/asterisk-addons-1.2.5.tar.gz" rel="nofollow ugc">http://ftp.digium.com/pub/telephony/asterisk/releases/asterisk-addons-1.2.5.tar.gz</a></p>
<p>This appears to have worked for me, I now await your next telling me I should have gone with the other option!</p>
<p>Many thanks again.</p>
<p><i>[WM: Thanks for the heads up. Didn&#8217;t know we were going to have to update this article EACH DAY when we wrote it.]</i></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: cvander		</title>
		<link>https://nerdvittles.com/another-asterisk-security-hole-to-plug/comment-page-1/#comment-2633</link>

		<dc:creator><![CDATA[cvander]]></dc:creator>
		<pubDate>Wed, 25 Apr 2007 17:03:32 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=178#comment-2633</guid>

					<description><![CDATA[It appears that zaptel-1.2.16 is no longer available from ftp.digium.com .  In it&#039;s place use zaptel-1.2.17.tar.gz and you will be fine.]]></description>
			<content:encoded><![CDATA[<p>It appears that zaptel-1.2.16 is no longer available from <a href="http://ftp.digium.com" rel="nofollow ugc">http://ftp.digium.com</a> .  In it&#8217;s place use zaptel-1.2.17.tar.gz and you will be fine.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Tom King		</title>
		<link>https://nerdvittles.com/another-asterisk-security-hole-to-plug/comment-page-1/#comment-2632</link>

		<dc:creator><![CDATA[Tom King]]></dc:creator>
		<pubDate>Wed, 25 Apr 2007 15:49:41 +0000</pubDate>
		<guid isPermaLink="false">http://nerdvittles.com/?p=178#comment-2632</guid>

					<description><![CDATA[Hi Ward

I have updated my script to include your new steps and revised the source code revision numbers.

http://www.script-trix.us/updatesource.htm

So far it seems to work just great. Thanks for all of your hard work. 

Tom

&lt;i&gt;[WM: Tom&#039;s script will need a little updating for the new Zaptel and Addon modules which were released overnight. Tom has made this incredibly easy to fix. Just don&#039;t forget to do it.]&lt;/i&gt;]]></description>
			<content:encoded><![CDATA[<p>Hi Ward</p>
<p>I have updated my script to include your new steps and revised the source code revision numbers.</p>
<p><a href="http://www.script-trix.us/updatesource.htm" rel="nofollow ugc">http://www.script-trix.us/updatesource.htm</a></p>
<p>So far it seems to work just great. Thanks for all of your hard work. </p>
<p>Tom</p>
<p><i>[WM: Tom&#8217;s script will need a little updating for the new Zaptel and Addon modules which were released overnight. Tom has made this incredibly easy to fix. Just don&#8217;t forget to do it.]</i></p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
