DeforaNetworks/fwknop
3
0
Fork 0
Code Releases Activity

Added GPG_ALLOW_NO_PW to the fwknopd man page

Browse Source
This commit is contained in:
Michael Rash
2012-08-14 22:31:03 -04:00
parent 66187a22af
commit 7ae45ecad1
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/fwknopd.man.asciidoc
View File

@@ -403,6 +403,16 @@ directive starts a new stanza.
``GPG_DECRYPT_ID'' above. This is a required field for gpg-based
authentication.
*GPG_ALLOW_NO_PW*: '<Y/N>'::
Allow *fwknopd* to leverage a GnuPG key pair that does not have an
associated password. While this may sound like a controversial deployment
mode, in automated environments it makes sense because "there is usually no
way to store a password more securely than on the secret keyring itself"
according to: ``http://www.gnupg.org/faq/GnuPG-FAQ.html#how-can-i-use-gnupg-in-an-automated-environment''.
Using this feature and removing the passphrase from a GnuPG key pair is
useful in some environments where libgpgme is forced to use gpg-agent
and/or pinentry to collect a passphrase.
*GPG_REQUIRE_SIG*: '<Y/N>'::
With this setting set to 'Y', fwknopd check all GPG-encrypted SPA
messages for a signature (signed by the sender's key). If the incoming