You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy-pasting seed phrases or private keys is highly insecure. Ledger and Trezor support is great, but also cumbersome.
Ideally, encrypted keystore files could be supported where the passphrase would either needs to be entered interactively or via a secret.
Docker swarm mode supports docker secrets, which allows accessing them under /run/secrets/<secret_name>.
The text was updated successfully, but these errors were encountered:
I would create a docker secret first (e.g. a keystorefile file or secret) using: cat myKeyStoreFile.json | docker secret create signer1 -
Then I would load the secret which never get's persisted on the file system btw but are only stored in memory as data rafts. They only exist in a virtual filesystem managed by Docker, and they are only accessible to the containers that have been granted access to them. load_cli_owners_from_file /run/secrets/signer1
Copy-pasting seed phrases or private keys is highly insecure. Ledger and Trezor support is great, but also cumbersome.
Ideally, encrypted keystore files could be supported where the passphrase would either needs to be entered interactively or via a secret.
Docker swarm mode supports docker secrets, which allows accessing them under
/run/secrets/<secret_name>
.The text was updated successfully, but these errors were encountered: