You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
f565f276e2
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> |
5 years ago | |
|---|---|---|
| .. | ||
| ca-certificates | 5 years ago | |
| fstools | 5 years ago | |
| fwtool | 5 years ago | |
| iucode-tool | 6 years ago | |
| mtd | 5 years ago | |
| openwrt-keyring | 5 years ago | |
| opkg | 5 years ago | |
| procd | 5 years ago | |
| rpcd | 5 years ago | |
| ubox | 5 years ago | |
| ubus | 5 years ago | |
| ucert | 5 years ago | |
| uci | 5 years ago | |
| urandom-seed | 5 years ago | |
| urngd | 5 years ago | |
| usign | 5 years ago | |
| zram-swap | 5 years ago | |