The Project "ESSTRA", a software suite for Enhancing Software Supply Chain Transparency, aims to improve transparency of software supply chains as the name suggests.
More specifically, the goal of this project is to provide a set of tools to help illuminate and unveil the "dark" areas in software supply chains where critical information about software components is unclear, primarily from software traceability and compliance perspective.
The current version of ESSTRA takes an approach of embedding metadata in resulting binary files at compile time with GCC. The metadata contains information about the source and header files from which the binary file is generated.
ESSTRA is being developed on Ubuntu 22.04 with GCC 11.4.0 and Python 3.10.12 installed on an x86_64 PC. And we have also confirmed that ESSTRA can build and run on an Aarch64 (arm64) Docker container virtualized with QEMU on an x86_64 PC.
This is a preliminary version. The data format and content of metadata, and the specifications and functionality of the tools are tentative and subject to change.
The current version of ESSTRA consists of the two tools:
ESSTRA Core (esstracore.so
) is a
GCC plugin that intervenes in compilation of
GCC and embeds metadata into the resulting binary file.
In this version, a list of the absolute paths of all source and header
files involved in compilation is embedded in the binary file as metadata.
ESSTRA Utility (esstra.py
) is a Python script for accessing metadata in
binary files embedded by ESSTRA Core.
In this version, you can output metadata in YAML format, shrink metadata by removing duplication, and attach license information to metadata by specifying files in SPDX 2.3 tag-value format which contain license information.
ESSTRA Core creates a section in the resulting ELF file to store metadata during compilation.
ESSTRA Utility allows users to access the metadata. For example, you may update the metadata using license information detected from the source files, delete some or all of the metadata, output the metadata to the console or pass it to some other SCA (Software Composition Analysis) tools.
Before you build the GCC plugin, you have to install a package on your system. For Debian/Ubuntu, check the version of GCC first:
$ gcc --version
gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
...
In this case, the major version is 11, so install the package named
gcc-11-plugin-dev
:
$ sudo apt install gcc-11-plugin-dev
Since ESSTRA Utility uses the PyYAML module to handle YAML data, you may need to install it by, for example, typing:
$ pip install pyyaml
or
$ sudo apt install python3-yaml
After that, run make
in the top directory:
$ make
If no errors, the build is complete.
To install ESSTRA Core and ESSTRA Utility on your system, run the following command:
$ sudo make install
Then esstracore.so
and esstra.py
are installed in /usr/local/share/esstra/
and /usr/local/bin/
, respectively.
The workflow using ESSTRA is as follows:
- Compile source files with GCC using ESSTRA Core
- Use ESSTRA Utility to access metadata embedded in the binary files
The example below compiles a source file
hello.c
with gcc
and generates a binary file hello
.
(See also ./samples/sample-hello)
First, compile the source file hello.c
by passing the path of
esstracore.so
to the compiler with the option -fplugin
:
$ gcc -fplugin=/usr/local/share/esstra/esstracore.so hello.c -o hello
Then the intervention of esstracore.so
embeds metadata in the resulting
binary file hello
. Note that this does not affect the behavior of the
binary file itself.
To access the embedded metadata, use the script esstra.py
. The first argument
of this script is a command, and the second or subsequent arguments are the
arguments of the command.
The command show
displays metadata in binary files in YAML format.
A command line:
$ esstra.py show hello
would generate an output as follows:
#
# BinaryFileName: hello
# BinaryPath: /home/snagao/esstra-test/hello
#
---
SourceFiles:
/home/snagao/esstra-test:
- File: hello.c
SHA1: 8a4090e4471481310808c664efc73b5b2ae6112c
/usr/include:
- File: features-time64.h
SHA1: 57c3c8093c3af70e5851f6d498600e2f6e24fdeb
- File: features.h
SHA1: d8725bb98129d6d70ddcbf010021c2841db783f7
- File: stdc-predef.h
SHA1: 2fef05d80514ca0be77efec90bda051cf87d771f
- File: stdio.h
SHA1: c7181b48c4194cd122024971527aab4056baf600
/usr/include/x86_64-linux-gnu/bits:
- File: floatn-common.h
SHA1: 3f37104123a2e6180621331c1da87125808e47bd
- File: floatn.h
SHA1: 806b759ab6894a09a3b3a422eec5f2414ba7dab7
- File: libc-header-start.h
SHA1: e0a400c194cd3962a342a6504a441920163b799c
- File: long-double.h
SHA1: 4e3f5928e816ad29079d1c7d75f3a510a0939ffb
- File: stdio_lim.h
SHA1: 6210c8ae410ee0f39a6096b0adb9fa86febd3517
- File: time64.h
SHA1: ab2017da21608498b58eea37b2aa6a3387ee978c
- File: timesize.h
SHA1: f1dd8d62a4d75288654626933edfc82ccf2394a7
- File: types.h
SHA1: e5893a9c4c523615c73a51feb9680279608027c6
/usr/include/x86_64-linux-gnu/bits/types:
- File: FILE.h
SHA1: 497924e329d53517631713ae52acb73e870d7d65
- File: __FILE.h
SHA1: 274242343e85d1c06e7f5ccc5abf15e120f6e957
- File: __fpos64_t.h
SHA1: ac38e294b004f6e2bf18f1c55e03dc80f48d6830
- File: __fpos_t.h
SHA1: 760ef77769ac1921f4b1f908cbf06863e2506775
- File: __mbstate_t.h
SHA1: e3a4f2ee55e635520db0b4610d2b361e9ce41de7
- File: struct_FILE.h
SHA1: 1dbf8bac589cb09e09aa4c1d36913e549a57bcf0
/usr/include/x86_64-linux-gnu/bits:
- File: typesizes.h
SHA1: ee94b5a60d007c23bdda9e5c46c8ba40f4eb402c
- File: wordsize.h
SHA1: 281ddd3c93f1e8653e809a45b606574c9b691092
/usr/include/x86_64-linux-gnu/gnu:
- File: stubs-64.h
SHA1: f7603fa3908b56e9d1b33c91590db3252e13a799
- File: stubs.h
SHA1: be168037b7503a82b1cf694cdbac8c063bb6e476
/usr/include/x86_64-linux-gnu/sys:
- File: cdefs.h
SHA1: a419a6372029d89ba38ada0811d34f51df8d09b7
/usr/lib/gcc/x86_64-linux-gnu/11/include:
- File: stdarg.h
SHA1: fa23f49da8a0a5068b781dff7182f1a1c363dc30
- File: stddef.h
SHA1: 0de70008ffa3f198baf55c7b3f3d03b4ca11c21f
For more details, refer to the file ./util/README.md.
It will surely be annoying that you have to specify -fplugin=....
for every
gcc/g++ invocation.
To avoid such a tedious job, just type:
$ sudo make install-specs
This command installs a GCC spec file on your system which enables the option:
-fplugin=/usr/local/share/esstra/esstracore.so
as default.
After that, every compiling something with GCC as usual:
$ gcc hello.c -o hello
generates a binary file with metadata embedded by ESSTRA Core.
This is a very useful feature when you compile some open source (or closed or whatever) projects and also want information ESSTRA generates for them.
For more details about installing/uninstalling the spec file, refer to the file ./core/README.md.
See the LICENSE file.