[Rt-commit] rt branch, smime, updated. rt-3.8.7-192-g2676fa0

[Ruslan Zakirov]

The branch, smime has been updated
       via  2676fa0e5a771b9e6abcb06f568c4aff07d55c4e (commit)
       via  7ca41145e1bd4a5829d022630c8bd7c904395c08 (commit)
      from  8f8068884e624a960a4e9653cbca62dfadd751cb (commit)

Summary of changes:
 etc/RT_Config.pm.in |   19 ++++++++++++++-----
 1 files changed, 14 insertions(+), 5 deletions(-)

- Log -----------------------------------------------------------------
commit 7ca41145e1bd4a5829d022630c8bd7c904395c08
Author: Ruslan Zakirov <ruz at bestpractical.com>
Date:   Wed Apr 14 19:27:48 2010 +0400

    update description of the %Crypt hash option

diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in
index dac3c63..1d3a1b1 100755
--- a/etc/RT_Config.pm.in
+++ b/etc/RT_Config.pm.in
@@ -658,9 +658,18 @@ protocols are supported.
 
 Options generic for all cryptography protocols.
 
-Set C<ProcessIncomming> to list of security protocols that should be
-analyzed in incomming emails. Note that C<Auth::Crypt> mail plugin
-should be added anyway to the C<@MailPlugins> option.
+Every enabled security protocol analyzed in incoming emails. Set
+C<Incoming> to list of only those security protocols that should be
+analyzed in incoming emails. Usually you don't need to change this.
+Note that C<Auth::Crypt> mail plugin should be added anyway to
+the C<@MailPlugins> option.
+
+For outgoing emails first security protocol from the above list is
+used. Use C<Outgoing> option to set a security protocol that should
+be used in outgoing emails. This helpful when SMIME and GnuPG are
+analyzed in incoming and you want make sure the correct one is used
+for outogin. At this moment only one protocol can be used to protect
+outgoing emails.
 
 Set C<RejectOnMissingPrivateKey> to false if you don't want to reject
 emails encrypted for key RT doesn't have and can not decrypt.

commit 2676fa0e5a771b9e6abcb06f568c4aff07d55c4e
Author: Ruslan Zakirov <ruz at bestpractical.com>
Date:   Wed Apr 14 19:28:36 2010 +0400

    Don't set GnuPG explicitly as the protocol used for outoging emails
    
    Check in the config code will pick enabled one and GnuPG if
    multiple are enabled

diff --git a/etc/RT_Config.pm.in b/etc/RT_Config.pm.in
index 1d3a1b1..dd59230 100755
--- a/etc/RT_Config.pm.in
+++ b/etc/RT_Config.pm.in
@@ -682,8 +682,8 @@ with incorrect data.
 =cut
 
 Set( %Crypt,
-    Incomming                 => undef, # ['GnuPG', 'SMIME']
-    Outgoing                  => 'GnuPG', # 'SMIME'
+    Incoming                  => undef, # ['GnuPG', 'SMIME']
+    Outgoing                  => undef, # 'SMIME' or 'GnuPG'
 
     RejectOnMissingPrivateKey => 1,
     RejectOnBadData           => 1,

-----------------------------------------------------------------------