8000 beep: change git repository includes fixes for CVE fixes by BKPepe · Pull Request #18697 · openwrt/packages · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

beep: change git repository includes fixes for CVE fixes #18697

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Conversation

BKPepe
Copy link
Member
@BKPepe BKPepe commented Jun 6, 2022

Maintainer: n/a
Compile tested: OpenWrt 21.02.03, Turris Omnia, mvebu/cortex-a9
Run tested: N/A

Description:

My commit was sitting for some time in my stash and I did not have time to finish it. Let's solve it once for all.

Changed Git repository, which is used for Fedora packaging
johnath/beep#11 (comment)

Fixed CVEs:
CVE-2018-0492 - https://nvd.nist.gov/vuln/detail/CVE-2018-0492
CVE-2018-1000532 - https://nvd.nist.gov/vuln/detail/CVE-2018-1000532

cc: @zpc0 who were findling around this package

@jefferyto
Copy link
Member

CI error:

arm-openwrt-linux-muslgnueabi-gcc -MT beep-log.o -MMD -MP -MF .deps/beep-log.o.dep  -DPACKAGE_TARNAME='"beep"' -DPACKAGE_VERSION='"1.4.12"' -D_GNU_SOURCE  -D_FORTIFY_SOURCE=2 -D_GLIBCXX_ASSERTIONS  -O2 -g -std=gnu99  -pedantic  -Wall -Wextra  -Werror -Wno-padded   -Wno-format-nonliteral -Os -pipe -fno-caller-saves -fno-plt -fhonour-copts -Wno-error=unused-but-set-variable -Wno-error=unused-result -mfloat-abi=hard -ffile-prefix-map=/home/build/openwrt/build_dir/target-arm_cortex-a9+vfpv3-d16_musl_eabi/beep-1.4.12=beep-1.4.12 -Wformat -Werror=format-security -fstack-protector -D_FORTIFY_SOURCE=1 -Wl,-z,now -Wl,-z,relro -o beep-log.o -c beep-log.c
<command-line>: error: "_FORTIFY_SOURCE" redefined [-Werror]
<command-line>: note: this is the location of the previous definition
cc1: all warnings being treated as errors
make[3]: *** [GNUmakefile:277: beep-log.o] Error 1
make[3]: Leaving directory '/home/build/openwrt/build_dir/target-arm_cortex-a9+vfpv3-d16_musl_eabi/beep-1.4.12'
make[2]: *** [Makefile:46: /home/build/openwrt/build_dir/target-arm_cortex-a9+vfpv3-d16_musl_eabi/beep-1.4.12/.built] Error 2
make[2]: Leaving directory '/feed/utils/beep'
time: package/feeds/packages_ci/beep/compile#1.04#0.25#1.29
    ERROR: package/feeds/packages_ci/beep failed to build.
make[1]: Leaving directory '/home/build/openwrt'
make[1]: *** [package/Makefile:116: package/feeds/packages_ci/beep/compile] Error 1
make: *** [/home/build/openwrt/include/toplevel.mk:223: package/beep/compile] Error 2

May need to patch out -Werror (or remove one of the -D_FORTIFY_SOURCE definitions).

@BKPepe
Copy link
Member Author
BKPepe commented Jun 7, 2022

Yes, it seems like it. I wonder why I didn't experience it on OpenWrt 21.02.x series, but during the night, I prepared env for master builds and I will fix this ASAP.

@jefferyto
Copy link
Member

Perhaps your build environment has CONFIG_PKG_FORTIFY_SOURCE_NONE selected?

@BKPepe
Copy link
Member Author
BKPepe commented Jun 7, 2022
# CONFIG_PKG_FORTIFY_SOURCE_NONE is not set
# CONFIG_PKG_FORTIFY_SOURCE_1 is not set
CONFIG_PKG_FORTIFY_SOURCE_2=y

@jefferyto
Copy link
Member

There was no error for you because upstream also has -D_FORTIFY_SOURCE=2, so it was set twice on the command line with the same value.

Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
@BKPepe BKPepe closed this Jun 7, 2022
@BKPepe BKPepe deleted the beep branch June 7, 2022 19:27
@BKPepe
Copy link
Member Author
BKPepe commented Jun 7, 2022

My bad. I could not force push the current branch as it was created in this repository and not in my forked repository. :-(

@BKPepe
Copy link
Member Author
BKPepe commented Oct 11, 2022 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0