Quote:
Originally Posted by =X=
It depends on where the vulnerability lies. If it is in the open source code. The branch is updated so new versions get the fix. Then use up to the hardware vendor to push the fix out.
If the vulnerability lies in Google's proprietary code then updates are pushed out.
Hardware vendors that use pure Android tend to get the updates faster since it's closest to the base line. While vendors like Nook and now Amazon take longer since they have to roll the changed to their branch.
|
Are these older branches getting updated much when issues are found though? I mean love or hate Microsoft they have continued to patch XP well beyond its used by date becuase it really affects people. Some security researchers I've listened too weren't favourable towards Andriod with regards to security as a whole (I personally haven't looked into it enough) so I was interested how these things are being handled because this will have implications for Amazon on a older codebase.
Quote:
Originally Posted by =X=
Yes, 3.0 had a lot of changes to support frames, better multitasking and more. Obviously 2.2 will not have these API so already Amazon is coming out with an obsoleted OS.
|
Thought that might be the case. Will be interesting to see the implications for Amazon moving forward.