d4b065e35c
The project has been transferred from Trustwave (SpiderLabs) to OWASP, hence the change in URLs. The upstream CPE vendor ID will likely also change in the future but the upstream is still working on this [1]. - Fixes: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-1019 [1] https://github.com/owasp-modsecurity/ModSecurity/issues/3083 Signed-off-by: Frank Vanbever <frank.vanbever@mind.be> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
25 lines
983 B
Plaintext
25 lines
983 B
Plaintext
config BR2_PACKAGE_LIBMODSECURITY
|
|
bool "libmodsecurity"
|
|
depends on BR2_INSTALL_LIBSTDCPP
|
|
depends on BR2_TOOLCHAIN_HAS_THREADS
|
|
# libmodsecurity embeds several mbedtls source files, causing
|
|
# various issues when static linking and other dependencies of
|
|
# libmodsecurity in turn use mbedtls
|
|
depends on !BR2_STATIC_LIBS
|
|
select BR2_PACKAGE_PCRE2
|
|
help
|
|
Libmodsecurity is one component of the ModSecurity
|
|
v3 project. The library codebase serves as an
|
|
interface to ModSecurity Connectors taking in web
|
|
traffic and applying traditional ModSecurity
|
|
processing. In general, it provides the capability
|
|
to load/interpret rules written in the ModSecurity
|
|
SecRules format and apply them to HTTP content
|
|
provided by your application via Connectors.
|
|
|
|
https://github.com/owasp-modsecurity/ModSecurity
|
|
|
|
comment "libmodsecurity needs a toolchain w/ C++, threads, dynamic library"
|
|
depends on !BR2_INSTALL_LIBSTDCPP || \
|
|
!BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS
|