Deprecated: Creation of dynamic property Jupiterx_Conditions_Check::$singulars is deprecated in /var/www/html/insights/wp-content/plugins/jupiterx-core/includes/condition/classes/conditions.php on line 18

Deprecated: Creation of dynamic property Jupiterx_Conditions_Check::$archives is deprecated in /var/www/html/insights/wp-content/plugins/jupiterx-core/includes/condition/classes/conditions.php on line 19

Deprecated: Creation of dynamic property Jupiterx_Conditions_Check::$woocommerce is deprecated in /var/www/html/insights/wp-content/plugins/jupiterx-core/includes/condition/classes/conditions.php on line 20

Deprecated: Creation of dynamic property Jupiterx_Conditions_Check::$users is deprecated in /var/www/html/insights/wp-content/plugins/jupiterx-core/includes/condition/classes/conditions.php on line 21

Deprecated: Creation of dynamic property JupiterX_Core\Condition\Apply_Condition::$checker is deprecated in /var/www/html/insights/wp-content/plugins/jupiterx-core/includes/condition/classes/apply-condition.php on line 57

Deprecated: Creation of dynamic property JupiterX_Core\Condition\Apply_Condition::$meta_name is deprecated in /var/www/html/insights/wp-content/plugins/jupiterx-core/includes/condition/classes/apply-condition.php on line 58

Deprecated: Creation of dynamic property JupiterX_Core\Condition\Apply_Condition::$posts_option is deprecated in /var/www/html/insights/wp-content/plugins/jupiterx-core/includes/condition/classes/apply-condition.php on line 59

Deprecated: Creation of dynamic property JupiterX_Core\Condition\Apply_Condition::$id is deprecated in /var/www/html/insights/wp-content/plugins/jupiterx-core/includes/condition/classes/apply-condition.php on line 60

Deprecated: Creation of dynamic property JupiterX_Core\Condition\Apply_Condition::$required_widget is deprecated in /var/www/html/insights/wp-content/plugins/jupiterx-core/includes/condition/classes/apply-condition.php on line 61

Deprecated: Creation of dynamic property JupiterX_Core\Condition\Apply_Condition::$posts is deprecated in /var/www/html/insights/wp-content/plugins/jupiterx-core/includes/condition/classes/apply-condition.php on line 72

Deprecated: Creation of dynamic property JupiterX_Core\Condition\Apply_Condition::$query is deprecated in /var/www/html/insights/wp-content/plugins/jupiterx-core/includes/condition/classes/apply-condition.php on line 124
Google Modifying URLs in Gmail Raises Security Concerns - TUX Insights Skip to content

Google modifying links in Gmail raising security concerns

Despite Google’s recent update to Gmail’s logo so that all google services look unified and follow the same design scheme, now google is making modifications to URLs when received by IMAP users and other external clients.

The addition of new features or design changes doesn’t cause many problems when it happens on social media or entertainment sites. But email’s are the supreme form of communication where serious links would be sent.

This tweak by Google makes it impossible for IMAP users to see the original email without logging into the web interface, due to the fact that it breaks verification of the cryptographic signatures.

Google is the largest e-mail provider in the world, offering both consumer-targeted Gmail product and G Suite for business customers. For some users, it is such that Google is actually modifying URLs instead of using their own link-checking and redirect service. This requires the body of the email to be edited before it reaches the user. External email clients that fetch email over IMAP are affected, with no way to access the original raw email they were sent.

Initially, it was thought that the editing was happening within the Gmail app or through their web client. However, Google confirmed that this is a new feature and is being rolled out to G Suite customers. In addition to that, you can disable this if you want to. Google calls this “Click-time link protection in third-party email clients” which you can read more about here.

The intention of this feature is to prevent phishing attacks with Google’s redirect service including a link checker to warn users who are traveling to potentially dangerous sites. However this explanation is not satisfactory for the average person, forcing users to head to a Google server to view the original URL they were sent is to many an egregious breach of privacy, and a security concern to boot. Moreover, the Company hasn’t shown any warnings or notified its users prior to implementing this feature.

Share your thoughts!
Join our community and share your thoughts about this article with thousands of people like you. You can ask questions, give answers, and do more. Don't miss out on all perks you will have as a community member, join now.
Join the TUX Community!
Join our tech community and meet people like you. Post and discuss about computers, smartphones or any other gadgets. Feel free to sign up now, it only takes a few seconds!
Cookie Notice
By using our site you agree to our use of cookies to deliver a better site experience.