Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Risk

8/1/2013
11:09 AM
Connect Directly
Google+
LinkedIn
Twitter
RSS
E-Mail
50%
50%

Facebook Enables Secure Browsing For All Users

Facebook converts all users to HTTPS for security, says the new encryption doesn't slow down connections.

10 Facebook Features To Help You Get Ahead
10 Facebook Features To Help You Get Ahead
(click image for larger view)
Facebook has converted all users to the Hypertext Transfer Protocol Secure (HTTPS) browsing form, the social network announced.

"HTTPS protects everyone, especially when you're using Wi-Fi access points," said Chester Wisniewski, senior security adviser at Sophos. "Before, it was really easy to have your Facebook account hijacked just by logging on a Wi-Fi network. Having HTTPS enabled also protects you when you're browsing from a mobile device, which people do daily."

This means that your browser now communicates with Facebook using a secure connection. You'll notice this in the address bar where there is a lock icon and "https" rather than "http" in the Web address.

Facebook first introduced the HTTPS browsing option two years ago. Facebook recommended that users who frequently accessed the social network from public Internet access points such as coffee shops, airports and schools enable this option, though it was voluntary. In November, the social network announced it would start rolling out HTTPS for all users in North America, followed by everywhere else.

[ Do you know what to look for? Read more: How To Spot A Facebook Scam. ]

According to Scott Renfro, a software engineer at Facebook, more than a third of users enabled the feature following its introduction. HTTPS uses Transport Layer Security, formerly known as Secure Sockets Layer, and makes the communication between your browser and Facebook servers more secure, he said.

"Now that HTTPS is on by default, virtually all traffic from www.facebook.com and 80% of traffic to m.facebook.com uses a secure connection," Renfro said. "Our native apps for Android and iOS have long used HTTPS a well."

One priority for Facebook in converting all users to HTTPS was increasing the site's speed, Renfro said. Encrypted pages tend to take longer to load, which slows down performance. Facebook was able to avoid extra latency in most cases by upgrading its infrastructure and using abbreviated "handshakes," he said. "In addition to the network round trips necessary for your browser to talk to Facebook servers, HTTPS adds additional round trips for the handshake to set up the connection. A full handshake requires two additional round trips, while an abbreviated handshake requires just one additional round trip. An abbreviated handshake can only follow a successful full handshake," he said.

"For example," he continued, "if you're in Vancouver, where a round trip to Facebook's Prineville, Oregon, data center takes 20ms, then the full handshake only adds about 40ms, which probably isn't noticeable. However, if you're in Jakarta, where a round trip takes 300ms, a full handshake can add 600ms. When combined with an already slow connection, this additional latency on every request could be very noticeable and frustrating."

Other changes Facebook made include: a secure attribute for authentication cookies, which instructs the browser to only send these cookies on HTTPS requests; an insecure indicator cookie, which directs to HTTPS when no authentication cookies are present; and upgrading all apps to support HTTPS browsing.

"Turning on HTTPS by default is a dream come true, and something Facebook's traffic, network, security infrastructure, and security teams have worked on for years," Renfro said. "We're really happy with how much of Facebook's traffic is now encrypted, and we are even more excited about the future changes we're preparing to launch."

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
COVID-19: Latest Security News & Commentary
Dark Reading Staff 5/27/2020
How an Industry Consortium Can Reinvent Security Solution Testing
Henry Harrison, Co-founder & Chief Technology Officer, Garrison,  5/21/2020
10 iOS Security Tips to Lock Down Your iPhone
Kelly Sheridan, Staff Editor, Dark Reading,  5/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
How Cybersecurity Incident Response Programs Work (and Why Some Don't)
This Tech Digest takes a look at the vital role cybersecurity incident response (IR) plays in managing cyber-risk within organizations. Download the Tech Digest today to find out how well-planned IR programs can detect intrusions, contain breaches, and help an organization restore normal operations.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-13386
PUBLISHED: 2020-05-27
In SmartDraw 2020 27.0.0.0, the installer gives inherited write permissions to the Authenticated Users group on the SmartDraw 2020 installation folder. Additionally, when the product is installed, two scheduled tasks are created on the machine, SDMsgUpdate (Local) and SDMsgUpdate (TE). The scheduled...
CVE-2019-20806
PUBLISHED: 2020-05-27
An issue was discovered in the Linux kernel before 5.2. There is a NULL pointer dereference in tw5864_handle_frame() in drivers/media/pci/tw5864/tw5864-video.c, which may cause denial of service, aka CID-2e7682ebfc75.
CVE-2020-10737
PUBLISHED: 2020-05-27
A race condition was found in the mkhomedir tool shipped with the oddjob package in versions before 0.34.5 and 0.34.6 wherein, during the home creation, mkhomedir copies the /etc/skel directory into the newly created home and changes its ownership to the home's user without properly checking the hom...
CVE-2020-13622
PUBLISHED: 2020-05-27
JerryScript 2.2.0 allows attackers to cause a denial of service (assertion failure) because a property key query for a Proxy object returns unintended data.
CVE-2020-13623
PUBLISHED: 2020-05-27
JerryScript 2.2.0 allows attackers to cause a denial of service (stack consumption) via a proxy operation.