[Security issue] Seed phrase in shell history

[willemneal]

Currently when generating a key from a seed phrase the phrase is part of the initial command.

 near generate-key bob.near --seedPhrase="..."

This is akin to typing out a password is plaintext and will remain in the shell's history. Also currently keys are stored in plaintext, but assuming that that issue was addressed with being encrypted with a password, this would still be an issue.

1. 1. Solution

Using --seedPhrase instead uses stdin and treats the input like a password when logging in with SSH.

[abacabadabacaba]

Secrets must never be passed in command line arguments. On Linux, any process can see command line arguments of any other process, even if this process belongs to a different user.

[willemneal]

Currently the documentation says to do this.

https://docs.near.org/docs/tools/near-cli#4a-near-generate-key---seedphraseyour-seed-phrase