2004-09-27 Marcus Brinkmann <marcus@g10code.de>

	* gpgme.texi (Passphrase Callback): Document
	GPG_ERR_NOT_IMPLEMENTED.

diff --git a/trunk/doc/ChangeLog b/trunk/doc/ChangeLog
index afb6a8d39e2cd26708f655a6d3f9a9bd39bd48c6..fba19d06d7f1d7b2d81e6b3dc52ad013a26bb5be 100644 (file)
--- a/trunk/doc/ChangeLog
+++ b/trunk/doc/ChangeLog
@@ -1,5 +1,8 @@
 2004-09-27  Marcus Brinkmann  <marcus@g10code.de>
 
+       * gpgme.texi (Passphrase Callback): Document
+       GPG_ERR_NOT_IMPLEMENTED.
+
        * gpgme.texi: Update copyright year for tex version.
 
 2004-07-29  Moritz Schulte  <moritz@g10code.com>

diff --git a/trunk/doc/gpgme.texi b/trunk/doc/gpgme.texi
index 6b903f3ce4e46e26bb14d7030c8afeebd1fa3a06..04a828a5dcac13dab8c9727ff1e2442d7891e9a4 100644 (file)
--- 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