-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for reading Fortinet firmware files #652
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #652 +/- ##
==========================================
- Coverage 74.84% 74.83% -0.01%
==========================================
Files 288 288
Lines 23932 24038 +106
==========================================
+ Hits 17912 17990 +78
- Misses 6020 6048 +28
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
This adds transparant decompression and deobfuscation of FortiGate firmware files via the `FortiFirmwareContainer` and `FortiFirmwareFile` classes. The filename has to end with `-FORTINET.out` for it to be detected as a Fortinet firmware file. Example usage: $ target-shell FGT_VM64-v7.4.3.F-build2573-FORTINET.out $ target-fs FGT_2000E-v5-build1673-FORTINET.out ls /migadmin
To decrypt a Fortigate firmware file you can now also use: $ python3 -m dissect.target.containers.fortifw <firmware file> | xxd
Co-authored-by: Erik Schamper <[email protected]>
b46635e
to
5a9c679
Compare
This adds transparant decompression and deobfuscation of Fortinet firmware files via the
FortiFirmwareContainer
andFortiFirmwareFile
classes.The filename has to end with
-FORTINET.out
for it to be detected as a Fortinet firmware file.Example usage:
Or to decompress and deobfuscate a firmware file to stdout:
Closes #655