<?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: New Facebook Feature Shows Actual Respect for Your Privacy &#124; WIRED</title>
	<atom:link href="http://www.epanorama.net/blog/2015/06/02/new-facebook-feature-shows-actual-respect-for-your-privacy-wired/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.epanorama.net/blog/2015/06/02/new-facebook-feature-shows-actual-respect-for-your-privacy-wired/</link>
	<description>All about electronics and circuit design</description>
	<lastBuildDate>Sun, 05 Apr 2026 18:35:45 +0000</lastBuildDate>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.9.14</generator>
	<item>
		<title>By: Tomi Engdahl</title>
		<link>https://www.epanorama.net/blog/2015/06/02/new-facebook-feature-shows-actual-respect-for-your-privacy-wired/comment-page-1/#comment-1400613</link>
		<dc:creator><![CDATA[Tomi Engdahl]]></dc:creator>
		<pubDate>Wed, 03 Jun 2015 05:53:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.epanorama.net/newepa/?p=32334#comment-1400613</guid>
		<description><![CDATA[Adam Gross / Facebook Developers:
Facebook to remove support for SHA-1 certificate signatures Oct. 1, will require SHA-2

Moving to a More Secure Standard: Please Update your Apps To Support Certificates Signed with SHA-2
https://developers.facebook.com/blog/post/2015/06/02/SHA-2-Updates-Needed/

As part of our commitments to helping developers build secure apps and protecting the people who use Facebook, we’re updating our encryption requirements for Facebook-connected apps to reflect a new and more secure industry standard. As a result, apps that don&#039;t support SHA-2 certificate signatures will no longer be able to connect to Facebook starting on October 1, 2015

These changes are part of a broader shift in how browsers and web sites encrypt traffic to protect the contents of online communications. Typically, web browsers use a hash function to create a unique fingerprint for a chunk of data or a message. 

For the past two decades, the SHA-1 standard has been the preferred choice across the Internet for calculating message fingerprints. But after identifying security weaknesses in SHA-1, the Certificate Authority and Browser Forum recently published new Baseline Requirements for SSL recommending that all certificate authorities transition away from SHA-1 based signatures, with a full sunset date of January 1, 2016.

We&#039;ll be updating our servers to stop accepting SHA-1 based connections before this final date, on October 1, 2015. After that date, we&#039;ll require apps and sites that connect to Facebook to support the more secure SHA-2 connections.]]></description>
		<content:encoded><![CDATA[<p>Adam Gross / Facebook Developers:<br />
Facebook to remove support for SHA-1 certificate signatures Oct. 1, will require SHA-2</p>
<p>Moving to a More Secure Standard: Please Update your Apps To Support Certificates Signed with SHA-2<br />
<a href="https://developers.facebook.com/blog/post/2015/06/02/SHA-2-Updates-Needed/" rel="nofollow">https://developers.facebook.com/blog/post/2015/06/02/SHA-2-Updates-Needed/</a></p>
<p>As part of our commitments to helping developers build secure apps and protecting the people who use Facebook, we’re updating our encryption requirements for Facebook-connected apps to reflect a new and more secure industry standard. As a result, apps that don&#8217;t support SHA-2 certificate signatures will no longer be able to connect to Facebook starting on October 1, 2015</p>
<p>These changes are part of a broader shift in how browsers and web sites encrypt traffic to protect the contents of online communications. Typically, web browsers use a hash function to create a unique fingerprint for a chunk of data or a message. </p>
<p>For the past two decades, the SHA-1 standard has been the preferred choice across the Internet for calculating message fingerprints. But after identifying security weaknesses in SHA-1, the Certificate Authority and Browser Forum recently published new Baseline Requirements for SSL recommending that all certificate authorities transition away from SHA-1 based signatures, with a full sunset date of January 1, 2016.</p>
<p>We&#8217;ll be updating our servers to stop accepting SHA-1 based connections before this final date, on October 1, 2015. After that date, we&#8217;ll require apps and sites that connect to Facebook to support the more secure SHA-2 connections.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
