<?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: how can I secure the information sent from my asp.net application to an email recepient?</title>
	<atom:link href="http://blog.emailingforyou.com/2009/12/how-can-i-secure-the-information-sent-from-my-aspnet-application-to-an-email-recepient/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.emailingforyou.com/2009/12/how-can-i-secure-the-information-sent-from-my-aspnet-application-to-an-email-recepient/</link>
	<description>Great blog about emailing</description>
	<lastBuildDate>Fri, 28 Jan 2011 00:11:43 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: ignacionr2</title>
		<link>http://blog.emailingforyou.com/2009/12/how-can-i-secure-the-information-sent-from-my-aspnet-application-to-an-email-recepient/comment-page-1/#comment-886</link>
		<dc:creator>ignacionr2</dc:creator>
		<pubDate>Thu, 31 Dec 2009 18:51:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.emailingforyou.com/2009/12/how-can-i-secure-the-information-sent-from-my-aspnet-application-to-an-email-recepient/#comment-886</guid>
		<description>SSL is involved in the sense that you can accept a client-side certificate. That will bring you a public RSA key.

With that key you can create a propperly formatted, secure (in the sense that only who posseses the private part of that key will be able to read the contents) email. That email is not secure in itself (it can travel through many servers and each get a chance to read it), but the contents are (what those servers will read will not make sense).

Try the link below for explanations and components.</description>
		<content:encoded><![CDATA[<p>SSL is involved in the sense that you can accept a client-side certificate. That will bring you a public RSA key.</p>
<p>With that key you can create a propperly formatted, secure (in the sense that only who posseses the private part of that key will be able to read the contents) email. That email is not secure in itself (it can travel through many servers and each get a chance to read it), but the contents are (what those servers will read will not make sense).</p>
<p>Try the link below for explanations and components.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kryzchek</title>
		<link>http://blog.emailingforyou.com/2009/12/how-can-i-secure-the-information-sent-from-my-aspnet-application-to-an-email-recepient/comment-page-1/#comment-885</link>
		<dc:creator>Kryzchek</dc:creator>
		<pubDate>Mon, 28 Dec 2009 17:05:25 +0000</pubDate>
		<guid isPermaLink="false">http://blog.emailingforyou.com/2009/12/how-can-i-secure-the-information-sent-from-my-aspnet-application-to-an-email-recepient/#comment-885</guid>
		<description>You can use PGP to encrypt the email. Conversely, you could use some hashing or encryption algorithm like MD5 to scramble the field. Once you receive the email, you can decode it yourself.</description>
		<content:encoded><![CDATA[<p>You can use PGP to encrypt the email. Conversely, you could use some hashing or encryption algorithm like MD5 to scramble the field. Once you receive the email, you can decode it yourself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nick2600ii</title>
		<link>http://blog.emailingforyou.com/2009/12/how-can-i-secure-the-information-sent-from-my-aspnet-application-to-an-email-recepient/comment-page-1/#comment-884</link>
		<dc:creator>nick2600ii</dc:creator>
		<pubDate>Sat, 26 Dec 2009 00:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.emailingforyou.com/2009/12/how-can-i-secure-the-information-sent-from-my-aspnet-application-to-an-email-recepient/#comment-884</guid>
		<description>As far as I know Email is unencrypted and cannot be encrypted. However, you may be able to throw the information/data into an encrypted file and attach it to an email then encrypt it once it gets back into your computer.

I&#039;m not positive on the email encryption thing so if anyone else knows for sure let me know.</description>
		<content:encoded><![CDATA[<p>As far as I know Email is unencrypted and cannot be encrypted. However, you may be able to throw the information/data into an encrypted file and attach it to an email then encrypt it once it gets back into your computer.</p>
<p>I&#8217;m not positive on the email encryption thing so if anyone else knows for sure let me know.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

