Google Online Security Blog

Google’s Public DNS intercepted in Turkey

29 de marzo de 2014

Posted by Steven Carstensen, Software Engineer
YouTube

If you could tell a user three things to do to stay safe online, what would they be?

26 de marzo de 2014

Posted by Rob Reeder, User Experience Research TeamSafety Centergoo.gl/F4fJ59

Staying at the forefront of email security and reliability: HTTPS-only and 99.978 percent availability

20 de marzo de 2014

Posted by Nicolas Lidzborski, Gmail Security Engineering Lead
Cross-posted on the Official Google Blog and Gmail Bloghas supported HTTPSHTTPS the defaultApps Status Dashboardcreating strong passwordsenabling 2-step verificationhttps://www.google.com/help/security

CAPTCHAs that capture your heart

14 de febrero de 2014

Posted by Vinay Shet, Product Manager, reCAPTCHAreCAPTCHA

Screen shot of CAPTCHAs reading Valentine, love, chocolate, and flowers

Some examples of Valentine's Day CAPTCHAs

we announced

Security Reward Programs Update

4 de febrero de 2014

Posted by Eduardo Vela Nava and Michal Zalewski, Google Security Teamsecurity researchsecurity bugspatchesvulnerability reward programby Googlesecurity guidelinesHangoutsGMail$500$10,000goo.gl/vulnzPatch Reward Program

$10,000 for complicated, high-impact improvements that almost certainly prevent major vulnerabilities in the affected code.

$5,000 for moderately complex patches that provide convincing security benefits.

Between $500 and $1,337 for submissions that are very simple or that offer only fairly speculative gains.

Keeping YouTube Views Authentic

4 de febrero de 2014

Posted by Philipp Pfeiffenberger, Software Engineerworking with third party view service providersincreasing YouTube views

FFmpeg and a thousand fixes

10 de enero de 2014

Posted by Mateusz Jurczyk and Gynvael Coldwind, Information Security EngineersVulnerabilities - Application SecurityFFmpegsamples.mplayerhq.hu$ git log | grep Jurczyk | grep -c Coldwind1120c77be3a35a0160d6af88056b0899f120f2eef38e

NULL pointer dereferences,

Invalid pointer arithmetic leading to SIGSEGV due to unmapped memory access,

Out-of-bounds reads and writes to stack, heap and static-based arrays,

Invalid free() calls,

Double free() calls over the same pointer,

Division errors,

Assertion failures,

Use of uninitialized memory.

"Found by Mateusz "j00ru" Jurczyk and Gynvael Coldwind"herehere

Further improving digital certificate security

7 de diciembre de 2013

Posted by Adam Langley, Security Engineerintermediate certificate authorityCertificate Transparency[Update December 12: We have decided that the ANSSI certificate authority will be limited to the following top-level domains in a future version of Chrome: .fr .gp (Guadeloupe) .gf (Guyane) .mq (Martinique) .re (Réunion) .yt (Mayotte) .pm (Saint-Pierre et Miquelon) .bl (Saint Barthélemy) .mf (Saint Martin) .wf (Wallis et Futuna) .pf (Polynésie française) .nc (Nouvelle Calédonie) .tf (Terres australes et antarctiques françaises)]

Internet-wide efforts to fight email phishing are working

6 de diciembre de 2013

Posted by Elie Bursztein, anti-abuse research lead and Vijay Eranti, Gmail anti-abuse technical lead
Editor's Note: This post was updated on February 9th, 2016. Adoption numbers reflect state of authentication as of this date.

86.8% of the emails we received are signed according to the (DKIM) standard (up from 76.9% in 2013). Over two million domains (weekly active) have adopted this standard (up from 0.5 millions 2013).

95.3% of incoming emails we receive come from SMTP servers that are authenticated using the SPF standard (up from 89.1% in 2013). Over 7.8 million domains (weekly active) have adopted the SPF standard (up from 3.5 million domains in 2013).

85% of incoming emails we receive are protected by both the DKIM and SPF standards (up from 74.7% in 2013).

Over 162,000 domains have deployed domain-wide policies that allow us to reject hundreds of millions of unauthenticated emails every week via the DMARC standard (up from 80,000 in 2013).

Join the fight against email spam DKIMSPFDMARC

Even more patch rewards!

18 de noviembre de 2013

Posted by Michal Zalewski, Google Security TeamAbout a month ago, we kicked off our Patch Reward Program. The goal is very simple: to recognize and reward proactive security improvements to third-party open-source projects that are vital to the health of the entire Internet.We started with a fairly conservative scope, but said we would expand the program soon. Today, we are adding the following to the list of projects that are eligible for rewards:

All the open-source components of Android: Android Open Source Project

Widely used web servers: Apache httpd, lighttpd, nginx

Popular mail delivery services: Sendmail, Postfix, Exim, Dovecot

Virtual private networking: OpenVPN

Network time: University of Delaware NTPD

Additional core libraries: Mozilla NSS, libxml2

Toolchain security improvements for GCC, binutils, and llvm

For more information about eligibility, reward amounts, and the submission process, please visit this page. Happy patching!

Security Blog