Fix misformating in Split GPG doc

An error was introduced in pull request #717.
This commit is contained in:
Fidel Ramos 2018-10-24 17:17:36 +00:00 committed by GitHub
parent 4fd0cb1110
commit 659baf3a02
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -78,10 +78,10 @@ there? To Be Determined.
GnuPG backend is protected by a passphrase, it will give a *"Inappropriate ioctl GnuPG backend is protected by a passphrase, it will give a *"Inappropriate ioctl
for device"* error. Avoid setting passphrases for the private keys in the GPG for device"* error. Avoid setting passphrases for the private keys in the GPG
backend domain, it won't provide extra security anyway, as explained before. If backend domain, it won't provide extra security anyway, as explained before. If
you have a private key that already has a passphrase set use `gpg2 --edit-key you have a private key that already has a passphrase set use
<key_id>`, then `passwd` to set an empty passphrase. Be aware that `gpg2 --edit-key {key_id}`, then `passwd` to set an empty passphrase. Be aware
`pinentry-ncurses` doesn't allow setting empty passphrases, so you would need to that `pinentry-ncurses` doesn't allow setting empty passphrases, so you would need
install `pinentry-gtk` for it to work. to install `pinentry-gtk` for it to work.
## Configuring Split GPG ## ## Configuring Split GPG ##