I have just enabled SMIME support in RT 4.4.2 and noticed that it doesn’t really like our smime certificates. When it receives a signed email, there are a couple of errors in the logs:
Jul 28 08:21:46 rt4 RT: [10528] Use of uninitialized value in concatenation (.) or string at /usr/local/rt4/sbin/../lib/RT/Crypt/SMIME.pm line 946.
Jul 28 08:21:46 rt4 RT: [10528] Use of uninitialized value in concatenation (.) or string at /usr/local/rt4/sbin/../lib/RT/Crypt/SMIME.pm line 967.
Jul 28 08:21:46 rt4 RT: [10528] Use of uninitialized value in concatenation (.) or string at /usr/local/rt4/sbin/../lib/RT/Crypt/SMIME.pm line 967.
Jul 28 08:21:46 rt4 RT: [10528] Use of uninitialized value in concatenation (.) or string at /usr/local/rt4/sbin/../lib/RT/Crypt/SMIME.pm line 522.
Jul 28 08:21:46 rt4 RT: [10528] Use of uninitialized value $v in concatenation (.) or string at /usr/local/rt4/sbin/../lib/RT/Crypt/SMIME.pm line 654.
It also doesn’t show the issuer in the web interface:
SMIME: The signature is good, signed by , trust is full
I have checked the res hash and it doesn’t have a String value set for either Issuer nor User. That again seems to be set only if the certificate of the subject or issues contains an email address in the cn (function canonicalize). Our certificates, however, have the email address set in the x509v3 extension “Subject Alternative Name”.