Open Bug 1532626 Opened 6 years ago Updated 2 years ago

Add more S/MIME xpcshell tests to Thunderbird

Categories

(MailNews Core :: Security: S/MIME, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: KaiE, Unassigned)

References

Details

Attachments

(1 file)

In bug 1011625, we added a basic set of S/MIME tests.

We should expand the tests with a broader variety of test messages, for example, complex nested messages. The initial comment in bug 1011625 also has additional suggestions.

For the initial tests from bug 1011625, we used certificates that are auto generated by NSS, this avoids the complexity of certificate generation. And we also obtained a basic set of test S/MIME messages.

For additional test scenarios, we should produce them outside of NSS, and inside the Thunderbird tree.

Once we have cmsutil built as part of TB, this will be possible.

Summary: Add more S/MIME tests → Add more S/MIME xpcshell tests to Thunderbird
Severity: normal → S3

· Cryptographic Message Syntax (CMS): rfc3852 2004/rfc5652 2009

Thunderbird is like an old car with restored body and seat, but with a run-down engine and worn-out brake pads. As long as it works and doesn't smoke, it's better not to fix anything, cause it will fall apart. It is so neglected that after draining the old oil and pouring in new oil, it will not start up anymore bug#676100#c15. There were no regular maintenance.

To know what needs to be done and fixed, you need experienced mechanics who know what they are doing bug#480174#c8, bug#215997#c7. Before that, you need to perform diagnostics, what is missing, what replacements to use, whether it is worth it, etc.

· rfc4134 Examples of S/MIME Messages

I looked at the NSS bug list for S/MIME and x.509 certificates. I also checked the various tests performed and found no mention of rfc4134. I wrote a script where I extract these certificates and messages and check with various programs what is in them. While looking through and studying this rfc, ideas arise as to what additional tests can be performed. I add the file in the attachment, maybe it will be useful.

When it comes to testing, it's also WORTH looking at old PDFs that tested the interoperability of various email clients. And then compare the list of bug concerning S/MIME in this folder and make decisions.

· CMS (RFC 3852) Implementation Report
· S/MIME – great idea, pity about the implementation
· Secure Messaging And PKI Interoperability Demonstrator Final Report
· NIST S/MIME Interoperability Testing NISS Paper3.doc
· The PKI Challenge - Interoperability Criteria Specification WP2-N013.pdf

· 76 tests X.509 Path Validation Test Suite, Version 1.07
· a LOT of tests The Public Key Interoperability Test Suite (PKITS) also available from this bug report: bug#1375900

Someone even did some interesting compilations and reports, see bug#95262, bug#476979


bugs:

bug#1645348, bug#216123, bug#228997, bug#232737, bug#265675, bug#414556, bug#414563, bug#522497, bug#523832, bug#1349226

Attached file rfc4134.tar.gz
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: