Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<blockquote> <p>I would like to find some kind of reference that either confirms the ability or states that it can not be done.</p> </blockquote> <p>It is impossible to prove a negative. However:</p> <ul> <li><p>You cannot modify the source code to Maps V1 or Maps V2, because we do not have that source code</p></li> <li><p>There is no API to control anything regarding the networking aspects of Maps V1 or Maps V2, as you can tell by reading the documentation for those APIs</p></li> <li><p>For Maps V2 at least, the actual networking is done by another app (Play Services Framework) in another process, AFAICT, and you have no way of modifying the behavior of that app</p></li> <li><p>If Google is not using HTTPS today for Maps V1/V2 map tiles, it is well within reason that Google never uses HTTPS for Maps V1/V2 map tiles (you could attempt to modify some firewall settings on your local network to see if HTTPS is an option, by blocking the HTTP URLs you find via packet sniffing, to see if Google fails over to using HTTPS URLs)</p></li> </ul> <p>The onus is on the security auditor to demonstrate that what they want is possible. If <em>they</em> do not have some documented and supported means of forcing Maps V1/V2 to use HTTPS, then they are being unethical for suggesting that other apps are insecure due to the behavior of Maps V1/V2. They may as well claim that your app is insecure because it is incapable of raising the dead, or incapable of transmuting lead into gold, or any number of other seemingly impossible tasks.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload