Fwd: Google Play warning: You are using an unsafe implementation of X509TrustManager

[Marcus Wolschon]

---------- Forwarded message ----------
From: Google Play <googlepla...@google.com>
Date: Thu, Feb 18, 2016 at 8:06 PM
Subject: Google Play warning: You are using an unsafe implementation of X509TrustManager
To: marcus....@googlemail.com

Hello Google Play Developer,

Your app(s) listed at the end of this email use an unsafe implementation of the interface X509TrustManager. Specifically, the implementation ignores all SSL certificate validation errors when establishing an HTTPS connection to a remote host, thereby making your app vulnerable to man-in-the-middle attacks. An attacker could read transmitted data (such as login credentials) and even change the data transmitted on the HTTPS connection. If you have more than 20 affected apps in your account, please check the Developer Console for a full list.

To properly handle SSL certificate validation, change your code in the checkServerTrusted method of your custom X509TrustManager interface to raise either CertificateException or IllegalArgumentException whenever the certificate presented by the server does not meet your expectations. For technical questions, you can post to Stack Overflow and use the tags “android-security” and “TrustManager.”

Please address this issue as soon as possible and increment the version number of the upgraded APK. Beginning May 17, 2016, Google Play will block publishing of any new apps or updates containing the unsafe implementation of the interface X509TrustManager.

To confirm you’ve made the correct changes, submit the updated version of your app to the Developer Console and check back after five hours. If the app hasn’t been correctly upgraded, we will display a warning.

While these specific issues may not affect every app with the TrustManager implementation, it’s best not to ignore SSL certificate validation errors. Apps with vulnerabilities that expose users to risk of compromise may be considered dangerous products in violation of the Content Policy and section 4.4 of the Developer Distribution Agreement.

Apps must also comply with the Developer Distribution Agreement and Content Policy. If you feel we have sent this warning in error, contact our policy support team through the Google Play Developer Help Center.

Regards,

The Google Play Team

©2016 Google Inc. 1600 Amphitheatre Parkway, Mountain View, CA 94043

Email preferences: You have received this mandatory email service announcement to update you about important changes to your Google Play Developer account.

Affected app(s), version(s), and class(es):

de.blau.android
16
org.acra.util.NaiveTrustManager;

[Simon Poole]

I'll upgrade to the current ACRA version asap (which has fixed the issue, real or not in this case). We need to address a non-backwards compatible change in in JOSM presets so I need to produce a new build of  0.9.7 anyway .

Simon

--

---
You received this message because you are subscribed to the Google Groups "osmeditor4android" group.
To unsubscribe from this group and stop receiving emails from it, send an email to osmeditor4andr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Simon Poole]

0.9.7 build with updated ACRA https://drive.google.com/open?id=0B9pKLmh8s1h8TnJCS0FjMnQybWc

See: https://github.com/MarcusWolschon/osmeditor4android/commits/0.9.7-MAINT-branch

[Simon Poole]

Small note: an updated 0.9.8 beta will take a couple of days.