mirror of
https://github.com/lineageos4microg/docker-lineage-cicd
synced 2024-11-09 10:09:56 +01:00
Revert "Update documentation to reflect status of signature spoofing in LOS 21"
This reverts commit 451b0a11eb0410fb90f4e54061a561ecf2b341f6.
This commit is contained in:
parent
451b0a11eb
commit
d9f25d3b55
@ -94,14 +94,6 @@ ENV ZIP_SUBDIR true
|
|||||||
ENV LOGS_SUBDIR true
|
ENV LOGS_SUBDIR true
|
||||||
|
|
||||||
# Apply the MicroG's signature spoofing patch
|
# Apply the MicroG's signature spoofing patch
|
||||||
# Since LineageOS 21, signature spoofing for microG is built into LineageOS
|
|
||||||
# itself and no patches are required if you're building an userdebug or eng
|
|
||||||
# variant. In this case, this value can be left set to "no".
|
|
||||||
# You may set the value to "restricted" if you wish to build an user variant
|
|
||||||
# with signature spoofing enabled; otherwise, it will be disabled in user
|
|
||||||
# builds.
|
|
||||||
#
|
|
||||||
# For LineageOS 20 and older:
|
|
||||||
# Valid values are "no", "yes" (for the original MicroG's patch) and
|
# Valid values are "no", "yes" (for the original MicroG's patch) and
|
||||||
# "restricted" (to grant the permission only to the system privileged apps).
|
# "restricted" (to grant the permission only to the system privileged apps).
|
||||||
#
|
#
|
||||||
|
18
README.md
18
README.md
@ -108,8 +108,7 @@ Include the repo with another manifest file like this:
|
|||||||
And when starting the build, set the `CUSTOM_PACKAGES` variable to a list of app names
|
And when starting the build, set the `CUSTOM_PACKAGES` variable to a list of app names
|
||||||
(defined by `LOCAL_MODULE` in `Android.mk`) separated by spaces.
|
(defined by `LOCAL_MODULE` in `Android.mk`) separated by spaces.
|
||||||
|
|
||||||
|
#### Signature spoofing
|
||||||
#### Signature spoofing (up until LineageOS 20)
|
|
||||||
|
|
||||||
There are two options for the [signature spoofing patch][signature-spoofing]
|
There are two options for the [signature spoofing patch][signature-spoofing]
|
||||||
required for [microG][microg]:
|
required for [microG][microg]:
|
||||||
@ -135,21 +134,6 @@ FAKE_SIGNATURE permission must be included in the build as system apps
|
|||||||
(e.g. as part of GMS or `CUSTOM_PACKAGES`)
|
(e.g. as part of GMS or `CUSTOM_PACKAGES`)
|
||||||
|
|
||||||
|
|
||||||
#### Signature spoofing (starting from LineageOS 21)
|
|
||||||
|
|
||||||
LineageOS 21 introduced built-in signature spoofing specifically for microG.
|
|
||||||
The "Original" and restricted patches applied to previous versions of LineageOS
|
|
||||||
have been dropped in favor of the built-in functionality.
|
|
||||||
|
|
||||||
This means that signature spoofing will work for microG even if the environment
|
|
||||||
variable `SIGNATURE_SPOOFING` is set to `no`.
|
|
||||||
|
|
||||||
It should be noted that by default, signature spoofing is only enabled on
|
|
||||||
"debuggable" builds (`eng` and `userdebug` build variants). It is possible to
|
|
||||||
enable signature spoofing on the `user` build variant as well by setting the
|
|
||||||
`SIGNATURE_SPOOFING` variable to `restricted`.
|
|
||||||
|
|
||||||
|
|
||||||
#### Proprietary files
|
#### Proprietary files
|
||||||
|
|
||||||
Some proprietary files are needed to create a LineageOS build, but they're not
|
Some proprietary files are needed to create a LineageOS build, but they're not
|
||||||
|
Loading…
Reference in New Issue
Block a user