Skip to content

Are build hardening flags intentionally not passed to src/gen_context.c? #1069

@sorenstoutner

Description

@sorenstoutner

Debian utilized a build hardening flag checker, which analyzes the build logs to make sure the appropriate hardening flags are passed to each command. It flags the following two entries.

CFLAGS missing (-fPIE): gcc -Wdate-time -D_FORTIFY_SOURCE=2 -I. -g -O2 -Werror=implicit-function-declaration -ffile-prefix-map=/build/reproducible-path/litecoin-0.21.4=. -fstack-protector-strong -fstack-clash-protection -Wformat -Werror=format-security -fcf-protection -Wall -Wextra -Wno-unused-function -c src/gen_context.c -o gen_context.o LDFLAGS missing (-fPIE -pie -Wl,-z,relro -Wl,-z,now): gcc gen_context.o -o gen_context 

Is it intentional that the CFLAGS and LDFLAGS are not passed to this file, or is it an oversight?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions