Cisco Learning Network Store Promotions Page
Showing posts with label Secure Sockets Layer (SSL). Show all posts
Showing posts with label Secure Sockets Layer (SSL). Show all posts

10.15.2014

Security alert: Google drops SSL 3.0 after POODLE attack discovery

 
Google's security team has discovered a vulnerability in SSL 3.0 which can be exploited to steal secure cookies and other data. The 15 year old technology is still used as a fallback when connection problems occur as it helps maintain backward compatibility, but the security problems mean that Google will start to phase out support. Details of the exploit have been published and Chrome has today been tweaked to disable SSL 3.0 fallback.
 
Bodo Möller from Google's security team points out that this move will "break some sites" and that they will need to be updated. This does present some compatibility issues, and the advice is to support TLS_FALLBACK_SCSV instead, at least for the time being.
 
Google explains that SSL 3.0 is an insecure, obsolete protocol that has since been superseded. But even when servers support the more secure TLS 1.0, TLS 1.1 or TLS 1.2, the "protocol downgrade dance" that takes place between servers and clients can be exploited using a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack. Clients and servers will automatically attempt to establish a connection using the most secure protocol supported by each, but should a problem arise the next most secure option will be used, and so on.
 
An attacker can force this protocol downgrade to take place by preventing the initial connection from taking place, triggering repeated attempts with increasingly less secure protocols. The encryption used in SSL 3.0 is fairly easily cracked and a relatively simple main-in-the-middle attack can then be used to intercept and decrypt secure cookies.
 
The full effect of the discovery is not yet known, but the fact that such a widely-used -- even if obsolete -- protocol is involved means that large numbers of sites are going to be involved, although it has been suggested that it is older versions of Internet Explorer that are worst affected. Google's security advisory includes advice for system admins looking to ensure the security of their servers.
 
Photo credit: KPG_Payless / Shutterstock
 
~ Mark Wilson

1.08.2014

Yahoo finally enables HTTPS encryption for email by default

Summary: Yahoo webmail users will get a significant security benefit with the company enabling encryption by default. 
 
From today, Yahoo will begin encrypting all email connections by default, offering its users the same additional security that Google rolled out for Gmail in 2010.
 
Meeting the January 8 deadline it announced last October, Yahoo has enabled Secure Sockets Layer (SSL) — denoted by 'HTTPS' in browsers' URL bar — encryption by default for its roughly 200 million Yahoo Mail users.
 
The change means that Yahoo Mail users no longer need to manually configure their accounts to enable SSL encryption for mail, which encrypts communications between the browser and Yahoo's web servers and is meant to ensure to the user the site they're communicating with really is what it claims to be.
 
"Anytime you use Yahoo Mail — whether it's on the web, mobile web, mobile apps, or via IMAP, POP or SMTP — it is 100 percent encrypted by default and protected with 2,048 bit certificates," Jeff Bonforte, Yahoo SVP of communication products, wrote in a company blog post.
 
Yahoo initially outlined plans to enable HTTPS by default, but later confirmed it would implement it with 2048-bit certificates, which is the minimum others, led by Google and Microsoft, have moved towards. So, while HTTPS by default is good news for Yahoo users, it's also come to Yahoo quite late compared to other webmail providers.
 
Google enabled SSL by default for Gmail in 2010, SSL by default in search (for signed-in users) in 2011 and now makes all searches SSL by default. Also, in November it completed its upgrade of all SSL certificates to 2048-bit RSA, with the longer key lengths making it harder to crack SSL connections.
 
Yahoo's plans to encrypt mail by default came after the first leaks from Edward Snowden, revealing the US National Security Agency (NSA) spy programs that targeted major US internet companies.
 
The NSA has also prompted a bigger response from Yahoo, which since pledged to encrypt all data moving from the internet to its servers and all data moving between its datacentres, with the latter being a response to revelations of the NSA's 'Muscular' program, which exploited unencrypted links between datacentres of Yahoo and Google.
 
~ Liam Tung