From a0b0d98a74bde0c0c17e7001d292b6b98a83947a Mon Sep 17 00:00:00 2001 From: Marcus Brinkmann Date: Mon, 27 Sep 2004 20:24:48 +0000 Subject: [PATCH] 2004-09-27 Marcus Brinkmann * gpgme.texi (Passphrase Callback): Document GPG_ERR_NOT_IMPLEMENTED. --- trunk/doc/ChangeLog | 3 +++ trunk/doc/gpgme.texi | 4 +++- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/trunk/doc/ChangeLog b/trunk/doc/ChangeLog index afb6a8d..fba19d0 100644 --- a/trunk/doc/ChangeLog +++ b/trunk/doc/ChangeLog @@ -1,5 +1,8 @@ 2004-09-27 Marcus Brinkmann + * gpgme.texi (Passphrase Callback): Document + GPG_ERR_NOT_IMPLEMENTED. + * gpgme.texi: Update copyright year for tex version. 2004-07-29 Moritz Schulte diff --git a/trunk/doc/gpgme.texi b/trunk/doc/gpgme.texi index 6b903f3..04a828a 100644 --- a/trunk/doc/gpgme.texi +++ b/trunk/doc/gpgme.texi @@ -2067,7 +2067,9 @@ function is set. Not all crypto engines require this callback to retrieve the passphrase. It is better if the engine retrieves the passphrase from a trusted agent (a daemon process), rather than having each user to -implement their own passphrase query. +implement their own passphrase query. Some engines do not even +support an external passphrase callback at all, in this case the error +code @code{GPG_ERR_NOT_SUPPORTED) is returned. The user can disable the use of a passphrase callback function by calling @code{gpgme_set_passphrase_cb} with @var{passfunc} being -- 2.26.2