Option to save firmware backup locally

[hyshka]

I get that you'd want the backup firmware on a USB drive in case of failure but as I went through it I thought it strange to not have an option to save the firmware locally. In my case I wanted to save it locally because I didn't have a USB immediately on-hand and I was planning to copy the firmware online as well.

I can help put together a PR if you think this is a valid use case.

[MrChromebox]

the main reason I didn't implement that as an option was I didn't want people backing up locally when running ChromeOS, then flashing the firmware and not being able to access that backup (because it's encrypted and no longer accessible). I'd have no problem accepting a PR for a local backup option provided it wasn't available when running the stock firmware and/or when running ChromeOS

On Mon, Oct 29, 2018 at 6:56 PM Bryan Hyshka [email protected] wrote:

I get that you'd want the backup firmware on a USB drive in case of failure but as I went through it I thought it strange to not have an option to save the firmware locally. In my case I wanted to save it locally because I didn't have a USB immediately on-hand and I was planning to copy the firmware online as well.

I can help put together a PR if you think this is a valid use case.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/MrChromebox/scripts/issues/74, or mute the thread https://github.com/notifications/unsubscribe-auth/AA56plZrOV1R_hL4x60OdX7pZ2B9owNNks5up5WcgaJpZM4YA61a .

[hyshka]

I see where you're coming from. Since ChromeOS encrypt disks by default it wouldn't be recoverable unless the user had taken a second, independent of the firmware scripts, step to copy that file to online storage. It also makes it especially hazardous as scripts offer the option to reboot after flashing new firmware.

I am going to put a little more thought into this and see if I can come up with a reasonably approach.