Release 3.1.2

[ShutdownRepo]

Additions

• Exegol images are now based on Debian 12 🥳
• Introducing a CCC (Code Compliance Checks) in the pipeline. The will make sure the bash function used to install tools are compliant and follow best practices, mainly using ShellCheck.
• Release images now share a common base layer to save some space. The pipelines were modified, and documented accordingly.
• The pipelines were greatly improved with the addition of "Catch And Retry" (referred to internally as CNR) that catches commands that fail for network reasons, and try to re-run them, effectively virtually removing all build fails due to timeouts and similar.
• Multiple Python versions are now installed (including latest 3.12, but also 2.7) and managed using pyenv
• Introducing a new beta feature: Remote Graphical Desktop. This feature is undocumented right now, as guidance and support is dedicated to the Discord community. Proper elements will be released once beta testing ends for this feature. This feature relies on XFCE4 and VNC/NoVNC to provide a graphical remote desktop for users. This is especially useful for macOS and Windows hosts were X11 sharing is limited, but also for pro users that deploy Exegol containers on Cloud Private Servers.
• Huge improvement on the documentation (contributors, maintainers, services, resources lists, ...).

New tools

Chainsaw, RsaCracker, ppfinder, Azure-cli, tig, ROADtools, GoMapEnum, yalis, TeamsPhisher, sherlock
blackbird, MurMurHash, GeoPincer, censys-python, yt-dlp, BloodHound-CE, NetExec, RustScan, GPOddity, pkcrack, pymeta, extractbitlockerkeys, cewler, LDAPWordlistHarvester, pywerview, freeipscanner, CyberChef, nmap-parse-output, Empire, legba, havoc, villain, ntlm_theft, bloodhound-ce ingestor, abuseACL, and a few other things here and there ...

Fixes

On tools installs, history commands, aliases, configurations, unit test commands in the pipeline etc. (pwntools, metasploit framework, trilium, 7zip2john, bloodhound.py, proxmark, ...).

External contributions

@Skileau @spameier @Neptunium931 @gbe @compass-dexter @lap1nou @AetherBlack @cHJlaXpoZXI (I hope I'm not forgetting anyone, truly sorry if that's the case)

As usual, a huge thanks to the whole Exegol team for this great progress 👏

[Dramelac]

Seems good to me!

[Neptunium931]

the failed tests are due to a problem in the alies with an alias command=(command) structure if arguments must be passed
error example #283 (comment)
fix in #286 (comment)

[Dramelac]

the failed tests are due to a problem in the alies with an alias command=(command) structure if arguments must be passed error example #283 (comment) fix in #286 (comment)

Indeed, already working on a permanent fix to keep the desired behavior while passing the arguments. I'm running some test to ensure no regressions

[Neptunium931]

the failed tests are due to a problem in the alies with an alias command=(command) structure if arguments must be passed error example #283 (comment) fix in #286 (comment)

Indeed, already working on a permanent fix to keep the desired behavior while passing the arguments. I'm running some test to ensure no regressions

I suggest function
exampe for MultiRelay
MultiRelay() {(cd /opt/tools/Responder/tools/ && /opt/tools/Responder/venv/bin/python3 /opt/tools/Responder/tools/MultiRelay.py "$@")}

[Dramelac]

the failed tests are due to a problem in the alies with an alias command=(command) structure if arguments must be passed error example #283 (comment) fix in #286 (comment)

Indeed, already working on a permanent fix to keep the desired behavior while passing the arguments. I'm running some test to ensure no regressions

I suggest function exampe for MultiRelay MultiRelay() {(cd /opt/tools/Responder/tools/ && /opt/tools/Responder/venv/bin/python3 /opt/tools/Responder/tools/MultiRelay.py "$@")}

Yes that was the plan. It worked on my local tests. Hopefully everything will be good this time