more software signatures

[jstucke]

• added some software signatures (mbed TLS, file, opkg)

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 66.66667% with 7 lines in your changes missing coverage. Please review.

Project coverage is 92.07%. Comparing base (bd5bdb0) to head (08eb5b6).
Report is 16 commits behind head on master.

Files with missing lines	Patch %	Lines
...is/software_components/code/software_components.py	61.11%	7 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1301      +/-   ##
==========================================
- Coverage   92.21%   92.07%   -0.15%     
==========================================
  Files         377      378       +1     
  Lines       23068    21429    -1639     
==========================================
- Hits        21273    19730    -1543     
+ Misses       1795     1699      -96     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[maringuu]

Can you document somewhere (commit message/code comments), why these signatures are correct?
I think it is important to not only have signatures, but also be able to verify why they are correct.
The most preferable proof would we permalinks to source code, but I'm happy with anything that allows me to understand why the signatures are as they are.

[jstucke]

Can you document somewhere (commit message/code comments), why these signatures are correct? I think it is important to not only have signatures, but also be able to verify why they are correct. The most preferable proof would we permalinks to source code, but I'm happy with anything that allows me to understand why the signatures are as they are.

I tried to find the corresponding places in the source code but I also found that in libmagic the version is stored as an integer instead of a string. The FSR currently does not have the capability to extract integers, so I added it.