Does anyone recognize why hardening-check reports that the binary isn't using the Fortify Source hardening on my local build? The build logs have -D_FORTIFY_SOURCE=2 used extensively.
Thanks
/usr/lib/x86_64-linux-gnu/boltd:
Position Independent Executable: yes
Stack protected: yes
Fortify Source functions: no, only unprotected functions found!
Read-only relocations: yes
Immediate binding: yes
/usr/bin/boltctl:
Position Independent Executable: yes
Stack protected: yes
Fortify Source functions: unknown, no protectable libc functions used
Read-only relocations: yes
Immediate binding: yes
Does anyone recognize why hardening-check reports that the binary isn't using the Fortify Source hardening on my local build? The build logs have -D_FORTIFY_SOURCE=2 used extensively.
Thanks
/usr/lib/ x86_64- linux-gnu/ boltd:
Position Independent Executable: yes
Stack protected: yes
Fortify Source functions: no, only unprotected functions found!
Read-only relocations: yes
Immediate binding: yes
/usr/bin/boltctl:
Position Independent Executable: yes
Stack protected: yes
Fortify Source functions: unknown, no protectable libc functions used
Read-only relocations: yes
Immediate binding: yes