<?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: The problem with VoIP Security</title>
	<atom:link href="http://www.ejovi.net/2005/09/25/the-problem-with-voip-security/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ejovi.net/2005/09/25/the-problem-with-voip-security/</link>
	<description></description>
	<pubDate>Thu, 16 Oct 2008 06:42:37 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: ejovi nuwere</title>
		<link>http://www.ejovi.net/2005/09/25/the-problem-with-voip-security/#comment-539</link>
		<dc:creator>ejovi nuwere</dc:creator>
		<pubDate>Mon, 26 Sep 2005 14:39:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.ejovi.net/2005/09/25/the-problem-with-voip-security/#comment-539</guid>
		<description>I agree. Most vendors are, and need to be focusing on "making it work." That's why I cut vendors a lot of slack. But we should be atleast talking about this issue now so we don't go through the whole cycle again of rushing to fix it at the very last minute.</description>
		<content:encoded><![CDATA[<p>I agree. Most vendors are, and need to be focusing on &#8220;making it work.&#8221; That&#8217;s why I cut vendors a lot of slack. But we should be atleast talking about this issue now so we don&#8217;t go through the whole cycle again of rushing to fix it at the very last minute.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: stijn</title>
		<link>http://www.ejovi.net/2005/09/25/the-problem-with-voip-security/#comment-538</link>
		<dc:creator>stijn</dc:creator>
		<pubDate>Mon, 26 Sep 2005 13:25:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.ejovi.net/2005/09/25/the-problem-with-voip-security/#comment-538</guid>
		<description>I agree with your pro-active approach by setting bad code on number one. But don't forget that code is written by humans and they make mistakes. Always.

Take buffer overflows, we have been knowing them for years and still every day those vulnerabilities pop up.

It will take a generation and education changes to produce coders with a security mindset. At the end of the day, it's the responsibility of you and me, security pros to provide the confidentiality of VoIP.
Not coders they deliver complex functionality.

For now, the companies spend more time in Return On Investment and functionality requirements...

If a VoIP connection can not match up with normal PSTN, it just won't be deployed.</description>
		<content:encoded><![CDATA[<p>I agree with your pro-active approach by setting bad code on number one. But don&#8217;t forget that code is written by humans and they make mistakes. Always.</p>
<p>Take buffer overflows, we have been knowing them for years and still every day those vulnerabilities pop up.</p>
<p>It will take a generation and education changes to produce coders with a security mindset. At the end of the day, it&#8217;s the responsibility of you and me, security pros to provide the confidentiality of VoIP.<br />
Not coders they deliver complex functionality.</p>
<p>For now, the companies spend more time in Return On Investment and functionality requirements&#8230;</p>
<p>If a VoIP connection can not match up with normal PSTN, it just won&#8217;t be deployed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
