Julien Viard de Galbert
Julien Viard de Galbert
Standard visitors (table, extract, save) are implemented: #250 And new visitors are in progress in #251 Note that all this only cover the 'NVAR' format (used by AMI firmwares) however...
Just a quick note, #251 is merged. Maybe this issue can be closed, unless you want to keep it to track other nvram format.
This is started see #239
Does this have something to do with the offset I calculated for the `layout-table` visitor ? If so this would make the visitor easier, but all visitors that modify the...
@xaionaro I think so: - an element cannot know it's own offset, it needs to get it from it's parent, so it's probably easier to store it - the offset...
The image use FFSv1 GUID for their firmware volume (even if UEFITool displays a FFSv2 Subtype). Whitelisting the FFSv1 GUID in `pkg/uefi/firmwarevolume.go` `supportedFVs` does allows to go a little deaper...
This should be easier now that #288 is merged, however #288 doesn't add the signature (it assume it's present in the unmodified part of the buffer). so it should be...
In particular currently `Erase` and `IsErased` have a `polarity` parameter. - `Erase` is ignoring it and using the global variable - `IsErased` uses it (it was easier for my initial...
Hello, first I've not looked into the code yet, but regarding your point about `PositionUpdater` above you can place it in the visitor package along with other visitors. There is...
Hello, Just a few thought: To my knowledge, the copy is not really a problem, all you have to do is call assemble after you changed a file. I'm not...