<?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: The Case For Email Security</title>
	<atom:link href="http://luxsci.com/blog/the-case-for-email-security.html/feed" rel="self" type="application/rss+xml" />
	<link>http://luxsci.com/blog/the-case-for-email-security.html</link>
	<description>News, solutions and insider insight from LuxSci: provider of Secure Email and Web Security</description>
	<lastBuildDate>Thu, 08 Mar 2012 02:57:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=445</generator>
	<item>
		<title>By: Protect Your Passwords from Theft &#124; LuxSci FYI</title>
		<link>http://luxsci.com/blog/the-case-for-email-security.html/comment-page-1#comment-1265</link>
		<dc:creator>Protect Your Passwords from Theft &#124; LuxSci FYI</dc:creator>
		<pubDate>Tue, 03 May 2011 16:16:34 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=1511#comment-1265</guid>
		<description>[...] to other services, like email, chat, Facebook or Twitter, should also be made over SSL or TLS connections.  If you want to use a [...]</description>
		<content:encoded><![CDATA[<p>[...] to other services, like email, chat, Facebook or Twitter, should also be made over SSL or TLS connections.  If you want to use a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BIS - No Better Security than Web Based Mail - Page 7 - BlackBerry Forums Support Community</title>
		<link>http://luxsci.com/blog/the-case-for-email-security.html/comment-page-1#comment-1253</link>
		<dc:creator>BIS - No Better Security than Web Based Mail - Page 7 - BlackBerry Forums Support Community</dc:creator>
		<pubDate>Mon, 17 Jan 2011 20:26:52 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=1511#comment-1253</guid>
		<description>[...] 03:26 PM       Read this - it helps to understand what SSL (https) does and what it doesn&#039;t do...  Case for Email Security - Why Use Encryption? &#124; LuxSci FYI  I don&#039;t use Luxsci, so this is not some add for them, I just found the article useful.  Right now [...]</description>
		<content:encoded><![CDATA[<p>[...] 03:26 PM       Read this &#8211; it helps to understand what SSL (https) does and what it doesn&#039;t do&#8230;  Case for Email Security &#8211; Why Use Encryption? | LuxSci FYI  I don&#039;t use Luxsci, so this is not some add for them, I just found the article useful.  Right now [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Linn</title>
		<link>http://luxsci.com/blog/the-case-for-email-security.html/comment-page-1#comment-921</link>
		<dc:creator>Michael Linn</dc:creator>
		<pubDate>Sat, 21 Aug 2010 06:29:40 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=1511#comment-921</guid>
		<description>This was a thorough primer on e-mail security.  Thanks for sharing</description>
		<content:encoded><![CDATA[<p>This was a thorough primer on e-mail security.  Thanks for sharing</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SecureForm Now Support SMTP TLS for Secure Form Email Delivery &#124; LuxSci FYI</title>
		<link>http://luxsci.com/blog/the-case-for-email-security.html/comment-page-1#comment-700</link>
		<dc:creator>SecureForm Now Support SMTP TLS for Secure Form Email Delivery &#124; LuxSci FYI</dc:creator>
		<pubDate>Sat, 03 Apr 2010 01:16:25 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=1511#comment-700</guid>
		<description>[...] in SecureForm refers in part to the fact that the emailed form data can be secured using PGP or S/MIME.  This, combined with enforced use of SSL, ensures that the form data is secured from end-to-end [...]</description>
		<content:encoded><![CDATA[<p>[...] in SecureForm refers in part to the fact that the emailed form data can be secured using PGP or S/MIME.  This, combined with enforced use of SSL, ensures that the form data is secured from end-to-end [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JumbleMe Support</title>
		<link>http://luxsci.com/blog/the-case-for-email-security.html/comment-page-1#comment-698</link>
		<dc:creator>JumbleMe Support</dc:creator>
		<pubDate>Thu, 01 Apr 2010 17:42:28 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=1511#comment-698</guid>
		<description>JumbleMe&#039;s security is very robust, while allowing convenience for our users.  All emails are actually secured with two passwords.  One password is given to the recipient, the other stored on JumbleMe&#039;s servers and is unique to each email.  Both must be present to open an email.  
  When a recipient tries to read an email, he/she enters her password on the website or using our software.  They have 4 attempts to enter the correct password, at which point there is a lockout and the Sender is notified of the failed attempts.  After the lockout, they may try again up to a total of 10 times, then the email is completely disabled.  Only with a correct password entry is the second key then used to decode the email.
  By using a 2 password system, a password cracker software would be trying to crack the equivalent of a 20+ character password (exact length reserved for security reasons).  And this password would be unique to each email.  This seemed the best way to allow our members the convenience of one password, but the security of long and unique passwords for each email.</description>
		<content:encoded><![CDATA[<p>JumbleMe&#8217;s security is very robust, while allowing convenience for our users.  All emails are actually secured with two passwords.  One password is given to the recipient, the other stored on JumbleMe&#8217;s servers and is unique to each email.  Both must be present to open an email.<br />
  When a recipient tries to read an email, he/she enters her password on the website or using our software.  They have 4 attempts to enter the correct password, at which point there is a lockout and the Sender is notified of the failed attempts.  After the lockout, they may try again up to a total of 10 times, then the email is completely disabled.  Only with a correct password entry is the second key then used to decode the email.<br />
  By using a 2 password system, a password cracker software would be trying to crack the equivalent of a 20+ character password (exact length reserved for security reasons).  And this password would be unique to each email.  This seemed the best way to allow our members the convenience of one password, but the security of long and unique passwords for each email.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Unsatisfied wJumbleme</title>
		<link>http://luxsci.com/blog/the-case-for-email-security.html/comment-page-1#comment-686</link>
		<dc:creator>Unsatisfied wJumbleme</dc:creator>
		<pubDate>Tue, 09 Mar 2010 04:24:16 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=1511#comment-686</guid>
		<description>Jumbleme may not be as secure as you think.  Let&#039;s suppose you put a strong password on a file and send your email.  You would expect your recipient to need to use that strong password, right?  Well, yes, except if that user has a jumbleme account.  In that case the recipient receives the email with THEIR jumbleme password regardless of what you sent.  Seems like a pretty serious security breach to me.  Many many password crackers exist that can crack 6 or 8 character passwords with relative ease. 

See for yourself:

http://jumbleme.com/board/index.php?action=printpage;topic=5.0
or 
If you are having trouble opening an email, the first question to ask is, are you a member? If so, all emails sent to you should be encrypted with YOUR password.  This was done for convenience, for if you are working at a business using our system, and you have 20 different people sending you encrypted emails, you don&#039;t want to remember 20 different passwords.  Just the one you signed up with.  Keep this in mind if you send yourself a test email.  It won&#039;t matter what password you use in the body of the email, it will always be encrypted with your password.</description>
		<content:encoded><![CDATA[<p>Jumbleme may not be as secure as you think.  Let&#8217;s suppose you put a strong password on a file and send your email.  You would expect your recipient to need to use that strong password, right?  Well, yes, except if that user has a jumbleme account.  In that case the recipient receives the email with THEIR jumbleme password regardless of what you sent.  Seems like a pretty serious security breach to me.  Many many password crackers exist that can crack 6 or 8 character passwords with relative ease. </p>
<p>See for yourself:</p>
<p><a href="http://jumbleme.com/board/index.php?action=printpage;topic=5.0"  rel="nofollow">http://jumbleme.com/board/index.php?action=printpage;topic=5.0</a><br />
or<br />
If you are having trouble opening an email, the first question to ask is, are you a member? If so, all emails sent to you should be encrypted with YOUR password.  This was done for convenience, for if you are working at a business using our system, and you have 20 different people sending you encrypted emails, you don&#8217;t want to remember 20 different passwords.  Just the one you signed up with.  Keep this in mind if you send yourself a test email.  It won&#8217;t matter what password you use in the body of the email, it will always be encrypted with your password.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Kangas</title>
		<link>http://luxsci.com/blog/the-case-for-email-security.html/comment-page-1#comment-683</link>
		<dc:creator>Erik Kangas</dc:creator>
		<pubDate>Wed, 24 Feb 2010 02:38:45 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=1511#comment-683</guid>
		<description>Postini filters inbound email for spam, viruses, and other content -- it is essentially a slightly inferior version of what McAfee offers (formerly MX Logic) -- and what we offer through our Premium Email Filtering service.

JumbleMe is a service somewhat like the &quot;Escrow&quot; feature of LuxSci&#039;s SecureLine end-to-end email encryption service.  it allows you to secure parts of an email message and that does help with some of the problems discussed in this article.</description>
		<content:encoded><![CDATA[<p>Postini filters inbound email for spam, viruses, and other content &#8212; it is essentially a slightly inferior version of what McAfee offers (formerly MX Logic) &#8212; and what we offer through our Premium Email Filtering service.</p>
<p>JumbleMe is a service somewhat like the &#8220;Escrow&#8221; feature of LuxSci&#8217;s SecureLine end-to-end email encryption service.  it allows you to secure parts of an email message and that does help with some of the problems discussed in this article.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack Lampson</title>
		<link>http://luxsci.com/blog/the-case-for-email-security.html/comment-page-1#comment-682</link>
		<dc:creator>Jack Lampson</dc:creator>
		<pubDate>Wed, 24 Feb 2010 02:30:08 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=1511#comment-682</guid>
		<description>how does something like postini or JumbleMe fit into this conversation?</description>
		<content:encoded><![CDATA[<p>how does something like postini or JumbleMe fit into this conversation?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SMTP TLS: All About Secure Email Delivery over TLS &#124; LuxSci FYI</title>
		<link>http://luxsci.com/blog/the-case-for-email-security.html/comment-page-1#comment-667</link>
		<dc:creator>SMTP TLS: All About Secure Email Delivery over TLS &#124; LuxSci FYI</dc:creator>
		<pubDate>Sat, 20 Feb 2010 02:13:33 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=1511#comment-667</guid>
		<description>[...] conversation cannot be eavesdropped upon (without Computer A [...]</description>
		<content:encoded><![CDATA[<p>[...] conversation cannot be eavesdropped upon (without Computer A [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Can You Make Your Email More Secure? &#124; LuxSci FYI</title>
		<link>http://luxsci.com/blog/the-case-for-email-security.html/comment-page-1#comment-593</link>
		<dc:creator>Can You Make Your Email More Secure? &#124; LuxSci FYI</dc:creator>
		<pubDate>Sun, 10 Jan 2010 15:41:24 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=1511#comment-593</guid>
		<description>[...] only to a point. While you can ensure that your users connect securely to LuxSci&#8217;s servers, who is to say that your recipient’s connection is secure? With LuxSci SecureLine, even if the recipient’s connection isn&#8217;t secure, you can be [...]</description>
		<content:encoded><![CDATA[<p>[...] only to a point. While you can ensure that your users connect securely to LuxSci&#8217;s servers, who is to say that your recipient’s connection is secure? With LuxSci SecureLine, even if the recipient’s connection isn&#8217;t secure, you can be [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

