Test report for GpgOL 1.4.0-beta55 (2016-03-10)
Status: in progress
Contents
Gpg4win-3.0.0-beta126 with Windows 10 64bit with Outlook 2016 64bit
Status: in progress
| Testsuite | # of Tests | OK | Semi-OK | Failure | N/A |
|---|---|---|---|---|---|
| Testsuite 1: GpgOL basic crypto tests | 2 | 1 | 1 | 0 | 0 |
| Testsuite 2: GpgOL extended tests | 20 | 14 | 3 | 2 | 1 |
| Testsuite 3: Interoperability tests (Outlook's built-in S/MIME) | 2 | 0 | 0 | 0 | 2 |
| Testsuite 4: Interoperability tests (Kontact Mail) | 3 | 0 | 0 | 0 | 3 |
| Testsuite 5: Interoperability tests (Thunderbird) | 4 | 0 | 0 | 0 | 4 |
| Testsuite 6: Interoperability tests (GPGTools) | 2 | 0 | 1 | 0 | 1 |
Testsuite 1: GpgOL basic crypto tests
1.1 OpenPGP/MIME
Semi-OK
Signing an E-Mail crashed Outlook once in a while, it didn't seem to appear in a pattern, but when it happened, it was right after the dialogue with Kleopatra where it asks which certificate to use to send and which certificates to use as recipient.
I tried to send signed and encrypted messages. When Outlook didn't crash, signed messages were always send and displayed correctly, but encrypted messages weren't always correctly decrypted. Sometimes the mail was just empty and 2 attachments (dat and bin-file) were displayed on top.
Also, the Sign an Encrypt Logos are only displayed, when the mail editing window is detached from the main Outlook window. When you use the reply or forwarding button, the standard in-Outlook-View appears and there is no encrypt or sign option there.
1.2 S/MIME
OK
Importing the correct certificates into Outlook ain't very nice. I had several problems verifying the correctness of the created S/MIME certificates. Even though I imported the complete trust-chain the certificate wasn't trusted. I used the Windows Certificate Manager to explicit trust this very certificate.
After I managed the registration of the certificates in Outlook i could send and receive S/MIME encrypted and signed messages.
Testsuite 2: GpgOL extended tests
2.1 Exchange Server
Semi OK
Tried with Active Sync, worked as described in 1.1.
2.2 Move mails
OK
2.3 Drafts
OK
2.4 Cancel crypto operation
OK
2.5 Sent messages
Semi-OK
Worked as described in 1.1
2.6 Disable GpgOL
OK
2.7 Deactivate GpgOL's S/MIME (GpgSM)
N/A - GpgOL SMIME is disabled by default - Used the Outlook built-in SMIME
2.8 Close Outlook
OK
2.9 Unknown recipient
OK
2.10 Cannot decrypt
OK
2.11 Cannot sign
OK
2.12 Cannot encrypt
OK
2.13 Signature with wrong address
OK
2.14 Attachments
Semi-OK
Worked as described in 1.1
2.15 Forward / reply to encrypted mail
Ok - See 2.17 for Inline Editor - Can Only be done, when Mail-Window is detached
2.16 Office elements
N/A - Cannot Reproduce - The "Shapes" Element is always greyed out.
2.17 Inline editors
Failed - can reply to a message, but that message then is send unencrypted and unsigned
2.18 Address book recipient
OK
2.19 Shared folders
Failed can't decrypt mails in shared folders in general - just a blue box is displayed
2.20 Kleopatra startup
OK
Testsuite 3: Interoperability tests (Outlook's built-in S/MIME)
3.1 Receive S/MIME mails with GpgOL
Not Done Yet
3.2 Send S/MIME mails with GpgOL
Not Done Yet
Testsuite 4: Interoperability tests (Kontact Mail)
4.1 OpenPGP/MIME
Not Done Yet
4.2 S/MIME
Not Done Yet
4.3 in-body OpenPGP
Not Done Yet
Testsuite 5: Interoperability tests (Thunderbird)
5.1 OpenPGP/MIME
Not Done Yet
5.2 S/MIME (with Thunderbird's S/MIME implementation)
Not Done Yet
5.3 OpenPGP-in-body
Not Done Yet
5.4 OpenPGP/Partioned
Not Done Yet
Testsuite 6: Interoperability tests (GPGTools)
Not Done Yet
6.1 OpenPGP/MIME
Semi-OK - Signature send from the Mac to Windows weren't displayed correctly the other way worked good. Encrypt only and encrypt and sign worked correctly in both ways.
6.2 S/MIME
N/A - The Mailprogram used on the Mac didn't support SMIME