<?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: Digital Signatures</title>
	<atom:link href="http://geminisecurity.com/technologies/digital-signatures/feed/" rel="self" type="application/rss+xml" />
	<link>http://geminisecurity.com</link>
	<description></description>
	<lastBuildDate>Fri, 11 Jun 2010 14:02:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Security Musings &#187; Blog Archive &#187; Analysis of a Forged Email</title>
		<link>http://geminisecurity.com/technologies/digital-signatures/#comment-55</link>
		<dc:creator>Security Musings &#187; Blog Archive &#187; Analysis of a Forged Email</dc:creator>
		<pubDate>Wed, 21 Oct 2009 05:14:18 +0000</pubDate>
		<guid isPermaLink="false">http://geminisecurity.com/?page_id=17#comment-55</guid>
		<description>[...] But if its so easy, there has to be a way to prevent it, right? Sure, there are plenty of ways to verify that a message came from who it claims to come from (authentication). One such method is digital signatures which make use of asymmetric cryptography. If you&#8217;re interested in learning about the benefits of digital signatures, we offer training. [...]</description>
		<content:encoded><![CDATA[<p>[...] But if its so easy, there has to be a way to prevent it, right? Sure, there are plenty of ways to verify that a message came from who it claims to come from (authentication). One such method is digital signatures which make use of asymmetric cryptography. If you&#8217;re interested in learning about the benefits of digital signatures, we offer training. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

