[Rt-commit] r9160 - in rtir/branches/2.3-EXPERIMENTAL: .

[sartak at bestpractical.com]

Author: sartak
Date: Wed Sep 26 13:33:21 2007
New Revision: 9160

Modified:
   rtir/branches/2.3-EXPERIMENTAL/   (props changed)
   rtir/branches/2.3-EXPERIMENTAL/lib/RT/IR/AdministrationTutorial.pod

Log:
 r43073 at onn:  sartak | 2007-09-26 13:33:11 -0400
 Doc reverification and key selection


Modified: rtir/branches/2.3-EXPERIMENTAL/lib/RT/IR/AdministrationTutorial.pod
==============================================================================
--- rtir/branches/2.3-EXPERIMENTAL/lib/RT/IR/AdministrationTutorial.pod	(original)
+++ rtir/branches/2.3-EXPERIMENTAL/lib/RT/IR/AdministrationTutorial.pod	Wed Sep 26 13:33:21 2007
@@ -160,3 +160,23 @@
 from backups. RT::Shredder provides SQL commands to reverse any delete
 operations, so any data that it deletes may be restored.
 
+=head2 GnuPG support
+
+See also the documentation in L<RT::Crypt::GnuPG>.
+
+=head3 Reverification
+
+RTIR supports reverification of incoming email. If a user sends signed mail
+but RTIR doesn't have his public key (or if some other error occurs), then his
+message will be still be processed, but there will be "This message is
+unverified" warnings in the UI. Afterwards, RTIR will automatically attempt to
+reverify that message whenever someone views it.
+
+=head3 Key selection
+
+Sometimes a user will have multiple public keys in RTIR's GPG database. When
+that happens, RTIR has the user writing the message decide which key to use
+when sending that user encrypted mail. They are listed as fingerprints along
+with their trust levels. If only one key is valid, then RTIR will
+automatically choose it instead of asking the user.
+