2004-09-27 Marcus Brinkmann <marcus@g10code.de>
* gpgme.texi (Passphrase Callback): Document GPG_ERR_NOT_IMPLEMENTED.
This commit is contained in:
parent
ae7ead80a0
commit
b8b44c4767
@ -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>
|
||||
|
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user