commandline options about uefitool

[NikolajSchlej]

Hi.

CLI requests are often, but I can't implement it right now because of complete lack of free time.
FFSEngine can indeed be used without UEFITool, but it has no suitable operations for tree traversing, so you need to reimplement QTreeView class, because FFSEngine works with QModelIndex'es.
I will make it more generic and less Qt-based after some refactoring rounds, I hope, but all I have right now is this.
If you have some ideas on how this CLI must look and how it must work - feel free to post it here, because right now I have none of them. Pull requests of any sorts are welcome too.

[vikasnkumar]

Hi

Ok. I will look at it to see if I can rip out QTreeView from FFSEngine
to make it more abstract, but if it is part of your design it may be
time consuming.

For the CLI, from my perspective, all I want to do is take a large BIOS
blob from the vendor and break it up into its components. I don't think
anyone would want to use the CLI to modify the components but maybe
there are programs that might want to do that or might want to wrap the
UEFITool as a library to do that.

this is how I would like to use it to extract all the components. then
the extracted components would automatically be saved in the current
directory or a new directory with their GUIDs acting as file names.
there would be an index file created that has the contents of the
TreeView that you have in the UEFITool so that someone could read the
contents and know which GUID refers to which component.
$ ./uefitool --extract bios_image.fd

Thanks

On 03/19/2014 07:08 AM, Nikolaj Schlej wrote:

Hi.

CLI requests are often, but I can't implement it right now because of
complete lack of free time.
FFSEngine can indeed be used without UEFITool, but it has no suitable
operations for tree traversing, so you need to reimplement QTreeView
class, because FFSEngine works with QModelIndex'es.
I will make it more generic and less Qt-based after some refactoring
rounds, I hope, but all I have right now is this.
If you have some ideas on how this CLI must look and how it must work

• feel free to post it here, because right now I have none of them.
  Pull requests of any sorts are welcome too.

—
Reply to this email directly or view it on GitHub
#4 (comment).

[NikolajSchlej]

Extraction will be implemented soon, it's easy and have no requirements to any classes except FFSEngine and members of QtCore. Modification and repacking will be a bit harder to implement without GUI, but still can be done. Will do something about it soon, I hope.

[vikasnkumar]

In my opinion, anyone who needs to modify will be manually doing it most
likely and hence the GUI works for that scenario. Extraction on the
other hand can be utilized by various malware analysis tools which will
most likely not want the GUI. I think doing extraction will be a big
win. You may want to wait for user demand for CLI-based
modification/repacking before implementing that.

On 03/19/2014 10:25 AM, Nikolaj Schlej wrote:

Extraction will be implemented soon, it's easy and have no
requirements to any classes except FFSEngine and members of QtCore.
Modification and repacking will be a bit harder to implement without
GUI, but still can be done. Will do something about it soon, I hope.

—
Reply to this email directly or view it on GitHub
#4 (comment).

[NikolajSchlej]

I wrote UEFIExtract utility (project file is located in UEFIExtract subfolder) that can be used from CLI to extract UEFI image file into directory tree.

[vikasnkumar]

That is awesome ! Thank you very much.

On 05/03/2014 07:00 AM, Nikolaj Schlej wrote:

I wrote UEFIExtract utility (project file is located in UEFIExtract
subfolder) that can be used from CLI to extract UEFI image file into
directory tree.

—
Reply to this email directly or view it on GitHub
#4 (comment).

[Zibri]

uefiextract creates too long paths in windows.. which is of if extracting a full image but not ok if you need to extract a single GUID

[NikolajSchlej]

Try UEFIDump, it extracts everything into a single subfolder