Google Chrome Will Soon Warn You of Software That Performs MitM Attacks

brambedkar59

Level 34
Thread author
Verified
Top Poster
Well-known
Forum Veteran
Apr 16, 2017
2,315
1
31,412
3,270
Banana Republic
Google Chrome 63 will include a new security feature that will detect when third-party software is performing a Man-in-the-Middle (MitM) attack that hijacks the user's Internet connection.

A MitM attack is when an application installed on a user's computer or a local network intercepts the user's web traffic.

For the party performing the MitM attack, the hardest part is dealing with encrypted HTTPS traffic. Most MitM toolkits fail to correctly rewrite the user's encrypted connections, causing SSL errors that Chrome will detect.
Read more at source link.
This is a welcome move by Google.
 
I wonder, how it is gonna be implemented. Thus far I do not like the sound of it. It seems very google like, good for google, bad for users.

Browsers already warn about insecure/damaged SSL connections, this sounds like a good excuse to monitor user's traffic.

Qualys SSL Labs - Projects / SSL Client Test
 
I wonder, how it is gonna be implemented. Thus far I do not like the sound of it. It seems very google like, good for google, bad for users.

Browsers already warn about insecure/damaged SSL connections, this sounds like a good excuse to monitor user's traffic.

Qualys SSL Labs - Projects / SSL Client Test
Here is a quote from the article-
The new Chrome 63 feature is in the form of a new warning screen. This new error will appear whenever Chrome detects a large number of SSL connection errors in a short timespan, a sign that someone is trying — and failing — to intercept the user's web traffic.
I don't think it has anything to do with monitoring user traffic, cause they already can and are doing all that.
 
I don't think it has anything to do with monitoring user traffic, cause they already can and are doing all that.
In order to detect errors like that, they have to keep the log of the traffic and visited webpages, which beats the point of using SSL for privacy reasons.

Though if it is gonna be implemented in Chrome only, I could not care less. Not like anyone, who cares about privacy, uses Chrome anyway.
 
nHr5Rg.jpg


HTTPS error not else but project in its beta form.
 
In order to detect errors like that, they have to keep the log of the traffic and visited webpages, which beats the point of using SSL for privacy reasons.

Though if it is gonna be implemented in Chrome only, I could not care less. Not like anyone, who cares about privacy, uses Chrome anyway.

Pretty much this.. I have to use Chrome in some cases, and when I do I use protection.. Command line toggles on the icon;

--disable-background-networking --disable-component-extensions-with-background-pages --dns-prefetch-disable --no-pings --disable-logging