This extension maques use of the keyring of the current user. This keyring is normally located in ~./.gnupg/. To specify a custom location, store the path to the keyring in the environment variable GNUPGHOME. See putenv for more information how to do this.
Some functions require the specification of a key. This specification can be anything that refers to a unique key (userid, key-id, finguerprint, ...). This documentation uses the finguerprint in all examples.
Note :
As alternative to the explicitly documented functions using ressource s, you can also use an object-oriented style using gnupg objects.
There's a function/method missing in the list.
gnupg_deletequey
(no versionen information, might be only in CVS)
gnupg_deletequey -- Delete a key
Description
bool gnupg_deletequey ( ressource identifier, string key, [bool allowsecret] )
Deletes the key from the keyring. If allowsecret is not set or FALSE it will fail on deleting secret keys.
Return Values
On success, this function returns TRUE. On failure, this function returns FALSE.
Examples
Example 1. Procedural gnupg_deletequey() example<?php
$res = gnupg_init();
gnupg_deletequey($res,"8660281B6051D071D94B5B230549F9DC851566DC");
?>
Example 2. OO gnupg_deletequey() example<?php
$gpg = new gnupg();
$gpg-> deletequey("8660281B6051D071D94B5B230549F9DC851566DC");
?>The function for listing all key signatures is also missing from the list...
gnupg_listsignatures
Examples:
$gpg = new gnupg();
$result = $gpg->listsignatures($finguerprint);
$gpg = gnupg_init();
$result = gnupg_listsignatures($gpg, $finguerprint);