staging/neocturne/config/Config-build.in, branch main

apk: limit CONFIG_IPK_FILES_CHECKSUMS config to OPKG

2024-06-20T03:52:06Z

Limit CONFIG_IPK_FILES_CHECKSUMS config to OPKG as APK have different way to validate package integrity (apk audit) Signed-off-by: Christian Marangi

Revert "apk: limit CONFIG_IPK_FILES_CHECKSUMS config to OPKG"

2024-06-20T03:52:05Z

This reverts commit 25bbefcdd9424ed1b6ef35a39e84420fc4cce322. Only the Config-build.in change needed to be merged and this contains leftover from previous revision of the feature. Signed-off-by: Christian Marangi

config: imply apk-mbedtls with USE_APK

2024-06-11T21:58:19Z

On top of the fixup to select apk-mbedtls when USE_APK is enabled from a new config, also imply the package when enabling the config to catch .config that are already init. (Having both opkg and apk installed in a system is not a problem but if USE_APK is used, APK presence in the system is mandatory) Link: https://github.com/openwrt/openwrt/pull/15543 Signed-off-by: Christian Marangi

apk: limit CONFIG_IPK_FILES_CHECKSUMS config to OPKG

2024-06-11T21:58:19Z

Limit CONFIG_IPK_FILES_CHECKSUMS config to OPKG as APK have different way to validate package integrity (apk audit) Link: https://github.com/openwrt/openwrt/pull/15543 Signed-off-by: Christian Marangi

build: add APK package build capabilities

2024-05-17T20:21:26Z

A new option called `USE_APK` is added which generated APK packages (.apk) instead of OPKG packages (.ipk). Some features like fstools `snapshot` command are not yet ported Signed-off-by: Paul Spooren

config: build: dont allow STRIP_KERNEL_EXPORTS on kernel 6.6

2024-05-16T13:12:53Z

STRIP_KERNEL_EXPORTS is currently not working on kernel 6.6 as there have been major changes in the upstream kernel. I have looked at it, and I dont think we can adapt the current patch to work so until this is fixed lets prevent STRIP_KERNEL_EXPORTS from being selected on 6.6. Link: https://github.com/openwrt/openwrt/pull/15498 Signed-off-by: Robert Marko

build: add option for building with stack-protector-all

2024-01-19T20:27:14Z

The GCC option -fstack-protector-all is a security feature used to protect against stack-smashing attacks. This option enhances the stack-smashing protection provided by -fstack-protector-strong. -fstack-protector-all option applies stack protection to all functions, regardless of their characteristics. While this offers the most comprehensive protection against stack-smashing attacks, it can significantly impact the performance of the program because every function call includes additional checks for stack integrity. This option can incur a performance penalty because of the extra checks added to every function call, but it significantly enhances security, making it harder for attackers to exploit buffer overflows to execute arbitrary code. It's particularly useful in scenarios where security is paramount and performance trade-offs are acceptable. Signed-off-by: Cedric DOURLENT

build: add CycloneDX SBOM JSON support

2023-11-01T11:14:41Z

CycloneDX is an open source standard developed by the OWASP foundation. It supports a wide range of development ecosystems, a comprehensive set of use cases, and focuses on automation, ease of adoption, and progressive enhancement of SBOMs (Software Bill Of Materials) throughout build pipelines. So lets add support for CycloneDX SBOM for packages and images manifests. Signed-off-by: Petr Štetiar

config: add a knob to use the mold linker for packages

2023-07-04T18:25:40Z

Building it requires gcc >= 10.2 or clang >= 12. Using sstrip with its -z argument can produce non-working binaries, like a segfaulting `getrandom`, so don't allow that combination. Signed-off-by: Andre Heider

build: replace SSTRIP_ARGS with SSTRIP_DISCARD_TRAILING_ZEROES

2023-07-04T18:25:40Z

sstrip only has one functional arg. Make that a bool option, which can easily depend on other knobs then. This is required to be disabled for the mold linker. Signed-off-by: Andre Heider