array ( 0 => 'index.php', 1 => 'PHP Manual', ), 'head' => array ( 0 => 'UTF-8', 1 => 'pt_BR', ), 'this' => array ( 0 => 'ref.gnupg.php', 1 => 'GnuPG Funções', ), 'up' => array ( 0 => 'book.gnupg.php', 1 => 'GnuPG', ), 'prev' => array ( 0 => 'gnupg.examples-clearsign.php', 1 => 'Clearsign text', ), 'next' => array ( 0 => 'function.gnupg-adddecryptkey.php', 1 => 'gnupg_adddecryptkey', ), 'alternatives' => array ( ), 'source' => array ( 'lang' => 'en', 'path' => 'reference/gnupg/reference.xml', ), 'extra_header_links' => array ( 'rel' => 'alternate', 'href' => '/manual/en/feeds/ref.gnupg.atom', 'type' => 'application/atom+xml', ), ); $setup["toc"] = $TOC; $setup["toc_deprecated"] = $TOC_DEPRECATED; $setup["parents"] = $PARENTS; manual_setup($setup); ?>
This extension makes 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, fingerprint, ...). This documentation uses the fingerprint in all examples.
Nota:
As alternative to the explicitly documented functions using resources, you can also use an object-oriented style using gnupg objects.