NAME
GnuPG::Options - GnuPG options embodiment
SYNOPSIS
# assuming $gnupg is a GnuPG::Interface object
$gnupg->options->armor( 1 );
$gnupg->options->push_recipients( 'ftobin', '0xABCD1234' );
DESCRIPTION
GnuPG::Options objects are generally not instantiated on their own, but rather as part of a GnuPG::Interface object.
OBJECT METHODS
- new( %initialization_args )
-
This methods creates a new object. The optional arguments are initialization of data members; the initialization is done in a manner according to the method created as described in "new_hash_init" in Class::MethodMaker.
- hash_init( %args ).
-
This method works as described in "new_hash_init" in Class::MethodMaker.
- copy
-
Returns a copy of this object. Useful for 'saving' options.
- get_args
-
Returns a list of arguments to be passed to GnuPG based on data members which are 'meta_' options, regular options, and then extra_args, in that order.
OBJECT DATA MEMBERS
Note that these data members are interacted with via object methods created using the methods described in "get_set" in Class::MethodMaker, "object" in Class::MethodMaker, and "list" in Class::MethodMaker. Please read there for more information.
- homedir
- armor
- default_key
- no_greeting
- verbose
- no_verbose
- quiet
- batch
- always_trust
- comment
- no_comment
- status_fd
- logger_fd
- passphrase_fd
- compress_algo
- force_v3_sigs
- rfc1991
- openpgp
- options
- no_options
- encrypt_to
- recipients
-
These options correlate directly to many GnuPG options. For those that are boolean to GnuPG, simply that argument is passed. For those that are associated with a scalar, that scalar is passed passed as an argument appropriate. For those that can be specified more than once, such as recipients, those are considered lists and passed accordingly. Each are undefined to begin.
Meta Options
Meta options are those which do not correlate directly to any option in GnuPG, but rather are generally a bundle of options used to accomplish a specific goal, such as obtaining compatibility with PGP 5. The actual arguments each of these reflects may change with time. Each defaults to false unless otherwise specified.
- meta_pgp_5_compatible
-
If true, arguments are generated to try to be compatible with PGP 5.
- meta_pgp_2_compatible
-
If true, arguments are generated to try to be compatible with PGP 5.
- meta_interactive
-
If false, arguments are generated to try to help the using program use GnuPG in a non-interactive environment, such as CGI scripts. Default is true.
- meta_signing_key
-
This scalar reflects the key used to sign messages. Currently this is synonymous with the default_key data member.
- meta_recipients_keys
-
This list of keys, of the type GnuPG::Key, are used to generate the appropriate arguments having these keys as recipients.
Other Data Members
- extra_args
-
This is a list of any other arguments used to pass to GnupG. Useful to pass an argument not yet covered in this package.
SEE ALSO
See also "GnuPG::Interface and ."
3 POD Errors
The following errors were encountered while parsing the POD:
- Around line 243:
You forgot a '=back' before '=head2'
- Around line 252:
'=item' outside of any '=over'
- Around line 291:
Nested L<> are illegal. Pretending inner one is X<...> so can continue looking for other errors.
Unterminated L<...> sequence