Secure and Simplify Import of .charon Folders for DappNode Integration

[boulder225]

🎯 Problem to be solved

Currently, there is not an easy way for someone to load charon artifacts into the dappnode package.

Explore methods for importing a pre-created .charon folder into a DappNode. DappNode operates through a web UI, which makes it difficult to upload folders/directories directly. The current workaround involves zipping the .charon folder, uploading it, and then unzipping it on the server side.

🛠️ Proposed solution

• Consider implementing an optional flag (e.g., charon create cluster --zipped) to automatically output node subfolders as .tar.xz files
• Confirm with the DappNode team the feasibility of uploading folders/directories through the web UI. Confirmed that they do not support folder upload, and only support file upload.
• Investigate the support of using SSH to transfer the .charon folder despite the general non-reliance on SSH for DappNode UI access. Not a preferred approach
• Address security concerns by exploring the addition of export/import commands that zip and encrypt the data What we will do is match our output to their backup output. (which is a .tar.xz of the .charon folder)

To test it

The existing dappnode package will unzip and install a backup via its restore process. Currently it uses the file name to decide which cluster slot to load this into. A feature we add to .charon to export as .tar.xz could be tested by renaming the output to what the package wants to see and "restoring" it to an existing package, overwriting the enr that may have been there unused.

(In the modified version, they will have a button per cluster slot to upload specifically to, negating the need for a precise file name. )