Skip to Content.
Sympa Menu

en - Re: [sympa-users] s/mime encryption with Sympa 3.4.x

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Aumont - Comite Reseaux des Universites <address@concealed>
  • To: Glenn Gillis <address@concealed>
  • Cc: address@concealed
  • Subject: Re: [sympa-users] s/mime encryption with Sympa 3.4.x
  • Date: Fri, 05 Mar 2004 09:02:03 +0100

Glenn Gillis wrote:


I've also noticed the directory I've specified for user certs never gets populated with anything, even if I send a signed (but not encrypted) message to the list trying to get my email cert accepted, and suggested by the above message.

When sending a s/mime signed message anywhere acrosss Sympa, Sympa catch the related certificat in expl/X509-user-cert (this is the default dir). The certificat are stored only if the S/MIME signature is recognized by Sympa. So you need to configure Sympa in order to trust certificats comming from your CA. This is mandatory in order to deliver any encrypted message because Sympa need to collect subscribers certs first. If the directory expl/X509-user-cert is empty no encrypted mùessage can be sent by Sympa.

The thing to do is to run "sympa.pl -d --keepcopy=/tmp" and send en signed message to your robot. The log will show you the exact openssl call Sympa use.


From this entry in the bug tracker:

http://listes.cru.fr/mantis/view_bug_advanced_page.php?f_id=0000089


This bug fixe is mandatory to use encryption, so you should use sympa 3.4.4.3 or beter sympa-4.0.b2. (to be relesed in a few days), both include this fixe. Sympa-4 include some others fixes related to S/MIME.

Serge

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature




Archive powered by MHonArc 2.6.19+.

Top of Page