<?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: 256-bit AES Encryption for SSL and TLS: Maximal Security</title>
	<atom:link href="http://luxsci.com/blog/256-bit-aes-encryption-for-ssl-and-tls-maximal-security.html/feed" rel="self" type="application/rss+xml" />
	<link>http://luxsci.com/blog/256-bit-aes-encryption-for-ssl-and-tls-maximal-security.html</link>
	<description>News, solutions and insider insight from LuxSci: provider of Secure Email and Web Security</description>
	<lastBuildDate>Thu, 06 Oct 2011 17:44:26 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=402</generator>
	<item>
		<title>By: How to surf safe in today&#8217;s digital world? &#171; Ovidiu Bernaschi&#039;s Blog</title>
		<link>http://luxsci.com/blog/256-bit-aes-encryption-for-ssl-and-tls-maximal-security.html/comment-page-1#comment-1301</link>
		<dc:creator>How to surf safe in today&#8217;s digital world? &#171; Ovidiu Bernaschi&#039;s Blog</dc:creator>
		<pubDate>Mon, 11 Jul 2011 15:45:58 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=623#comment-1301</guid>
		<description>[...] first I really think you should read this article if you&#8217;ve got a basic understanding of Internet encryption. Towards the end of the page, [...]</description>
		<content:encoded><![CDATA[<p>[...] first I really think you should read this article if you&#8217;ve got a basic understanding of Internet encryption. Towards the end of the page, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nord</title>
		<link>http://luxsci.com/blog/256-bit-aes-encryption-for-ssl-and-tls-maximal-security.html/comment-page-1#comment-654</link>
		<dc:creator>Nord</dc:creator>
		<pubDate>Tue, 09 Feb 2010 20:04:23 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=623#comment-654</guid>
		<description>Although AES won the world-wide competition for a new security standard to replace DES (and 3DES), it is not the only good encryption standard. 

Two other competitors receive uniformly good marks: Blowfish (128) and TwoFish (its successor).</description>
		<content:encoded><![CDATA[<p>Although AES won the world-wide competition for a new security standard to replace DES (and 3DES), it is not the only good encryption standard. </p>
<p>Two other competitors receive uniformly good marks: Blowfish (128) and TwoFish (its successor).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Secure Web Pages and Secure Web Forms: Steps to Security &#124; LuxSci FYI</title>
		<link>http://luxsci.com/blog/256-bit-aes-encryption-for-ssl-and-tls-maximal-security.html/comment-page-1#comment-588</link>
		<dc:creator>Secure Web Pages and Secure Web Forms: Steps to Security &#124; LuxSci FYI</dc:creator>
		<pubDate>Sun, 10 Jan 2010 03:03:06 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=623#comment-588</guid>
		<description>[...] You can modify your web server configuration so that only levels of encryption that you approve can be used to access your site.  For more information, see 256-bit AES Encryption for SSL and TLS: Maximal Security. [...]</description>
		<content:encoded><![CDATA[<p>[...] You can modify your web server configuration so that only levels of encryption that you approve can be used to access your site.  For more information, see 256-bit AES Encryption for SSL and TLS: Maximal Security. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Kangas</title>
		<link>http://luxsci.com/blog/256-bit-aes-encryption-for-ssl-and-tls-maximal-security.html/comment-page-1#comment-549</link>
		<dc:creator>Erik Kangas</dc:creator>
		<pubDate>Fri, 04 Dec 2009 04:22:41 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=623#comment-549</guid>
		<description>Note that while they support it, they will choose 128-bit over 256 bit when both are available on the server side.  So, if you are connecting to a site that is not 256-bit only, these systems will use only 128-bit AES.  Microsoft judges that the speed up using 128-bit is more important than the security of using 256-bit.</description>
		<content:encoded><![CDATA[<p>Note that while they support it, they will choose 128-bit over 256 bit when both are available on the server side.  So, if you are connecting to a site that is not 256-bit only, these systems will use only 128-bit AES.  Microsoft judges that the speed up using 128-bit is more important than the security of using 256-bit.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Derek</title>
		<link>http://luxsci.com/blog/256-bit-aes-encryption-for-ssl-and-tls-maximal-security.html/comment-page-1#comment-547</link>
		<dc:creator>Derek</dc:creator>
		<pubDate>Wed, 02 Dec 2009 17:18:03 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=623#comment-547</guid>
		<description>According to TechNet IE on Vista/Windows 7 supports AES-256.

http://technet.microsoft.com/en-us/library/cc766285(WS.10).aspx

TLS_RSA_WITH_AES_128_CBC_SHA
TLS_RSA_WITH_AES_256_CBC_SHA
TLS_DHE_DSS_WITH_AES_128_CBC_SHA
TLS_DHE_DSS_WITH_AES_256_CBC_SHA</description>
		<content:encoded><![CDATA[<p>According to TechNet IE on Vista/Windows 7 supports AES-256.</p>
<p><a href="http://technet.microsoft.com/en-us/library/cc766285(WS.10).aspx"  rel="nofollow">http://technet.microsoft.com/en-us/library/cc766285(WS.10).aspx</a></p>
<p>TLS_RSA_WITH_AES_128_CBC_SHA<br />
TLS_RSA_WITH_AES_256_CBC_SHA<br />
TLS_DHE_DSS_WITH_AES_128_CBC_SHA<br />
TLS_DHE_DSS_WITH_AES_256_CBC_SHA</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Kangas</title>
		<link>http://luxsci.com/blog/256-bit-aes-encryption-for-ssl-and-tls-maximal-security.html/comment-page-1#comment-489</link>
		<dc:creator>Erik Kangas</dc:creator>
		<pubDate>Mon, 31 Aug 2009 01:06:53 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=623#comment-489</guid>
		<description>Looks like Yahoo! Mail doesn&#039;t support AES 256 encryption -- so by restricting your browser to using it you have loced yourself out of Yahoo! Mail.  Your choice is to either give up on the higher strength security so you can use Yahoo! Mail, or move to another email provider (like LuxSci) that does.</description>
		<content:encoded><![CDATA[<p>Looks like Yahoo! Mail doesn&#8217;t support AES 256 encryption &#8212; so by restricting your browser to using it you have loced yourself out of Yahoo! Mail.  Your choice is to either give up on the higher strength security so you can use Yahoo! Mail, or move to another email provider (like LuxSci) that does.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin Frederick</title>
		<link>http://luxsci.com/blog/256-bit-aes-encryption-for-ssl-and-tls-maximal-security.html/comment-page-1#comment-488</link>
		<dc:creator>Kevin Frederick</dc:creator>
		<pubDate>Mon, 31 Aug 2009 00:56:23 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=623#comment-488</guid>
		<description>I have done the Mozilla AES-256 encryption method (editing the about:config) and now I cannot login Yahoo! Mail, this has never happened before and it had worked fine before I changed my config. I believe that Yahoo! Mail is safe enough to log on, yet I cannot do so.
Here is the message I am receiving:


Secure Connection Failed

An error occurred during a connection to login.yahoo.com.

Cannot communicate securely with peer: no common encryption algorithm(s).

(Error code: ssl_error_no_cypher_overlap)

    *   The page you are trying to view can not be shown because the authenticity of the received data could not be verified.

    *   Please contact the web site owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site.


Any ideas?</description>
		<content:encoded><![CDATA[<p>I have done the Mozilla AES-256 encryption method (editing the about:config) and now I cannot login Yahoo! Mail, this has never happened before and it had worked fine before I changed my config. I believe that Yahoo! Mail is safe enough to log on, yet I cannot do so.<br />
Here is the message I am receiving:</p>
<p>Secure Connection Failed</p>
<p>An error occurred during a connection to login.yahoo.com.</p>
<p>Cannot communicate securely with peer: no common encryption algorithm(s).</p>
<p>(Error code: ssl_error_no_cypher_overlap)</p>
<p>    *   The page you are trying to view can not be shown because the authenticity of the received data could not be verified.</p>
<p>    *   Please contact the web site owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site.</p>
<p>Any ideas?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Erik Kangas</title>
		<link>http://luxsci.com/blog/256-bit-aes-encryption-for-ssl-and-tls-maximal-security.html/comment-page-1#comment-472</link>
		<dc:creator>Erik Kangas</dc:creator>
		<pubDate>Sat, 15 Aug 2009 01:38:46 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=623#comment-472</guid>
		<description>Hello,

There is nothing wrong or out of date here.  The thing is that Vista supports AES256 and AES128, but given the choice of the two will pick AES128 for speed over security.  XP doesn&#039;t support AES at all by default.

In your web server, you specified only 2 possible ciphers -- and the only AES one you allow is AES256.  Thus, given the choice between AES256 and RC4, Vista will happily choose AES256.  XP will choose RC4 as it does not support AES.  This is what you see.  However, if you included AES128 in your list of allowed ciphers, then Vista would use that instead of AES256.</description>
		<content:encoded><![CDATA[<p>Hello,</p>
<p>There is nothing wrong or out of date here.  The thing is that Vista supports AES256 and AES128, but given the choice of the two will pick AES128 for speed over security.  XP doesn&#8217;t support AES at all by default.</p>
<p>In your web server, you specified only 2 possible ciphers &#8212; and the only AES one you allow is AES256.  Thus, given the choice between AES256 and RC4, Vista will happily choose AES256.  XP will choose RC4 as it does not support AES.  This is what you see.  However, if you included AES128 in your list of allowed ciphers, then Vista would use that instead of AES256.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Serge Fonville</title>
		<link>http://luxsci.com/blog/256-bit-aes-encryption-for-ssl-and-tls-maximal-security.html/comment-page-1#comment-468</link>
		<dc:creator>Serge Fonville</dc:creator>
		<pubDate>Thu, 13 Aug 2009 15:09:40 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=623#comment-468</guid>
		<description>I&#039;m not sure how up to date this is, but:
I am running apache 2.2 on Vista Home Premium x64 and have set SSLCipherSuite AES256-SHA:RC4-MD5 and when I connect to my website from the same system, the ssl access log shows AES256-SHA, when I connecto from XP Home x32 to the site the log says RC4-MD5. Perhaps this is specific to Vista x64...
My Vista and XP both have the most recent updates</description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure how up to date this is, but:<br />
I am running apache 2.2 on Vista Home Premium x64 and have set SSLCipherSuite AES256-SHA:RC4-MD5 and when I connect to my website from the same system, the ssl access log shows AES256-SHA, when I connecto from XP Home x32 to the site the log says RC4-MD5. Perhaps this is specific to Vista x64&#8230;<br />
My Vista and XP both have the most recent updates</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: How Does Secure Socket Layer (SSL) Work? &#124; LuxSci FYI &#124; LuxSci FYI</title>
		<link>http://luxsci.com/blog/256-bit-aes-encryption-for-ssl-and-tls-maximal-security.html/comment-page-1#comment-317</link>
		<dc:creator>How Does Secure Socket Layer (SSL) Work? &#124; LuxSci FYI &#124; LuxSci FYI</dc:creator>
		<pubDate>Thu, 12 Mar 2009 12:46:37 +0000</pubDate>
		<guid isPermaLink="false">http://luxsci.com/blog/?p=623#comment-317</guid>
		<description>[...] Ciphers: SSL uses one of a large variety of possible &#8220;ciphers&#8221; to perform the symmetric encryption.  Use of a poor/weak cipher can result in fast SSL that is easily compromised.  Currently, it is recommended that one use 128-bit or stronger AES encryption as your cipher.  See: 256-bit AES Encryption for SSL and TLS: Maximal Security. [...]</description>
		<content:encoded><![CDATA[<p>[...] Ciphers: SSL uses one of a large variety of possible &#8220;ciphers&#8221; to perform the symmetric encryption.  Use of a poor/weak cipher can result in fast SSL that is easily compromised.  Currently, it is recommended that one use 128-bit or stronger AES encryption as your cipher.  See: 256-bit AES Encryption for SSL and TLS: Maximal Security. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

