<?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: Send secure and encrypted text via email online</title>
	<atom:link href="http://www.online-tech-tips.com/cool-websites/send-secure-and-encrypted-text-via-email-online/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.online-tech-tips.com/cool-websites/send-secure-and-encrypted-text-via-email-online/</link>
	<description></description>
	<lastBuildDate>Mon, 23 Nov 2009 04:59:48 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Chris Biltcliffe</title>
		<link>http://www.online-tech-tips.com/cool-websites/send-secure-and-encrypted-text-via-email-online/comment-page-1/#comment-27126</link>
		<dc:creator>Chris Biltcliffe</dc:creator>
		<pubDate>Wed, 11 Nov 2009 21:51:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.online-tech-tips.com/?p=9802#comment-27126</guid>
		<description>&quot;Just make sure that no one else gets to know about the website other than the people you want to share private information with.&quot;

Great!  I was using this to encrypt all my super secret information, and now you&#039;ve gone and blabbed about it to everybody.  Now the bad guys know how to get at my super secret information!  Thanks a lot!

It&#039;s a website.  Which means Google knows about it.  And I think once Google knows about it, it&#039;s pretty safe to say the rest of the world does, too.

This is what would be considered either &quot;security theater,&quot; or &quot;security by obscurity,&quot; and is a prime example of what _not_ to do if you want your information to be secure.

The SHA1 hash is great for encrypting.  It&#039;s very secure.
But the most important part of the entire encryption process is that you know what the decryption key is, and NOBODY else does.
In this case, not only does somebody else (the website owner) know what the decryption key is, but you DON&#039;T!  You&#039;ve encrypted your super secret information, and given somebody you don&#039;t know the only key.

Not only that, but you&#039;ve also simply exchanged the insecure email for an insecure website.  If you&#039;re so concerned about BadGuy sniffing your or the recipient&#039;s email connection, then BadGuy is also going to be in a position to sniff the insecure connection to this website when you send your text to be encrypted/decrypted.

The ONLY secure method for email is to encrypt the email directly on your computer, with either the recipient&#039;s public key, or a shared key that only the two of you know.

A shared key is not as secure, because even if you delete the unencrypted copy of the email, someone can still decrypt with your copy of the shared key.
With the recipient&#039;s public key, once you&#039;ve encrypted the email, you cannot decrypt it again with the same key.  The only key that will decrypt that email is the recipient&#039;s private key, which you don&#039;t know.  If you properly delete the unencrypted email, the contents CANNOT be decrypted on your end, even if someone steals your computer.  The ONLY person who can decrypt is the recipient.

Now THAT&#039;S real security.</description>
		<content:encoded><![CDATA[<p>&#8220;Just make sure that no one else gets to know about the website other than the people you want to share private information with.&#8221;</p>
<p>Great!  I was using this to encrypt all my super secret information, and now you&#8217;ve gone and blabbed about it to everybody.  Now the bad guys know how to get at my super secret information!  Thanks a lot!</p>
<p>It&#8217;s a website.  Which means Google knows about it.  And I think once Google knows about it, it&#8217;s pretty safe to say the rest of the world does, too.</p>
<p>This is what would be considered either &#8220;security theater,&#8221; or &#8220;security by obscurity,&#8221; and is a prime example of what _not_ to do if you want your information to be secure.</p>
<p>The SHA1 hash is great for encrypting.  It&#8217;s very secure.<br />
But the most important part of the entire encryption process is that you know what the decryption key is, and NOBODY else does.<br />
In this case, not only does somebody else (the website owner) know what the decryption key is, but you DON&#8217;T!  You&#8217;ve encrypted your super secret information, and given somebody you don&#8217;t know the only key.</p>
<p>Not only that, but you&#8217;ve also simply exchanged the insecure email for an insecure website.  If you&#8217;re so concerned about BadGuy sniffing your or the recipient&#8217;s email connection, then BadGuy is also going to be in a position to sniff the insecure connection to this website when you send your text to be encrypted/decrypted.</p>
<p>The ONLY secure method for email is to encrypt the email directly on your computer, with either the recipient&#8217;s public key, or a shared key that only the two of you know.</p>
<p>A shared key is not as secure, because even if you delete the unencrypted copy of the email, someone can still decrypt with your copy of the shared key.<br />
With the recipient&#8217;s public key, once you&#8217;ve encrypted the email, you cannot decrypt it again with the same key.  The only key that will decrypt that email is the recipient&#8217;s private key, which you don&#8217;t know.  If you properly delete the unencrypted email, the contents CANNOT be decrypted on your end, even if someone steals your computer.  The ONLY person who can decrypt is the recipient.</p>
<p>Now THAT&#8217;S real security.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
