|
|
12
|
|
Can you explain what that "backport source code" is? I can see the tag released e.g. in frameworks/base for 7.1.2. It looks like it's finally the source code for all the security patches listed by the Android security bulletins, but never reapplied to previous versions of the AOSP. Is that right?
Thanks, Jean-Marie.
Le lundi 9 septembre 2019 20:25:37 UTC+2, Bill Yi a écrit : Android security backport source code is now available. The following builds and tags are supported:
5725749, android-7.1.1_r60 5725750, android-7.1.2_r38 5729099, android-8.0.0_r38 5725752, android-8.1.0_r68 5748468, android-9.0.0_r48
bill
--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to [hidden email]
To unsubscribe from this group, send email to
[hidden email]
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/46d3dc7f-f740-47e6-ad92-b079cad16e3c%40googlegroups.com.
|
|
|
Could you explain why the PLATFORM_SECURITY_PATCH of android-8.1.0_r70 is still 2017-12-05? That's very confusing!
lh@server2:~/cwhuang/oreo/build/make$ git diff android-8.1.0_r65 android-8.1.0_r70 core/version_defaults.mk diff --git a/core/version_defaults.mk b/core/version_defaults.mk index 5f45946..5758d22 100644 --- a/core/version_defaults.mk +++ b/core/version_defaults.mk @@ -181,7 +181,7 @@ ifndef PLATFORM_SECURITY_PATCH # It must be of the form "YYYY-MM-DD" on production devices. # It must match one of the Android Security Patch Level strings of the Public Security Bulletins. # If there is no $PLATFORM_SECURITY_PATCH set, keep it empty. - PLATFORM_SECURITY_PATCH := 2019-06-05 + PLATFORM_SECURITY_PATCH := 2017-12-05 endif ifndef PLATFORM_BASE_OS Bill Yi於 2019年11月5日星期二 UTC+8上午1時34分28秒寫道： Android security backport source code is now available. The following builds and tags are supported:
5887206, android-8.0.0_r40 5887208, android-8.1.0_r70 5887210, android-9.0.0_r50
bill
--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to [hidden email]
To unsubscribe from this group, send email to
[hidden email]
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/a1cd8431-339b-4a4e-855c-db553bb22e49%40googlegroups.com.
|
|
|
The security backports are not device specific. Hence we are not updating the security string on those branches.
bill On Monday, November 11, 2019 at 9:59:25 AM UTC-8, Chih-Wei Huang wrote: Could you explain why the PLATFORM_SECURITY_PATCH of android-8.1.0_r70 is still 2017-12-05? That's very confusing!
lh@server2:~/cwhuang/oreo/build/make$ git diff android-8.1.0_r65 android-8.1.0_r70 core/<a href="http://version_defaults.mk" target="_blank" rel="nofollow" onmousedown="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fversion_defaults.mk\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH7rbQMZF814crgew696B5EDpR-ZQ';return true;" onclick="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fversion_defaults.mk\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH7rbQMZF814crgew696B5EDpR-ZQ';return true;">version_defaults.mk diff --git a/core/<a href="http://version_defaults.mk" target="_blank" rel="nofollow" onmousedown="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fversion_defaults.mk\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH7rbQMZF814crgew696B5EDpR-ZQ';return true;" onclick="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fversion_defaults.mk\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH7rbQMZF814crgew696B5EDpR-ZQ';return true;">version_defaults.mk b/core/<a href="http://version_defaults.mk" target="_blank" rel="nofollow" onmousedown="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fversion_defaults.mk\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH7rbQMZF814crgew696B5EDpR-ZQ';return true;" onclick="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fversion_defaults.mk\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH7rbQMZF814crgew696B5EDpR-ZQ';return true;">version_defaults.mk index 5f45946..5758d22 100644 --- a/core/<a href="http://version_defaults.mk" target="_blank" rel="nofollow" onmousedown="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fversion_defaults.mk\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH7rbQMZF814crgew696B5EDpR-ZQ';return true;" onclick="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fversion_defaults.mk\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH7rbQMZF814crgew696B5EDpR-ZQ';return true;">version_defaults.mk +++ b/core/<a href="http://version_defaults.mk" target="_blank" rel="nofollow" onmousedown="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fversion_defaults.mk\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH7rbQMZF814crgew696B5EDpR-ZQ';return true;" onclick="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fversion_defaults.mk\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNH7rbQMZF814crgew696B5EDpR-ZQ';return true;">version_defaults.mk @@ -181,7 +181,7 @@ ifndef PLATFORM_SECURITY_PATCH # It must be of the form "YYYY-MM-DD" on production devices. # It must match one of the Android Security Patch Level strings of the Public Security Bulletins. # If there is no $PLATFORM_SECURITY_PATCH set, keep it empty. - PLATFORM_SECURITY_PATCH := 2019-06-05 + PLATFORM_SECURITY_PATCH := 2017-12-05 endif ifndef PLATFORM_BASE_OS Bill Yi於 2019年11月5日星期二 UTC+8上午1時34分28秒寫道： Android security backport source code is now available. The following builds and tags are supported:
5887206, android-8.0.0_r40 5887208, android-8.1.0_r70 5887210, android-9.0.0_r50
bill
--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to [hidden email]
To unsubscribe from this group, send email to
[hidden email]
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/c0ea71cc-e601-4b1e-9820-e9d47194c879%40googlegroups.com.
|
|
|
maybe I am missing something.
even if a tag is not device-specific, doesn't it make sense to update
the SPL?
e.g. if android-8.1.0_r70 has all the security patches applied from the
November 2019 (and earlier) security bulletin, why not update the
variable PLATFORM_SECURITY_PATCH?
Leaving it set to 2017-12-05 seems unnecessarily confusing.
-James M
On 2019-11-13 6:19 p.m., 'Bill Yi' via Android Building wrote:
> The security backports are not device specific. Hence we are not
> updating the security string on those branches.
>
> bill
>
> On Monday, November 11, 2019 at 9:59:25 AM UTC-8, Chih-Wei Huang wrote:
>
> Could you explain why the PLATFORM_SECURITY_PATCH of
> android-8.1.0_r70 is still 2017-12-05?
> That's very confusing!
>
> lh@server2:~/cwhuang/oreo/build/make$ git diff android-8.1.0_r65
> android-8.1.0_r70 core/version_defaults.mk < http://version_defaults.mk>
> diff --git a/core/version_defaults.mk < http://version_defaults.mk>
> b/core/version_defaults.mk < http://version_defaults.mk>
> index 5f45946..5758d22 100644
> --- a/core/version_defaults.mk < http://version_defaults.mk>
> +++ b/core/version_defaults.mk < http://version_defaults.mk>
> @@ -181,7 +181,7 @@ ifndef PLATFORM_SECURITY_PATCH
> # It must be of the form "YYYY-MM-DD" on production devices.
> # It must match one of the Android Security Patch Level
> strings of the Public Security Bulletins.
> # If there is no $PLATFORM_SECURITY_PATCH set, keep it empty.
> - PLATFORM_SECURITY_PATCH := 2019-06-05
> + PLATFORM_SECURITY_PATCH := 2017-12-05
> endif
>
> ifndef PLATFORM_BASE_OS
>
>
> Bill Yi於 2019年11月5日星期二 UTC+8上午1時34分28秒寫道：
>
> Android security backport source code is now available. The
> following builds and tags are supported:
>
> 5887206, android-8.0.0_r40
> 5887208, android-8.1.0_r70
> 5887210, android-9.0.0_r50
>
> bill
>
> --
> --
> You received this message because you are subscribed to the "Android
> Building" mailing list.
> To post to this group, send email to [hidden email]
> To unsubscribe from this group, send email to
> [hidden email]
> For more options, visit this group at
> http://groups.google.com/group/android-building?hl=en>
> ---
> You received this message because you are subscribed to the Google
> Groups "Android Building" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to [hidden email]
> <mailto: [hidden email]>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/android-building/c0ea71cc-e601-4b1e-9820-e9d47194c879%40googlegroups.com
> < https://groups.google.com/d/msgid/android-building/c0ea71cc-e601-4b1e-9820-e9d47194c879%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to [hidden email]
To unsubscribe from this group, send email to
[hidden email]
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/f1f769bd-ebf9-0fb9-956a-fc5b7def9827%40gmail.com.
|
|
|
James Muir於 2019年11月14日星期四 UTC+8下午4時56分59秒寫道： maybe I am missing something.
even if a tag is not device-specific, doesn't it make sense to update
the SPL?
e.g. if android-8.1.0_r70 has all the security patches applied from the
November 2019 (and earlier) security bulletin, why not update the
variable PLATFORM_SECURITY_PATCH?
Leaving it set to 2017-12-05 seems unnecessarily confusing.
Yes. Totally agree.
If I update to android-8.1.0_r70, the users would think this is a VERY OLD release which is not updated for almost two years!
Even android-8.1.0_r65 has update to 2019-06-05, why android-8.1.0_r70 became even older?
Please manage the thing right, Google!
--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to [hidden email]
To unsubscribe from this group, send email to
[hidden email]
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/043868b6-de10-49f5-aaf7-3b8ccfa00edd%40googlegroups.com.
|
|
|
James Muir於 2019年11月18日星期一 UTC+8下午4時04分45秒寫道： > Please manage the thing right, Google!
I'm not sure if comments like that are helpful.
Maybe there is a valid reason not to touch the SPL when google has not
published a device release from a given tag, or maybe it is just a
process issue (e.g. may be the release manager is in charge of changing
the SPL).
What's the valid reason to keep it to a very old date? That's inconceivable.
--
--
You received this message because you are subscribed to the "Android Building" mailing list.
To post to this group, send email to [hidden email]
To unsubscribe from this group, send email to
[hidden email]
For more options, visit this group at
http://groups.google.com/group/android-building?hl=en
---
You received this message because you are subscribed to the Google Groups "Android Building" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/android-building/2854a15b-ef9d-4f20-971e-414a9123fc4f%40googlegroups.com.
|
12
|
Locked
