Update encryption example to distinguish input
The example for how to encrypt a gauth.csv file using openssl implicitly assumes the input and output are different files. But if you run that command while already in the output directory, they will be the same path, and it appears openssl may clobber the output. To avert this, explicitly indicate in the example that the input is in the home directory, and the output is elsewhere. The actual paths do not matter, this is just to keep the example safe.
This commit is contained in:
parent
f5a1f722c0
commit
b3d8c2bc50
@ -46,7 +46,7 @@ Encryption
|
||||
|
||||
`gauth` supports password-based encryption of `gauth.csv`. To encrypt, use:
|
||||
|
||||
$ openssl enc -aes-128-cbc -md sha256 -in gauth.csv -out ~/.config/gauth.csv
|
||||
$ openssl enc -aes-128-cbc -md sha256 -in ~/gauth.csv -out ~/.config/gauth.csv
|
||||
enter aes-128-cbc encryption password:
|
||||
Verifying - enter aes-128-cbc encryption password:
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user