cmd, ethkey: Amend the new flags in the README, to match the ethkey updates

This commit is contained in:
Evangelos Pappas 2018-08-07 10:42:15 +01:00
parent 3589cebbc0
commit 0778f09c6a
No known key found for this signature in database
GPG key ID: F6FEDFFE62C87FC6

View file

@ -25,12 +25,20 @@ make sure to use this feature with great caution!
Sign the message with a keyfile. Sign the message with a keyfile.
It is possible to refer to a file containing the message. It is possible to refer to a file containing the message.
To sign a message contained in a file, use the `--msgfile` flag.
### `ethkey verifymessage <address> <signature> <message/file>` ### `ethkey verifymessage <address> <signature> <message/file>`
Verify the signature of the message. Verify the signature of the message.
It is possible to refer to a file containing the message. It is possible to refer to a file containing the message.
To sign a message contained in a file, use the --msgfile flag.
### `ethkey changepassphrase <keyfile>`
Change the passphrase of a keyfile.
use the `--newpasswordfile` to point to the new password file.
## Passphrases ## Passphrases
@ -39,3 +47,7 @@ For every command that uses a keyfile, you will be prompted to provide the
passphrase for decrypting the keyfile. To avoid this message, it is possible passphrase for decrypting the keyfile. To avoid this message, it is possible
to pass the passphrase by using the `--passwordfile` flag pointing to a file that to pass the passphrase by using the `--passwordfile` flag pointing to a file that
contains the passphrase. contains the passphrase.
## JSON
In case you need to output the result in a JSON format, you shall by using the `--json` flag.