koutheir/binary-security-check

Moved: https://codeberg.org/koutheir/binary-security-check

binary-security-check's Issues

Automatically detect proper libC

Feature-request, not a bug.

Compiling from 27beefd, it seems like the application is failing to automatically process pretty much any ELF I supply it with.

$ bsc /bin/bash
15:00:17 [ERROR] /bin/bash: Dependent C runtime library is not recognized.

$ bsc -l /lib/x86_64-linux-gnu/libc.so.6 /bin/bash
/bin/bash: +ASLR +STACK-PROT +READ-ONLY-RELOC !IMMEDIATE-BIND ~FORTIFY-SOURCE(+memmove,+strcpy,+strncpy,+sprintf,+fprintf,+asprintf,+snprintf,+memcpy,+vfprintf,+fdelt,+printf,+longjmp,+vsnprintf,!fgets,!mbstowcs,!readlink,!memmove,!strcpy,!wcsrtombs,!wcrtomb,!strcat,!mbsnrtowcs,!mbsrtowcs,!memcpy,!getgroups,!confstr,!wctomb,!strncpy,!memset,!getcwd,!read,!stpcpy,!gethostname)

System:

# Debian 11

$ uname -vr
5.14.0-0.bpo.2-amd64 #1 SMP Debian 5.14.9-2~bpo11+1 (2021-10-10)

$ rustc -V
rustc 1.56.1 (59eed8a2a 2021-11-01)

binary-security-check command line invalid arguments

I am trying to run the binary after installing it on my system(Linux Ubuntu), but I get an invalid arguments error. How to use this binary correctly? Can you help me for this?

My usage:
(In my home directory):
cd .cargo/bin
./binary-security-check -l MYFILE

Please add git tags for versions.

I like something like git tag v1.2.3

Generating a report

I would like to receive a report in the form of a table with a list of binary files and results. Or the translation in a beautiful form into a text file

Timestamp is always in UTC/GMT

Please disregard the "library not recognized", there is #4 for it.

$ bsc /bin/bash
14:58:12 [ERROR] /bin/bash: Dependent C runtime library is not recognized.

$ date
Sat 13 Nov 2021 01:28:34 ACDT

[QUESTION] Can this Analyze Static Binaries?

I have statically compiled binaries, that have no dynamically linked libc.

I get:

$ file "/home/runner/hugo/hugo"
/home/runner/hugo/hugo: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), static-pie linked, stripped

$ ldd "/home/runner/hugo/hugo"
        statically linked

$ binary-security-check "/home/runner/hugo/hugo"
07:49:57 [ERROR] /home/runner/hugo/hugo: dependent C runtime library is not recognized.

I have been using OfriOuzan/HardeningMeter which works even for static binaries.
Could a similar feature-set be implemented in binary-security-check as well?

Can you provide installation documents and use documents？

Can you provide installation documents and use documents