push apps failing in Android until you disable IPv6

[Jeroen Massar]

On 2016-05-09 19:28, Lorenzo Colitti wrote:
> On Mon, May 9, 2016 at 6:17 PM, Tore Anderson <tore at fud.no
> <mailto:tore at fud.no>> wrote:
> 
>     Even a ULA PIO could be problematic if Android's source
>     address selection algorithm isn't updated to RFC6724 defaults. RFC3484
>     predates ULAs, so it treats them the same as other globally scoped
>     addresses.
> 
> 
> Android's source address selection was updated to RFC 6724 in early 2013
> [commit
> <https://android.googlesource.com/platform/bionic/+/378b0e1ea298ab4b8653e4b95e24d0cc0029414c>].
> I think that went into 4.3.

And how many devices will thus actually receive such an update? 3%?

Oh, not too much off:

http://www.statista.com/statistics/271774/share-of-android-platforms-on-mobile-devices-with-android-os/

4.3 has 2.9% of the market, same amount as people still running 2.3.x...
but fortunately apparently some people have been replacing devices with
4.4, at 32%, not as bad as for actual security issues that are still
available on all those platforms though. And that is all assuming it
really landed in 4.3 and not in a 5.x branch....

Now to hope that one day DHCPv6 gets added.... and then the long long
tail of having all those ancient versions going extinct.

Would be so amazing if Google forced vendors to actually support their
devices for a long time and otherwise not allow those devices to use
Google services, would be a great first step... though more important
for security than for IPv6...

Greets,
 Jeroen