![]() # 'commented-option' => 'value or undef', To disable these option just comment them out or delete them from the hash Set(%GnuPGOptions, For options without specific value use undef as hash value. Some GnuPG options take arguments while others take none. You can define almost any option you want which gnupg supports, but never try to set options which change output format or gnupg's commands, such as -sign (command), -list-options (option) and other. Use this hash to set options of the 'gnupg' program. Users must have rights to see and modify tickets to use this feature. You can allow users to encrypt data in the database using option AllowEncryptDataInDB. This format is discouraged because modern mail clients typically don't support it well. For each attachments another attachment with a signature is added with '.sig' extension.Įncryption of text parts is implemented using inline format, other parts are replaced with attachments with the filename extension '.pgp'. We sign text parts using clear signatures. This format doesn't take advantage of MIME, but some mail clients do not support GPG/MIME. Technique described in these RFCs is well supported by many mail user agents (MUA), but some MUAs support only inline signatures and encryption, so it's possible to use inline format (see below). This format is also known as GPG/MIME and described in RFC3156 and RFC1847. This framework implements two formats of signing and encrypting of email messages: RFC Format of outgoing messagesįormat of outgoing messages can be controlled using the 'OutgoingMessagesFormat' option in the RT config: Set( %GnuPG, However, note that you must add the 'Auth::GnuPG' email filter to enable the handling of incoming encrypted/signed messages. Set to true value to enable this subsystem: Set( %GnuPG, You can use it to define a keyserver, enable auto-retrieval keys and set almost any option 'gnupg' supports on your system. The second one is a hash with options for the 'gnupg' utility. It enables you to enable/disable facility or change the format of messages. The first one controls RT specific options. There are two hashes, GnuPG and GnuPGOptions in the configuration file. Some options are available via the web interface, but to enable this functionality, you MUST start in the configuration file. You can control the configuration of this subsystem from RT's configuration file. This module provides support for encryption and signing of outgoing messages, as well as the decryption and verification of incoming email. RT::Crypt::GnuPG - encrypt/decrypt and sign/verify email messages with the GNU Privacy Guard (GPG) DESCRIPTION
0 Comments
Leave a Reply. |