|
⇤ ← Revision 1 as of 2016-03-11 07:30:29
Size: 52
Comment:
|
Size: 1467
Comment: Added: Testsuite 1: GpgOL basic crypto tests
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| GpgOL/Testreports/1.4.0-beta55 hier beschreiben... | = Test report for GpgOL 1.4.0-beta55 (2016-03-10) = == Gpg4win-3.0.0-beta126 with Windows 10 64bit with Outlook 2016 64bit == === Testsuite 1: GpgOL basic crypto tests === ==== 1.1 OpenPGP/MIME ==== 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 ==== Importing the correct certificates into Outlook ain't very nice. I had serveral problems verifying the correctnes of the created SMIME 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 recieve SMIME crypted and signed messages. |
Test report for GpgOL 1.4.0-beta55 (2016-03-10)
Gpg4win-3.0.0-beta126 with Windows 10 64bit with Outlook 2016 64bit
Testsuite 1: GpgOL basic crypto tests
1.1 OpenPGP/MIME
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
Importing the correct certificates into Outlook ain't very nice. I had serveral problems verifying the correctnes of the created SMIME 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 recieve SMIME crypted and signed messages.