<?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: WS-Security versus SOA over SSL</title>
	<atom:link href="http://cosine.org/2007/10/25/wss-vs-ssl/feed/" rel="self" type="application/rss+xml" />
	<link>http://cosine.org/2007/10/25/wss-vs-ssl/</link>
	<description>Life and Ruby and Security</description>
	<lastBuildDate>Sun, 11 Dec 2011 12:10:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
	<item>
		<title>By: Cosine Jeremiah</title>
		<link>http://cosine.org/2007/10/25/wss-vs-ssl/comment-page-1/#comment-404</link>
		<dc:creator>Cosine Jeremiah</dc:creator>
		<pubDate>Sat, 27 Oct 2007 21:33:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.cosine.org/2007/10/25/wss-vs-ssl/#comment-404</guid>
		<description>It is true one could use WS-Security in a mode that would spare the use of some of the asymmetric encryption, but I think the ideal of doing things with the most stringent security would have both encryption and signing certificates used by both the client and the server.  Thus I did not really consider doing it any other way for the purpose of this comparison.

The asymmetric encryption used to protect the message is always just to encrypt a symmetric encryption key that is used to encrypt the actual contents of the message, as you said (and like SSL as you also said).  Even so, that little bit of asymmetric encryption gets expensive when multiplied by a heavy load of messages.  The symmetric encryption computation time, on the other hand, is cake by comparison.

Let me know if your understanding is different.</description>
		<content:encoded><![CDATA[<p>It is true one could use WS-Security in a mode that would spare the use of some of the asymmetric encryption, but I think the ideal of doing things with the most stringent security would have both encryption and signing certificates used by both the client and the server.  Thus I did not really consider doing it any other way for the purpose of this comparison.</p>
<p>The asymmetric encryption used to protect the message is always just to encrypt a symmetric encryption key that is used to encrypt the actual contents of the message, as you said (and like SSL as you also said).  Even so, that little bit of asymmetric encryption gets expensive when multiplied by a heavy load of messages.  The symmetric encryption computation time, on the other hand, is cake by comparison.</p>
<p>Let me know if your understanding is different.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan</title>
		<link>http://cosine.org/2007/10/25/wss-vs-ssl/comment-page-1/#comment-352</link>
		<dc:creator>Ryan</dc:creator>
		<pubDate>Fri, 26 Oct 2007 02:13:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.cosine.org/2007/10/25/wss-vs-ssl/#comment-352</guid>
		<description>Good summary.  You do seem to be forgetting or missing one of the modes WS-Security can operate in.

&quot;whereas WS-Security needs to perform asymmetric key encryption on each message (one computation for handling encryption and one computation for handling the signature)&quot;

While you can&#039;t get away from the need for a server certificate, you can use WS-Security without a client certificate, and you often will use symmetric encryption as part of the message.  You&#039;re right that you&#039;ll definitely use asymmetric in the message, but it might be used just for key exchange like SSL.  Actually I think this is the more common usage.  Of course it&#039;s still per message.</description>
		<content:encoded><![CDATA[<p>Good summary.  You do seem to be forgetting or missing one of the modes WS-Security can operate in.</p>
<p>&#8220;whereas WS-Security needs to perform asymmetric key encryption on each message (one computation for handling encryption and one computation for handling the signature)&#8221;</p>
<p>While you can&#8217;t get away from the need for a server certificate, you can use WS-Security without a client certificate, and you often will use symmetric encryption as part of the message.  You&#8217;re right that you&#8217;ll definitely use asymmetric in the message, but it might be used just for key exchange like SSL.  Actually I think this is the more common usage.  Of course it&#8217;s still per message.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

