Why does Google Say Mozilla Thunderbird is Less Secure?

Every now and again when you are scanning for a reaction to one thing, you end up finding something else rather bewildering. For instance, Google's declaration that Mozilla Thunderbird is less secure, however, why do they say that? Today's Superuser Q& a post has the reaction to a puzzled peruser's request.

Today's Question & Answer session comes to us graciousness of Superuser—a subdivision of Stack Exchange, a gathering driven social occasion of Q& a si


[post_ad]

The Question :

Superuser peruser Nemo needs to know why Google considers Thunderbird to be less secure:

I have never had issues using Gmail with Thunderbird, yet while endeavoring to use a free programming client for Google Talk/Chat/Hangout I discovered the going hand in hand with unforeseen verbalization. According to Google's record on Less Secure Apps:

A couple of instances of utilizations that don't help the latest security gages join […  ] Desktop mail clients like Microsoft Outlook and Mozilla Thunderbird.

Google then offers a win or forget about it versus non secure record switch ("Allow less secure applications").

Why does Google say Thunderbird does not help the latest security rules? Is Google endeavoring to say that standard traditions like IMAP, SMTP and Pop3 are less secure ways to get to a letter drop? It is sheltered to say that they are endeavoring to say that the activities customers take part in with the item puts their records at threat without a doubt?

Secunia's Vulnerability Report on Mozilla Thunderbird 24.x says:

Unpatched 11 percent (1 of 9 Secunia advisories) […  ] The most great unpatched Secunia consultative impacting Mozilla Thunderbird 24.x, with all vendor patches associated, is assessed exceptionally fundamental (obviously Sa59803).

Why does Google say Mozilla Thunderbird is less

[post_ad]

The Answer :

Superuser supporter Techie007 has the response for us: 

It is because of those clients (at present) don't help Oauth 2.0. As showed by Google:

Beginning in the second half of 2014, we will start constantly growing the security checks performed when customers log into Google. These additional checks will promise that simply the proposed customer has passage to their record, whether through a system, contraption, or application. These movements will impact any application that sends a customer name and/or watchword to Google.

To better secure your customers, we recommend you overhaul most of your applications to Oauth 2.0. In case you pick not to do along  these  lines, your customers will be obliged to make extra strides in order to keep getting to your applications.

In framework, if your application starting now uses plain passwords to confirm to Google, we immovably urge you to minimize customer interference by changing to Oauth 2.0.

Source: New Security Measures Will Affect Older (non-Oauth 2.0) Applications (Google Online Security Blog)

[post_ad]