aboutsummaryrefslogtreecommitdiffstats
path: root/include/kernel-version.mk
diff options
context:
space:
mode:
authorJo-Philipp Wich <jo@mein.io>2019-08-06 21:22:27 +0200
committerJo-Philipp Wich <jo@mein.io>2019-08-07 07:53:48 +0200
commit872cbcc6280738fa9b5a7f9f7d49576405d2f18e (patch)
tree4b9cb2ec721e9afec365306c165b650381f75145 /include/kernel-version.mk
parentff550dae32ea431de9d74c11f77f28c62c935204 (diff)
downloadupstream-872cbcc6280738fa9b5a7f9f7d49576405d2f18e.tar.gz
upstream-872cbcc6280738fa9b5a7f9f7d49576405d2f18e.tar.bz2
upstream-872cbcc6280738fa9b5a7f9f7d49576405d2f18e.zip
config: introduce separate CONFIG_SIGNATURE_CHECK option
Introduce a new option CONFIG_SIGNATURE_CHECK which defaults to the value of CONFIG_SIGNED_PACKAGES and thus is enabled by default. This option is needed to support building target opkg with enabled signature verification while having the signed package lists disabled. Our buildbots currently disable package signing globally in the buildroot and SDK to avoid the need to ship private signing keys to the build workers and to prevent the triggering of random key generation on the worker nodes since package signing happens off-line on the master nodes. As unintended side-effect, updated opkg packages will get built with disabled signature verification, hence the need for a new override option. Signed-off-by: Jo-Philipp Wich <jo@mein.io> (cherry picked from commit f565f276e2c06ac8f3176e0b16d6f2d40cd653d4)
Diffstat (limited to 'include/kernel-version.mk')
0 files changed, 0 insertions, 0 deletions