search

slimm609 / checksec

Checksec
https://slimm609.github.io/checksec
Other
2.04k stars 306 forks source link

checksec FORTIFY detection (proccheck) again #244

Closed teoberi closed 6 months ago

teoberi commented 6 months ago

Added detailed results for Fortify: 'N/A', 'Partial' in src/functions/proccheck.sh Add cases for 'N/A' and 'Partial' in tests/hardening-checks.sh ('# process checks' section) Update build_binaries.sh ('# Fortify source' section) Change test files for Fortify Fix for #241

teoberi commented 6 months ago

./build_binaries.sh: line 54: nasm: command not found

NASM can be added or I can add the object files (.o), i.e. nolibc.o and nolibc32.o generated with the commands:

nasm -f elf64 -o nolibc.o nolibc.asm
nasm -f elf32 -o nolibc32.o nolibc32.asm

I would still prefer the addition of NASM instead of the .o binary files that contain the machine code.

teoberi commented 6 months ago

If the addition of missing object files is accepted, does it go through a Draft pull requests? If NASM is installed, the files are regenerated and therefore the added ones are overwritten.

slimm609 commented 6 months ago

If the addition of missing object files is accepted, does it go through a Draft pull requests? If NASM is installed, the files are regenerated and therefore the added ones are overwritten.

If the addition of missing object files is accepted, does it go through a Draft pull requests? If NASM is installed, the files are regenerated and therefore the added ones are overwritten.

The Dockerfiles are not generated, its only the checksec script itself that is generated. The formatting/linters apply to all files though

teoberi commented 6 months ago

So can NASM be installed or do I add the object files generated by me with NASM?

slimm609 commented 6 months ago

yes, please add it to the test dockerfiles