<?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: VPN&#8217;s: IPSec vs. SSL</title>
	<atom:link href="http://www.tonybradley.com/2009/08/vpns-ipsec-vs-ssl/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tonybradley.com/2009/08/vpns-ipsec-vs-ssl/</link>
	<description>Computer Security In Plain English For Normal People</description>
	<lastBuildDate>Wed, 03 Mar 2010 17:29:50 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: VPN Haus</title>
		<link>http://www.tonybradley.com/2009/08/vpns-ipsec-vs-ssl/comment-page-1/#comment-841</link>
		<dc:creator>VPN Haus</dc:creator>
		<pubDate>Mon, 17 Aug 2009 14:41:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.tonybradley.com/?p=1904#comment-841</guid>
		<description>“Traditional IPsec solutions are complicated.  Consequently, SSL VPN solutions were introduced with the intention to be clientless and easy.  However, this was not the case, and in fact, SSL requires a thin or fat client to enable all of the features users require.  In your post, you make many interesting and accurate points—but what about addressing new IPsec solutions.  NCP has developed a client, which is a hybrid of IPsec and SSL that solves the problems you describe above.  This solution also eases the problems associated with remote PCs/Laptops.”</description>
		<content:encoded><![CDATA[<p>“Traditional IPsec solutions are complicated.  Consequently, SSL VPN solutions were introduced with the intention to be clientless and easy.  However, this was not the case, and in fact, SSL requires a thin or fat client to enable all of the features users require.  In your post, you make many interesting and accurate points—but what about addressing new IPsec solutions.  NCP has developed a client, which is a hybrid of IPsec and SSL that solves the problems you describe above.  This solution also eases the problems associated with remote PCs/Laptops.”</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Etherealmind</title>
		<link>http://www.tonybradley.com/2009/08/vpns-ipsec-vs-ssl/comment-page-1/#comment-832</link>
		<dc:creator>Etherealmind</dc:creator>
		<pubDate>Fri, 14 Aug 2009 08:54:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.tonybradley.com/?p=1904#comment-832</guid>
		<description>You are not entirely correct. SSL VPNs support a full range of site to site VPN functionality whereas you suggest that it only operates in a web browser. In fact, SSL VPN typically supports three modes:
- browser only
- thin client mode supporting port forwarding by downloading an agent from within the browser
- full client support  equivalent to IPSec. 

This capability has been available for several years and its surprising that you are not aware of it. 

You have also made no mention of the fact that SSL VPN require expensive licenses and cost a substantial amount for most commercial implementation from the main vendors.</description>
		<content:encoded><![CDATA[<p>You are not entirely correct. SSL VPNs support a full range of site to site VPN functionality whereas you suggest that it only operates in a web browser. In fact, SSL VPN typically supports three modes:<br />
- browser only<br />
- thin client mode supporting port forwarding by downloading an agent from within the browser<br />
- full client support  equivalent to IPSec. </p>
<p>This capability has been available for several years and its surprising that you are not aware of it. </p>
<p>You have also made no mention of the fact that SSL VPN require expensive licenses and cost a substantial amount for most commercial implementation from the main vendors.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
