Risk
1/27/2011
11:29 AM
Connect Directly
RSS
E-Mail
50%
50%

Facebook Boosts Security With SSL Encryption

Technology upgrade blocks Firesheep and eavesdropping attacks, but, for now, users must opt in.

How Firesheep Can Hijack Web Sessions
(click image for larger view)
Slideshow: How Firesheep Can Hijack Web Sessions

On Wednesday, Facebook announced that it's adding HTTPS, which uses SSL/TLS encryption, to secure all communications between browsers and Facebook Web servers. The move means that Facebook users will now see a lock icon or a green SSL address bar when using the Facebook site.

Previously, Facebook used HTTPS only on pages that required users to enter a password. Now, extending HTTPS to all pages means better security because tools such as Firesheep -- an automated browser extension able to hijack sessions with Web 2.0 sites -- as well as packet sniffers will no longer work against the site.

There's only one catch: HTTPS won't be enabled by default. According to Facebook security engineer Alex Rice, "we hope to offer HTTPS as a default whenever you are using Facebook sometime in the future."

In the interim, the feature will shortly -- over the next few weeks -- become available to all users. To activate it, they'll have to manually select it on the "advanced security features" page, which is located under the "account security" section of the "account settings" page.

Rice warned that users may see some issues, at least in the short term. "Encrypted pages take longer to load, so you may notice that Facebook is slower using HTTPS. In addition, some Facebook features, including many third-party applications, are not currently supported in HTTPS. We'll be working hard to resolve these remaining issues."

But based on other Web sites' experiences, any slowdowns should be minor, as long as Facebook correctly implements the protocol. For example, in July 2010, Google software engineer Matt Cutts posted an assessment of Google's experience. In brief: "If you stop reading now you only need to remember one thing: SSL/TLS is not computationally expensive anymore."

Google made HTTPS non-optional for all Gmail users in January 2010 as a way to boost security after finding that the protocol required no additional hardware and consumed very few resources. "On our production frontend machines, SSL/TLS accounts for less than 1% of the CPU load, less than 10 KB of memory per connection, and less than 2% of network overhead," said Cutts.

Facebook faced criticism for not following Google's lead more quickly, especially after the arrival last year of Firesheep. Its author, Eric Butler, said he built the tool to highlight the inherent vulnerability of using Facebook on an unencrypted Wi-Fi network.

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Flash Poll
Current Issue
Cartoon
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2013-7392
Published: 2014-07-22
Gitlist allows remote attackers to execute arbitrary commands via shell metacharacters in a file name to Source/.

CVE-2014-2385
Published: 2014-07-22
Multiple cross-site scripting (XSS) vulnerabilities in the web UI in Sophos Anti-Virus for Linux before 9.6.1 allow local users to inject arbitrary web script or HTML via the (1) newListList:ExcludeFileOnExpression, (2) newListList:ExcludeFilesystems, or (3) newListList:ExcludeMountPaths parameter t...

CVE-2014-4326
Published: 2014-07-22
Elasticsearch Logstash 1.0.14 through 1.4.x before 1.4.2 allows remote attackers to execute arbitrary commands via a crafted event in (1) zabbix.rb or (2) nagios_nsca.rb in outputs/.

CVE-2014-4511
Published: 2014-07-22
Gitlist before 0.5.0 allows remote attackers to execute arbitrary commands via shell metacharacters in the file name in the URI of a request for a (1) blame, (2) file, or (3) stats page, as demonstrated by requests to blame/master/, master/, and stats/master/.

CVE-2014-4911
Published: 2014-07-22
The ssl_decrypt_buf function in library/ssl_tls.c in PolarSSL before 1.2.11 and 1.3.x before 1.3.8 allows remote attackers to cause a denial of service (crash) via vectors related to the GCM ciphersuites, as demonstrated using the Codenomicon Defensics toolkit.

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Where do information security startups come from? More important, how can I tell a good one from a flash in the pan? Learn how to separate ITSec wheat from chaff in this episode.