#100 - the future of emba

[m-1-k-3]

What are you missing in emba? Let us know how you are using emba, what is working and what doesn't work

From our point of view we have the following areas to improve:

• improve threading (more modules should use it) (Updated deep extraction and s110 #107 / do not execute s30 all the time #106 / More threading in f19 and r09 #102 / Performance updates #97)
• improve the web reporter (see Rewrite web report #101 / Webreport updates #121)
• emba needs to get faster again (we lost a lot of performance with this pull request FreeBSD detection and improved static version detection #92)
• some modules need some cleanup (e.g. P07 - S10 split, S108 removed, P07 cleaned #110)
• Cleanup and speedup of F19 and S115 (F19 and S115 updates, cleanups, certificate details #112 and S115 cleanup and speedup, threading in S11 #115)
• CSV export of aggregator data (CSV aggregator #116)
• Speedup of S105 (S105 update, Metasploit integration, fixes #117)
• Include Metasploit exploit information to aggregator (S105 update, Metasploit integration, fixes #117)
• Include the ability to create configuration profiles (Scan profile support #120)
• Installation summary with hint to update cve-database and protecting your host
• Create a UI for emba (see https://github.com/e-m-b-a/embark)
• Test emba on RPi v4
  tested it, works, but is really slow (RPI v4 with 8 Gigs Ram) and therefore not usable as a standalone server.
• Include a check for the cve-database in the installer (to not touch an already installed and running database environment) (see cve-db update skipping #145)
• Provide docker images for emba (https://hub.docker.com/r/embeddedanalyzer/emba)
• TLI installation process (e.g. image of debian installation)
  I did some research, it would be possible, but not worth the developing time (especially because we are advising to use docker and then it has to be non-interactive)
• switch from docker to podman (should we?)

What else would be great to bring to emba?

[m-1-k-3]

all done.