The current implementation of script generation in the GUI will process input binaries, but it has no side effects. Generated scripts should be able to flush files to disk when they have been downloaded in the GUI.
As an OFRAK user, I want to be able to extract a file from a deeply-nested structure in the GUI, and then generate a script that can repeat that extraction by dumping the extracted file to disk somewhere.
Does the feature contain any proprietary information about another company's intellectual property?
No.
How would you implement this feature?
Since the "Download" button in the GUI runs fully client-side, whoever implements this will need to create an API endpoint to add a flush_to_disk step to the script in the back end. Then the function run when the GUI "Download" button is pressed will need to be updated to make a request to this endpoint, and call resource.update_script().
Are there any (reasonable) alternative approaches?
What is the use case for the feature?
The current implementation of script generation in the GUI will process input binaries, but it has no side effects. Generated scripts should be able to flush files to disk when they have been downloaded in the GUI.
As an OFRAK user, I want to be able to extract a file from a deeply-nested structure in the GUI, and then generate a script that can repeat that extraction by dumping the extracted file to disk somewhere.
Does the feature contain any proprietary information about another company's intellectual property?
No.
How would you implement this feature?
Since the "Download" button in the GUI runs fully client-side, whoever implements this will need to create an API endpoint to add a
flush_to_diskstep to the script in the back end. Then the function run when the GUI "Download" button is pressed will need to be updated to make a request to this endpoint, and callresource.update_script().Are there any (reasonable) alternative approaches?
None that I can think of.