Broken CFI Checks
The new --extended CFI checks appear broken:
https://github.com/slimm609/checksec.sh/blob/fd840bcf3aeeb105dd83374ed80fce226ba0bc4b/checksec#L547-L556
- I think you will need
readelf -Wsto capture long mangled C++ symbol function names - The method of checking the first (?) entry of the array to see if theres a non .cfi function is likely full of false positives.
https://github.com/dobin/clang-cfi-safestack-analysis
This is the repo I have used for reference testing, if you have source of false positives that I can use to test/troubleshoot, it would help in resolving the issue.
It seems that the grep pattern is broken? Was it intended to be \.cfi? I run into the following FP:
readelf -s /tmp/sample_go_binary | grep .cfi
1143: 0000000000456640 261 FUNC GLOBAL DEFAULT 1 runtime.funcfile
which results in CFI shown to be present