Recover keys from asymmetrically encrypted key backup file

• Receive a asymmetric key backup file (e.g. oreid_asym_key_backup.json)
• Download a backup decrypt program for your operating system (oreid-backup-recover-macos, oreid-backup-recover-linux, OR oreid-backup-recover-win.exe )
• Populate key file (see below)

If a payload is wrapped (encrypted sucessively with multiple keys), this utility can unwrap the payload (using multiple keys in sequence). If all keys are provided in the keyfile.json, a payload will be completely unwrapped. If all the keys are not available to fully unwrap the payload, this utility will unwrap only the outer layer with a single key (as provided in keyfile.json). And output the partially unwrapped payload.

• Place the input file in the same directory as the utility. The input file is an array of JSON objects (asymmetrically encrypted payloads). Each item in the array is a JSON object or, if the payload is wrapped, it is itself an array of JSON objects with each object being one encryption 'wrap'
• Place the private key(s) needed to decrypt into keyfile.json (a JSON Array of strings). For an encryption payload that is wrapped by multiple keys, keys should appear in the file in the order that they were used to encrypt. The utility will decrypt in reverse order of the key list - i.e. the last key in the array is used to unwrap with first.
  
  

• Run ./oreid-backup-recover-macos {chainName} input.json keys.json

• Run ./oreid-backup-recover-linux {chainName} input.json keys.json

• Run oreid-backup-recover-win.exe {chainName} input.json keys.json

./oreid-backup-recover-macos algorand input.json keys.json output.json

Note: input, key, and output filenames are optional (uses defaults if not provided)

The Examples directory includes example input, key, and output file contents for various scenarios. Please refer to the readme in that directory.

npm install --global [email protected]
nvm install 14.16.1

Node 14 or higher Required by pkg library.
Use nvm current to see if you are running Node 14, if not you can switch to it using nvm.

nvm use node v14.16.1

npm run build

Use pkg version 5.3.3 or higher (earlier version might throw errors)

If you get 'FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory', make sure you are passing in the option max_old_space_size=4096. It should already be set on npm run build command. However if you need to add it manually, you can do the following on the command prompt:

export NODE_OPTIONS=--max_old_space_size=4096