Developers of Sympa

[David Verdin <address@concealed>]

Hi Guillaume,

I think it's definitely something in our code. A simple 'perl -e "use Crypt::OpenSSL::RSA;" does not issue the same problem.

I'll try to find what part of the code exactly produces this problem. However I'm quite busy bedtesting Sympa. And by that, I don't mean anything kinky. I'm just sending messages in all the possible configurations to make sure I'll be able to put it in production soon. All the S/MIME part works now OK and DKIM too (once I have installed "Crypt::OpenSSL::Bignum").

So if any of you have time soon to debug the spooler.pl trouble, here's attached a gmail message which contains a valid DKIM signature. You just have to change the message name and X-Sympa-To header to be able to feed it to your msg spool.

And, yes, it is from my gmail account which I nicknamed "Bob Morane". I guess some part of my brains thought it was a hell of a good idea at the time...

Cheers,

David

Le 27/11/12 10:48, Guillaume Rousse a écrit :

address@concealed">Le 27/11/2012 10:30, David Verdin a écrit :
[..]

In Crypt::OpenSSL::RSA::BEGIN at /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi/Crypt/OpenSSL/RSA.pm line 17.

In (eval) at /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi/Crypt/OpenSSL/RSA.pm line 17.

Erreur de segmentation (Note; this means "segmentation fault")

Indeed the module "Crypt::OpenSSL::bignum was not installed. But it is
not required by Crypt::OpenSSL::RSA. It is not event listed in the
dependencies and the line where it is required is enclosed in an eval{},
like this:

BEGIN { eval { require Crypt::OpenSSL::Bignum; }; }

So, on my opinion, the process should not crash when Bignum is not
found. That's what this eval is doing.

So, how comes the spooler.pl crashes?

The segmentation fault is quite surprising, and may eventually explain the issue. If you have the time, you should try to isolate the issue by producing a reproductible and minimal test case, and submit a bug report upstream if relevant.

Alternatively, I'd be happy to try to do it myself, if you can provide me the faulty mail (or any other valid DKIM message, actually).

X-Sympa-To: address@concealed
Return-Path: <address@concealed>
X-Original-To: address@concealed
Delivered-To: address@concealed
Received: from in-paris1-1.relay.renater.fr (out-paris1-1.relay.renater.fr 
[194.214.201.3])
        by imap1.renater.fr (Postfix) with ESMTP id F197E18068
        for <address@concealed>; Fri, 23 Nov 2012 13:56:20 +0100 (CET)
Received: from mail-ea0-f178.google.com ([209.85.215.178])
        by in-paris1-1.relay.renater.fr with bizsmtp
        id T0wL1k0033rX0Ax010wLWt; Fri, 23 Nov 2012 13:56:20 +0100
X-RENATER-F2-Desc: undefined
X-RENATER-F2-Score: 0.00
X-Bizanga: IMP - in-paris1-1.relay.renater.fr
X-Original-Source-IP: 209.85.215.178
Received: by mail-ea0-f178.google.com with SMTP id k11so2895274eaa.37
        for <address@concealed>; Fri, 23 Nov 2012 04:56:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=Z6NzIL6MhkDol+9jZX5qxJ+D2NLJ+GrUZw9lPTEK/8s=;
        b=jv/TOr8N95jAHDal0Vjni+2XMC1q3GZrO3XAd34s14VB0KUuuS5exDQRVllcriIDmn
         XJCJx3s3lYr0OQi3GOkK6MIugrHO3EDBBhB80cOiNVjD9eniDKQZcMNt574WOOeQkS5c
         xsj16k7kMIyKndRjxQjbdcWvKlfpGg2t2xeST8KMhgp/09TPuR0V9be/u/Stqvahe8Cm
         rOe7sVhUHmsoqRZ8iHb/6VvHN1jaDN+L/J1sW87hOmr7uWHv3IUjQZze2GU7Oy2eDdD1
         44TyVJm7drSUAbmmNazGa5ImXxHAmn8JjxJmv54zxDTbwGEQDQRGZ7/MvF5aCu8pun9o
         nw6Q==
MIME-Version: 1.0
Received: by 10.14.194.71 with SMTP id l47mr13322957een.6.1353675380644; Fri,
 23 Nov 2012 04:56:20 -0800 (PST)
Received: by 10.14.37.131 with HTTP; Fri, 23 Nov 2012 04:56:20 -0800 (PST)
Date: Fri, 23 Nov 2012 13:56:20 +0100
Message-ID: 
<address@concealed>
Subject: Test DKIM
From: Bob Morane <address@concealed>
To: address@concealed
Content-Type: multipart/alternative; boundary=047d7b3436b0345c1b04cf291ca6

--047d7b3436b0345c1b04cf291ca6
Content-Type: text/plain; charset=ISO-8859-1

Un test

--047d7b3436b0345c1b04cf291ca6
Content-Type: text/html; charset=ISO-8859-1

Un test <br>

--047d7b3436b0345c1b04cf291ca6--

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