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
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading Tech Digest, Dec. 19, 2014
Software-defined networking can be a net plus for security. The key: Work with the network team to implement gradually, test as you go, and take the opportunity to overhaul your security strategy.
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2004-2771
Published: 2014-12-24
The expand function in fio.c in Heirloom mailx 12.5 and earlier and BSD mailx 8.1.2 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in an email address.

CVE-2014-3569
Published: 2014-12-24
The ssl23_get_client_hello function in s23_srvr.c in OpenSSL 1.0.1j does not properly handle attempts to use unsupported protocols, which allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via an unexpected handshake, as demonstrated by an SSLv3 handshak...

CVE-2014-4322
Published: 2014-12-24
drivers/misc/qseecom.c in the QSEECOM driver for the Linux kernel 3.x, as used in Qualcomm Innovation Center (QuIC) Android contributions for MSM devices and other products, does not validate certain offset, length, and base values within an ioctl call, which allows attackers to gain privileges or c...

CVE-2014-6132
Published: 2014-12-24
Cross-site scripting (XSS) vulnerability in the Web UI in IBM WebSphere Service Registry and Repository (WSRR) 6.3 through 6.3.0.5, 7.0.x through 7.0.0.5, 7.5.x through 7.5.0.4, 8.0.x before 8.0.0.3, and 8.5.x before 8.5.0.1 allows remote authenticated users to inject arbitrary web script or HTML vi...

CVE-2014-6153
Published: 2014-12-24
The Web UI in IBM WebSphere Service Registry and Repository (WSRR) 6.3.x through 6.3.0.5, 7.0.x through 7.0.0.5, 7.5.x through 7.5.0.4, 8.0.x before 8.0.0.3, and 8.5.x before 8.5.0.1 does not set the secure flag for a cookie in an https session, which makes it easier for remote attackers to capture ...

Best of the Web
Dark Reading Radio
Archived Dark Reading Radio
Join us Wednesday, Dec. 17 at 1 p.m. Eastern Time to hear what employers are really looking for in a chief information security officer -- it may not be what you think.