Size: 13567
Comment: used "beta 85" for testing, not "beta 84"
|
Size: 14617
Comment: Updated gpgol test plan (still in progress)
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
= GpgOL test plan | = GpgOL Test Plan **Status: in progress** |
Line 7: | Line 9: |
== What should be tested? We want to ensure GpgOL works well on all supported Microsoft Windows operating systems with all supported versions of Microsoft Outlook. The tests refer to the signing and encrypting process in Microsoft Outlook using GpgOL, the transmission of encrypted and/or signed emails, and the receiving of encrypted and/or signed emails. The tests are not only performed with messages from and to Microsoft Outlook, but also with other Windows and Linux mail clients which are supported by GnuPG, especially: * Microsoft Outlook 2010 32bit (on Windows 7 64bit) * Microsoft Outlook 2013 64bit (on Windows 8 64bit) * Microsoft Outlook 2016 32bit (on Windows 7 32bit) * Microsoft Outlook 2016 64bit (on Windows 8 64bit) * Microsoft Outlook 2016 64bit (on Windows 10 64bit) * Thunderbird with Enigmail-Add-On (on Windows or GNU/Linux) * KMail of Kontact enterprise 35 (on GNU/Linux) The tests will refer to the usage of PGP/~MIME and no-MIME-PGP. To test out the different versions of Microsoft Outlook on different platforms and CPU-Architectures a virtual test environment was recommenended, e.g. [[https://www.virtualbox.org/|VirtualBox]]. == Test plan Check if GpgOL can perform the following test suites without errors. === 1. Outlook <--> Outlook Send crypto emails between Outlook (GpgOL) and Outlook (GpgOL). ==== 1.1 Using PGP/MIME a) sign -> verify\\ b) encrypt -> decrypt\\ c) sign/encrypt with attachment -> decrypt/verify and check attachment ==== 1.2 Using S/MIME a) sign -> verify\\ b) encrypt -> decrypt\\ c) sign/encrypt with attachment -> decrypt/verify and check attachment === 2. KMail <--> Outlook Send crypto emails between KMail and Outlook (GpgOL). ==== 2.1 Using PGP/MIME |
== Introduction The purpose of this test plan is to ensure GpgOL works well on all supported Microsoft Windows operating systems with all supported versions of Microsoft Outlook. == Test environment Choose one combination of the following target platforms supported by GpgOL. Microsoft Outlook: * 2003 (32bit) * 2007 (32bit) * 2010 (32 or 64bit) * 2013 (32 or 64bit) * 2016 (32 or 64bit) Operation system: * Windows Vista (32 or 64bit) * Windows 7 (32 or 64bit) * Windows 8 (32 or 64bit) * Windows 10 (32 or 64bit) For interoperability tests additional mail clients will be tested together with Outlook/GpgOL: * Thunderbird with Enigmail-Add-On (on Windows, MacOS or GNU/Linux) * Apple Mail with GPGTools (on MacOS) * Kontact Mail (KMail) enterprise 35 (on GNU/Linux) * Kontact Mail (KMail) of KDE 4.14 (on GNU/Linux) It is recommended to use a clean virtual test environment, e.g. with [[https://www.virtualbox.org/|VirtualBox]]. == Preconditions * email account A on IMAP/SMTP server * email account B on Exchange Server 2013 or later * ~OpenPGP public key (*.asc or *.gpg) and private key (*.asc or *.gpg) * S/~M~I~M~E certificate chain (*.pem) and private key (*.p12) == Tests === Testsuite 1: GpgOL basic crypto tests Send crypto mails from/to same Outlook account. ==== 1.1 PGP/MIME Send mails with P~G~P/~M~I~M~E:\\ a) sign and verify\\ b) encrypt and decrypt\\ c) sign/encrypt (with attachment*) and decrypt/verify (and check attachment) ==== 1.2 S/MIME Send mails with S/~M~I~M~E:\\ a) sign and verify\\ b) encrypt and decrypt\\ c) sign/encrypt (with attachment*) and decrypt/verify (and check attachment) (*) Attachment should contain umlauts in filename (e.g. fooäüö.txt) === Testsuite 2: GpgOL extended tests ==== 2.1 Exchange Server Run all tests from testsuite 1 via Exchange Server. ==== 2.2 Move Mails Move some encrypted mails from inbox into an other folder. Check with an other IMAP client that all mails are always encrypted. ==== 2.3 Drafts Create new message. Mark message with "sign" and "encrypt". Close and save mail as draft. Open draft again. Check if the message is still marked with "sign" and "encrypt". ==== 2.4 Cancel crypto operation Create a mew message. Mark as sign/encrypt. Click send. Cancel certificate selection dialog. Check if the message is not sent. ==== 2.5 Sent messages Send a signed/encrypted message. Check the sent folder ("Sent messages") if the mail is still signed/encrypted. ==== 2.6 Reply Reply to an encrypted mail. Check if the quoted text contains the decrypted message. ==== 2.7 Disable GpgOL Disable the GpgOL plugin in Outlook (via COM add-ons). Select a signed/encrypted mail. Check that the mail cannot decrypted/verify. ==== 2.8 Deactivate GpgOL's S/MIME (GpgSM) TODO === Testsuite 3. Interoperability tests (Kontact Mail) Send crypto mails from Kontact Mail (KMail) to Outlook (GpgOL). ==== 3.1 Using PGP/MIME |
Line 56: | Line 106: |
==== 2.2 Using S/MIME | ==== 3.2 Using S/MIME |
Line 64: | Line 114: |
==== 2.3 Using no-mime-PGP | ==== 3.3 Using no-mime-PGP |
Line 70: | Line 120: |
=== 3. Thunderbird <--> Outlook Send crypto emails between Thunderbird (Enigmail) and Outlook (GpgOL). ==== 3.1 Using PGP/MIME |
=== Testsuite 4. Interoperability tests (Thunderbird) Send crypto mails from Thunderbird (Enigmail) to Outlook (GpgOL). ==== 4.1 Using PGP/MIME |
Line 81: | Line 132: |
==== 3.2 Using S/MIME (with Thunderbird's S/MIME implementation) | ==== 4.2 Using S/MIME (with Thunderbird's S/MIME implementation) |
Line 89: | Line 140: |
==== 3.3 Using no-mime-PGP | ==== 4.3 Using no-mime-PGP |
Line 93: | Line 144: |
Line 113: | Line 165: |
|Testsuite 2: KMail/OL | |2.1.a | ? | ? | ? | ? | ? | .. | |2.1.b | ? | ? | ? | ? | ? | .. | |2.1.c | ? | ? | ? | ? | ? | .. | |2.1.d | ? | ? | ? | ? | ? | .. | |2.1.e | ? | ? | ? | ? | ? | .. | |2.1.f | ? | ? | ? | ? | ? | .. | |2.2.a | ? | ? | ? | ? | ? | .. | |2.2.b | ? | ? | ? | ? | ? | .. | |2.2.c | ? | ? | ? | ? | ? | .. | |2.2.d | ? | ? | ? | ? | ? | .. | |2.2.e | ? | ? | ? | ? | ? | .. | |2.2.f | ? | ? | ? | ? | ? | .. | |2.3.a | ? | ? | ? | ? | ? | .. | |2.3.b | ? | ? | ? | ? | ? | .. | |2.3.c | ? | ? | ? | ? | ? | .. | |Testsuite 3: Thunderbird/OL | |3.1.a | ? | ? | ? | ? | ? | .. | |3.1.b | ? | ? | ? | ? | ? | .. | |3.1.c | ? | ? | ? | ? | ? | .. | |3.1.d | ? | ? | ? | ? | ? | .. | |3.1.e | ? | ? | ? | ? | ? | .. | |3.1.f | ? | ? | ? | ? | ? | .. | |3.2.a | ? | ? | ? | ? | ? | .. | |3.2.b | ? | ? | ? | ? | ? | .. | |3.2.c | ? | ? | ? | ? | ? | .. | |3.2.d | ? | ? | ? | ? | ? | .. | |3.2.e | ? | ? | ? | ? | ? | .. | |3.2.f | ? | ? | ? | ? | ? | .. | |3.3.a | ? | ? | ? | ? | ? | .. | |3.3.b | ? | ? | ? | ? | ? | .. | |3.3.c | ? | ? | ? | ? | ? | .. | ---- == Test results for GpgOL 1.3.0-beta85 (2015-11-04) using Gpg4win-2.2.6 under Windows 7 32bit with Outlook 2016 32bit ==== 1.1.a (sign and verify Using PGP/MIME) Signing an E-Mail with OpenPGP and sending it worked without a noticeable problem. Receiving an signed E-Mail and read it worked without a problem. To verify the received E-Mail, it was necessary to open it (The E-Mail) in an external window (double click) and navigate to the GpgOL-tab afterwards, which is inconvenient. It was not possible to verify the E-Mail inside the Outlook-Main-Window (missing option). Expected: * The E-Mail may be verified automatically * The E-Mail may be verified from inside the main window (GpgOL-tab) Result: * Successful verification from an external window ==== 1.1.b (encrypt and decrypt Using PGP/MIME) Encrypting an E-Mail with OpenPGP and sending it worked without a noticeable problem. Receiving an encrypted E-Mail worked without a problem. Once clicked on an encrypted E-Mail, Kleopatra pops-up automatically and notified about the decryption. It is necessary to close the popped-up window manually. Expected: * decryption of the encrypted mail automatically. Result: * decryption of the encrypted mail automatically (there was a suddenly appearing Kleopatra-window which needed attention, which is slightly inconvenient) ==== 1.1.c (sign/encrypt and decrypt/verify using PGP/MIME) Sign an E-Mail and encrypt it afterwards (using PGP/MIME). * No noticeable problems when sending the E-Mail * The decryption works as expected. * The verification does not seem to work: After clicking on "verify" Kleopatra mentions that the decryption was successful, but does not react to the verification-request Expected: * The Program always Signs and Encrypts in the correct order * The encryption process works similar to 1.1.b * The verification process works similar to 1.1.a Result: * behavior depends on the order of actions. Can work when choosing the options in the right order, but Kleopatra will inform about errors. The attachment was not encrypted. ==== 1.2.a (sign and verify Using S/MIME) (like in 1.1.a) Signing an E-mail with S/MIME and sending it worked without a noticeable problem. Receiving a signed E-Mail and reading it worked without a noticeable problem. The process of verifying failed. The error message was "Decryption failed: no data" (sic: (German) "Entschlüsseln fehlgeschlagen: Keine Daten.") The detailed error decryption was "input error: unknown error" (sic: (German) "Eingabefehler: Unbekannter fehler"). Expected: * The E-Mail may be verified successful. * The E-Mail may be verified from inside the main window (GpgOL-tab) Result: * The verification failed. Error message: "Decryption failed: no data" | "input error: unknown error" noticed: * After clicking on "sign" pinentry pops up. After entering the password, the E-Mail-window will vanish behind the main-window. ==== 1.2.b (encrypt and decrypt Using S/MIME) Encrypting an E-Mail with S/MIME and sending it worked without a noticeable problem. Receiving an encrypted E-Mail worked without a problem. Once clicked on an encrypted E-Mail, Outlook will display the encrypted text. It was necessary to open the E-Mail in an external window, navigating to the GpgOL tab and hitting "decrypt". The decrytion process itself worked without a problem. Expected: * decryption of the encrypted mail automatically. Result: * Outlook displayed the encrypted text. * Decryption worked after manual navigating to according options in the GpgOL-tab on an external window. ==== 1.2.c (sign/encrypt, and decrypt/verify using S/MIME) * Signing and encrypting the E-Mail works without errors. * Decryption works like in 1.2.b * Verification fails like in 1.2.a The attachment was not encrypted. Expected: * Similar behavior to 1.2.a and 1.2.b * As mentioned in 1.1.c, the program is expected to sign and encrypt in the correct order. Result: * Similar behavior to 1.2.a and 1.2.b ==== 2.1.a (Sign in KMail, Verify in Outlook, PGP/MIME) Imported the required certificate (B) on gpg on Linux using "gpg2 --import" and verified it using "gpg2 --edit-key <key>" and "trust". Set up a new E-Mail Account in KMail e35 and added the openPGP-Key in the Identity section. Signed an E-Mail using the according option on KMail and send them to the outlook client. Signing and sending worked without problems. Receiving and verifying the E-Mail worked without a problem. The verification process started immediately after clicking on the E-Mail. The verification was also repeatable using the way described in 1.1.a. Expected: * Automatic verification once clicked the E-Mail Result: * Automatic verification once clicked the E-Mail (Kleopatra still seems to be //in the way//) * Manual verification is also possible ==== 2.1.b (Sign in KMail, Verify in Outlook, PGP/MIME) Imported the required certificate on gpg on Linux using "gpg2 --import" and verified it using "gpg2 --edit-key <key>" and "trust" for both keys (source an target). Encrypted a new E-Mail using the according option on KMail and send them to the outlook client. Encrypting and sending worked without problems. Receiving and decrypting the E-Mail worked without a problem. The decrpting started immediately after clicking on the E-Mail, similar to the result of 1.1.b. Expected: * Automatic verification once clicked the E-Mail Result: * Automatic verification once clicked the E-Mail (Kleopatra still seems to be //in the way//) === Test matrix for 1.3-beta85 Legend:\\ ? = untested\\ x = passed\\ F = failed ** +++ Tested ~GpgOL version: 1.3.0-beta85 (2015-11-04) +++** |Outlook |=2010 (32) |= 2013 (64) |=2016 (32) |= 2016 (64) |= 2016 (64) |= .. |Windows |=7 (64) |= 8 (64) |=7 (32) |= 8 (64) |= 10 (64) |= .. |Testsuite 1: OL/OL | |1.1.a | ? | ? | x¹ | ? | ? | .. | |1.1.b | ? | ? | x² | ? | ? | .. | |1.1.c | ? | ? | F³ | ? | ? | .. | |1.2.a | ? | ? | F | ? | ? | .. | |1.2.b | ? | ? | x¹ | ? | ? | .. | |1.2.c | ? | ? | F | ? | ? | .. | |
|
Line 146: | Line 403: |
---- == Test results for GpgOL 1.3.0-beta85 (2015-11-04) using Gpg4win-2.2.6 under Windows 7 32bit with Outlook 2016 32bit ==== 1.1.a (sign and verify Using PGP/MIME) Signing an E-Mail with OpenPGP and sending it worked without a noticeable problem. Receiving an signed E-Mail and read it worked without a problem. To verify the received E-Mail, it was necessary to open it (The E-Mail) in an external window (double click) and navigate to the GpgOL-tab afterwards, which is inconvenient. It was not possible to verify the E-Mail inside the Outlook-Main-Window (missing option). Expected: * The E-Mail may be verified automatically * The E-Mail may be verified from inside the main window (GpgOL-tab) Result: * Successful verification from an external window ==== 1.1.b (encrypt and decrypt Using PGP/MIME) Encrypting an E-Mail with OpenPGP and sending it worked without a noticeable problem. Receiving an encrypted E-Mail worked without a problem. Once clicked on an encrypted E-Mail, Kleopatra pops-up automatically and notified about the decryption. It is necessary to close the popped-up window manually. Expected: * decryption of the encrypted mail automatically. Result: * decryption of the encrypted mail automatically (there was a suddenly appearing Kleopatra-window which needed attention, which is slightly inconvenient) ==== 1.1.c (sign/encrypt and decrypt/verify using PGP/MIME) Sign an E-Mail and encrypt it afterwards (using PGP/MIME). * No noticeable problems when sending the E-Mail * The decryption works as expected. * The verification does not seem to work: After clicking on "verify" Kleopatra mentions that the decryption was successful, but does not react to the verification-request Expected: * The Program always Signs and Encrypts in the correct order * The encryption process works similar to 1.1.b * The verification process works similar to 1.1.a Result: * behavior depends on the order of actions. Can work when choosing the options in the right order, but Kleopatra will inform about errors. The attachment was not encrypted. ==== 1.2.a (sign and verify Using S/MIME) (like in 1.1.a) Signing an E-mail with S/MIME and sending it worked without a noticeable problem. Receiving a signed E-Mail and reading it worked without a noticeable problem. The process of verifying failed. The error message was "Decryption failed: no data" (sic: (German) "Entschlüsseln fehlgeschlagen: Keine Daten.") The detailed error decryption was "input error: unknown error" (sic: (German) "Eingabefehler: Unbekannter fehler"). Expected: * The E-Mail may be verified successful. * The E-Mail may be verified from inside the main window (GpgOL-tab) Result: * The verification failed. Error message: "Decryption failed: no data" | "input error: unknown error" noticed: * After clicking on "sign" pinentry pops up. After entering the password, the E-Mail-window will vanish behind the main-window. ==== 1.2.b (encrypt and decrypt Using S/MIME) Encrypting an E-Mail with S/MIME and sending it worked without a noticeable problem. Receiving an encrypted E-Mail worked without a problem. Once clicked on an encrypted E-Mail, Outlook will display the encrypted text. It was necessary to open the E-Mail in an external window, navigating to the GpgOL tab and hitting "decrypt". The decrytion process itself worked without a problem. Expected: * decryption of the encrypted mail automatically. Result: * Outlook displayed the encrypted text. * Decryption worked after manual navigating to according options in the GpgOL-tab on an external window. ==== 1.2.c (sign/encrypt, and decrypt/verify using S/MIME) * Signing and encrypting the E-Mail works without errors. * Decryption works like in 1.2.b * Verification fails like in 1.2.a The attachment was not encrypted. Expected: * Similar behavior to 1.2.a and 1.2.b * As mentioned in 1.1.c, the program is expected to sign and encrypt in the correct order. Result: * Similar behavior to 1.2.a and 1.2.b ==== 2.1.a (Sign in KMail, Verify in Outlook, PGP/MIME) Imported the required certificate (B) on gpg on Linux using "gpg2 --import" and verified it using "gpg2 --edit-key <key>" and "trust". Set up a new E-Mail Account in KMail e35 and added the openPGP-Key in the Identity section. Signed an E-Mail using the according option on KMail and send them to the outlook client. Signing and sending worked without problems. Receiving and verifying the E-Mail worked without a problem. The verification process started immediately after clicking on the E-Mail. The verification was also repeatable using the way described in 1.1.a. Expected: * Automatic verification once clicked the E-Mail Result: * Automatic verification once clicked the E-Mail (Kleopatra still seems to be //in the way//) * Manual verification is also possible ==== 2.1.b (Sign in KMail, Verify in Outlook, PGP/MIME) Imported the required certificate on gpg on Linux using "gpg2 --import" and verified it using "gpg2 --edit-key <key>" and "trust" for both keys (source an target). Encrypted a new E-Mail using the according option on KMail and send them to the outlook client. Encrypting and sending worked without problems. Receiving and decrypting the E-Mail worked without a problem. The decrpting started immediately after clicking on the E-Mail, similar to the result of 1.1.b. Expected: * Automatic verification once clicked the E-Mail Result: * Automatic verification once clicked the E-Mail (Kleopatra still seems to be //in the way//) === Test matrix for 1.3-beta84 Legend:\\ ? = untested\\ x = passed\\ F = failed ** +++ Tested ~GpgOL version: 1.3.0-beta84 (2015-11-04) +++** |Outlook |=2010 (32) |= 2013 (64) |=2016 (32) |= 2016 (64) |= 2016 (64) |= .. |Windows |=7 (64) |= 8 (64) |=7 (32) |= 8 (64) |= 10 (64) |= .. |Testsuite 1: OL/OL | |1.1.a | ? | ? | x¹ | ? | ? | .. | |1.1.b | ? | ? | x² | ? | ? | .. | |1.1.c | ? | ? | F³ | ? | ? | .. | |1.1.d⁰ | ? | ? | ? | ? | ? | .. | |1.1.e⁰ | ? | ? | ? | ? | ? | .. | |1.1.f⁰ | ? | ? | ? | ? | ? | .. | |1.2.a | ? | ? | F | ? | ? | .. | |1.2.b | ? | ? | x¹ | ? | ? | .. | |1.2.c | ? | ? | F | ? | ? | .. | |1.2.d⁰ | ? | ? | ? | ? | ? | .. | |1.2.e⁰ | ? | ? | ? | ? | ? | .. | |1.2.f⁰ | ? | ? | ? | ? | ? | .. | |Testsuite 2: KMail/OL | |2.1.a | ? | ? | x | ? | ? | .. | |2.1.b | ? | ? | x | ? | ? | .. | |2.1.c | ? | ? | ? | ? | ? | .. | |2.1.d | ? | ? | ? | ? | ? | .. | |2.1.e | ? | ? | ? | ? | ? | .. | |2.1.f | ? | ? | ? | ? | ? | .. | |2.2.a | ? | ? | ? | ? | ? | .. | |2.2.b | ? | ? | ? | ? | ? | .. | |2.2.c | ? | ? | ? | ? | ? | .. | |2.2.d | ? | ? | ? | ? | ? | .. | |2.2.e | ? | ? | ? | ? | ? | .. | |2.2.f | ? | ? | ? | ? | ? | .. | |2.3.a | ? | ? | ? | ? | ? | .. | |2.3.b | ? | ? | ? | ? | ? | .. | |2.3.c | ? | ? | ? | ? | ? | .. | |Testsuite 3: Thunderbird/OL | |3.1.a | ? | ? | ? | ? | ? | .. | |3.1.b | ? | ? | ? | ? | ? | .. | |3.1.c | ? | ? | ? | ? | ? | .. | |3.1.d | ? | ? | ? | ? | ? | .. | |3.1.e | ? | ? | ? | ? | ? | .. | |3.1.f | ? | ? | ? | ? | ? | .. | |3.2.a | ? | ? | ? | ? | ? | .. | |3.2.b | ? | ? | ? | ? | ? | .. | |3.2.c | ? | ? | ? | ? | ? | .. | |3.2.d | ? | ? | ? | ? | ? | .. | |3.2.e | ? | ? | ? | ? | ? | .. | |3.2.f | ? | ? | ? | ? | ? | .. | |3.3.a | ? | ? | ? | ? | ? | .. | |3.3.b | ? | ? | ? | ? | ? | .. | |3.3.c | ? | ? | ? | ? | ? | .. | |
GpgOL Test Plan
Status: in progress
Here you can find information about the manual testing progress of GpgOL.
Contents
Introduction
The purpose of this test plan is to ensure GpgOL works well on all supported Microsoft Windows operating systems with all supported versions of Microsoft Outlook.
Test environment
Choose one combination of the following target platforms supported by GpgOL.
Microsoft Outlook:
- 2003 (32bit)
- 2007 (32bit)
- 2010 (32 or 64bit)
- 2013 (32 or 64bit)
- 2016 (32 or 64bit)
Operation system:
- Windows Vista (32 or 64bit)
- Windows 7 (32 or 64bit)
- Windows 8 (32 or 64bit)
- Windows 10 (32 or 64bit)
For interoperability tests additional mail clients will be tested together with Outlook/GpgOL:
- Thunderbird with Enigmail-Add-On (on Windows, MacOS or GNU/Linux)
- Apple Mail with GPGTools (on MacOS)
- Kontact Mail (KMail) enterprise 35 (on GNU/Linux)
- Kontact Mail (KMail) of KDE 4.14 (on GNU/Linux)
It is recommended to use a clean virtual test environment, e.g. with VirtualBox.
Preconditions
- email account A on IMAP/SMTP server
- email account B on Exchange Server 2013 or later
- OpenPGP public key (*.asc or *.gpg) and private key (*.asc or *.gpg)
- S/MIME certificate chain (*.pem) and private key (*.p12)
Tests
Testsuite 1: GpgOL basic crypto tests
Send crypto mails from/to same Outlook account.
1.1 PGP/MIME
Send mails with PGP/MIME:
a) sign and verify
b) encrypt and decrypt
c) sign/encrypt (with attachment*) and decrypt/verify (and check attachment)
1.2 S/MIME
Send mails with S/MIME:
a) sign and verify
b) encrypt and decrypt
c) sign/encrypt (with attachment*) and decrypt/verify (and check attachment)
(*) Attachment should contain umlauts in filename (e.g. fooäüö.txt)
Testsuite 2: GpgOL extended tests
2.1 Exchange Server
Run all tests from testsuite 1 via Exchange Server.
2.2 Move Mails
Move some encrypted mails from inbox into an other folder. Check with an other IMAP client that all mails are always encrypted.
2.3 Drafts
Create new message. Mark message with "sign" and "encrypt". Close and save mail as draft. Open draft again. Check if the message is still marked with "sign" and "encrypt".
2.4 Cancel crypto operation
Create a mew message. Mark as sign/encrypt. Click send. Cancel certificate selection dialog. Check if the message is not sent.
2.5 Sent messages
Send a signed/encrypted message. Check the sent folder ("Sent messages") if the mail is still signed/encrypted.
2.6 Reply
Reply to an encrypted mail. Check if the quoted text contains the decrypted message.
2.7 Disable GpgOL
Disable the GpgOL plugin in Outlook (via COM add-ons). Select a signed/encrypted mail. Check that the mail cannot decrypted/verify.
2.8 Deactivate GpgOL's S/MIME (GpgSM)
Testsuite 3. Interoperability tests (Kontact Mail)
Send crypto mails from Kontact Mail (KMail) to Outlook (GpgOL).
3.1 Using PGP/MIME
a) sign (KMail) -> verify (GpgOL)
b) encrypt (KMail) -> decrypt (GpgOL)
c) sign/encrypt with attachment (KMail) -> decrypt/verify and check attachment (GpgOL)
d) answer to (a): sign (GpgOL) -> verify (KMail)
e) answer to (b): encrypt (GpgOL) -> decrypt (KMail)
f) answer to (c): sign/encrypt with attachment (GpgOL) -> decrypt/verify and check attachment (KMail)
3.2 Using S/MIME
a) sign (KMail) -> verify (GpgOL)
b) encrypt (KMail) -> decrypt (GpgOL)
c) sign/encrypt with attachment (KMail) -> decrypt/verify and check attachment (GpgOL)
d) answer to (a): sign (GpgOL) -> verify (KMail)
e) answer to (b): encrypt (GpgOL) -> decrypt (KMail)
f) answer to (c): sign/encrypt with attachment (GpgOL) -> decrypt/verify and check attachment (KMail)
3.3 Using no-mime-PGP
a) sign (KMail) -> verify (GpgOL)
b) encrypt (KMail) -> decrypt (GpgOL)
c) sign/encrypt without attachment (KMail) -> decrypt/verify (GpgOL)
Testsuite 4. Interoperability tests (Thunderbird)
Send crypto mails from Thunderbird (Enigmail) to Outlook (GpgOL).
4.1 Using PGP/MIME
a) sign (TB) -> verify (GpgOL)
b) encrypt (TB) -> decrypt (GpgOL)
c) sign/encrypt with attachment (TB) -> decrypt/verify and check attachment (GpgOL)
d) answer to (a): sign (GpgOL) -> verify (TB)
e) answer to (b): encrypt (GpgOL) -> decrypt (TB)
f) answer to (c): sign/encrypt with attachment (GpgOL) -> decrypt/verify and check attachment (TB)
4.2 Using S/MIME (with Thunderbird's S/MIME implementation)
a) sign (TB) -> verify (GpgOL)
b) encrypt (TB) -> decrypt (GpgOL)
c) sign/encrypt with attachment (TB) -> decrypt/verify and check attachment (GpgOL)
d) answer to (a): sign (GpgOL) -> verify (TB)
e) answer to (b): encrypt (GpgOL) -> decrypt (TB)
f) answer to (c): sign/encrypt with attachment (GpgOL) -> decrypt/verify and check attachment (TB)
4.3 Using no-mime-PGP
a) sign (TB) -> verify (GpgOL)
b) encrypt (TB) -> decrypt (GpgOL)
c) sign/encrypt with attachment (TB) -> decrypt/verify and check attachment (GpgOL)
Test matrix
Legend:
? = untested
x = passed
F = failed
+++ Tested GpgOL version: X.X.X +++
Outlook | 2010 (32) | 2013 (64) | 2016 (32) | 2016 (64) | 2016 (64) | .. |
---|---|---|---|---|---|---|
Windows | 7 (64) | 8 (64) | 7 (32) | 8 (64) | 10 (64) | .. |
Testsuite 1: OL/OL | ||||||
1.1.a | ? | ? | ? | ? | ? | .. |
1.1.b | ? | ? | ? | ? | ? | .. |
1.1.c | ? | ? | ? | ? | ? | .. |
1.2.a | ? | ? | ? | ? | ? | .. |
1.2.b | ? | ? | ? | ? | ? | .. |
1.2.c | ? | ? | ? | ? | ? | .. |
Testsuite 2: KMail/OL | ||||||
2.1.a | ? | ? | ? | ? | ? | .. |
2.1.b | ? | ? | ? | ? | ? | .. |
2.1.c | ? | ? | ? | ? | ? | .. |
2.1.d | ? | ? | ? | ? | ? | .. |
2.1.e | ? | ? | ? | ? | ? | .. |
2.1.f | ? | ? | ? | ? | ? | .. |
2.2.a | ? | ? | ? | ? | ? | .. |
2.2.b | ? | ? | ? | ? | ? | .. |
2.2.c | ? | ? | ? | ? | ? | .. |
2.2.d | ? | ? | ? | ? | ? | .. |
2.2.e | ? | ? | ? | ? | ? | .. |
2.2.f | ? | ? | ? | ? | ? | .. |
2.3.a | ? | ? | ? | ? | ? | .. |
2.3.b | ? | ? | ? | ? | ? | .. |
2.3.c | ? | ? | ? | ? | ? | .. |
Testsuite 3: Thunderbird/OL | ||||||
3.1.a | ? | ? | ? | ? | ? | .. |
3.1.b | ? | ? | ? | ? | ? | .. |
3.1.c | ? | ? | ? | ? | ? | .. |
3.1.d | ? | ? | ? | ? | ? | .. |
3.1.e | ? | ? | ? | ? | ? | .. |
3.1.f | ? | ? | ? | ? | ? | .. |
3.2.a | ? | ? | ? | ? | ? | .. |
3.2.b | ? | ? | ? | ? | ? | .. |
3.2.c | ? | ? | ? | ? | ? | .. |
3.2.d | ? | ? | ? | ? | ? | .. |
3.2.e | ? | ? | ? | ? | ? | .. |
3.2.f | ? | ? | ? | ? | ? | .. |
3.3.a | ? | ? | ? | ? | ? | .. |
3.3.b | ? | ? | ? | ? | ? | .. |
3.3.c | ? | ? | ? | ? | ? | .. |
Test results for GpgOL 1.3.0-beta85 (2015-11-04)
using Gpg4win-2.2.6 under Windows 7 32bit with Outlook 2016 32bit
1.1.a (sign and verify Using PGP/MIME)
Signing an E-Mail with OpenPGP and sending it worked without a noticeable problem.
Receiving an signed E-Mail and read it worked without a problem.
To verify the received E-Mail, it was necessary to open it (The E-Mail) in an external window (double click) and navigate to the GpgOL-tab afterwards, which is inconvenient. It was not possible to verify the E-Mail inside the Outlook-Main-Window (missing option).
Expected:
- The E-Mail may be verified automatically
- The E-Mail may be verified from inside the main window (GpgOL-tab)
Result:
- Successful verification from an external window
1.1.b (encrypt and decrypt Using PGP/MIME)
Encrypting an E-Mail with OpenPGP and sending it worked without a noticeable problem.
Receiving an encrypted E-Mail worked without a problem.
Once clicked on an encrypted E-Mail, Kleopatra pops-up automatically and notified about the decryption.
It is necessary to close the popped-up window manually.
Expected:
- decryption of the encrypted mail automatically.
Result:
- decryption of the encrypted mail automatically (there was a suddenly appearing Kleopatra-window which needed attention, which is slightly inconvenient)
1.1.c (sign/encrypt and decrypt/verify using PGP/MIME)
Sign an E-Mail and encrypt it afterwards (using PGP/MIME).
- No noticeable problems when sending the E-Mail
- The decryption works as expected.
- The verification does not seem to work: After clicking on "verify" Kleopatra mentions that the decryption was successful, but does not react to the verification-request
Expected:
- The Program always Signs and Encrypts in the correct order
- The encryption process works similar to 1.1.b
- The verification process works similar to 1.1.a
Result:
- behavior depends on the order of actions. Can work when choosing the options in the right order, but Kleopatra will inform about errors.
The attachment was not encrypted.
1.2.a (sign and verify Using S/MIME)
(like in 1.1.a) Signing an E-mail with S/MIME and sending it worked without a noticeable problem.
Receiving a signed E-Mail and reading it worked without a noticeable problem.
The process of verifying failed. The error message was "Decryption failed: no data" (sic: (German) "Entschlüsseln fehlgeschlagen: Keine Daten.") The detailed error decryption was "input error: unknown error" (sic: (German) "Eingabefehler: Unbekannter fehler").
Expected:
- The E-Mail may be verified successful.
- The E-Mail may be verified from inside the main window (GpgOL-tab)
Result:
- The verification failed. Error message: "Decryption failed: no data" | "input error: unknown error"
noticed:
- After clicking on "sign" pinentry pops up. After entering the password, the E-Mail-window will vanish behind the main-window.
1.2.b (encrypt and decrypt Using S/MIME)
Encrypting an E-Mail with S/MIME and sending it worked without a noticeable problem.
Receiving an encrypted E-Mail worked without a problem.
Once clicked on an encrypted E-Mail, Outlook will display the encrypted text. It was necessary to open the E-Mail in an external window, navigating to the GpgOL tab and hitting "decrypt". The decrytion process itself worked without a problem.
Expected:
- decryption of the encrypted mail automatically.
Result:
- Outlook displayed the encrypted text.
- Decryption worked after manual navigating to according options in the GpgOL-tab on an external window.
1.2.c (sign/encrypt, and decrypt/verify using S/MIME)
- Signing and encrypting the E-Mail works without errors.
- Decryption works like in 1.2.b
- Verification fails like in 1.2.a
The attachment was not encrypted.
Expected:
- Similar behavior to 1.2.a and 1.2.b
- As mentioned in 1.1.c, the program is expected to sign and encrypt in the correct order.
Result:
- Similar behavior to 1.2.a and 1.2.b
2.1.a (Sign in KMail, Verify in Outlook, PGP/MIME)
Imported the required certificate (B) on gpg on Linux using "gpg2 --import" and verified it using "gpg2 --edit-key <key>" and "trust".
Set up a new E-Mail Account in KMail e35 and added the openPGP-Key in the Identity section.
Signed an E-Mail using the according option on KMail and send them to the outlook client.
Signing and sending worked without problems. Receiving and verifying the E-Mail worked without a problem.
The verification process started immediately after clicking on the E-Mail. The verification was also repeatable using the way described in 1.1.a.
Expected:
- Automatic verification once clicked the E-Mail
Result:
- Automatic verification once clicked the E-Mail (Kleopatra still seems to be in the way)
- Manual verification is also possible
2.1.b (Sign in KMail, Verify in Outlook, PGP/MIME)
Imported the required certificate on gpg on Linux using "gpg2 --import" and verified it using "gpg2 --edit-key <key>" and "trust" for both keys (source an target).
Encrypted a new E-Mail using the according option on KMail and send them to the outlook client.
Encrypting and sending worked without problems. Receiving and decrypting the E-Mail worked without a problem.
The decrpting started immediately after clicking on the E-Mail, similar to the result of 1.1.b.
Expected:
- Automatic verification once clicked the E-Mail
Result:
- Automatic verification once clicked the E-Mail (Kleopatra still seems to be in the way)
Test matrix for 1.3-beta85
Legend:
? = untested
x = passed
F = failed
+++ Tested GpgOL version: 1.3.0-beta85 (2015-11-04) +++
Outlook | 2010 (32) | 2013 (64) | 2016 (32) | 2016 (64) | 2016 (64) | .. |
---|---|---|---|---|---|---|
Windows | 7 (64) | 8 (64) | 7 (32) | 8 (64) | 10 (64) | .. |
Testsuite 1: OL/OL | ||||||
1.1.a | ? | ? | x¹ | ? | ? | .. |
1.1.b | ? | ? | x² | ? | ? | .. |
1.1.c | ? | ? | F³ | ? | ? | .. |
1.2.a | ? | ? | F | ? | ? | .. |
1.2.b | ? | ? | x¹ | ? | ? | .. |
1.2.c | ? | ? | F | ? | ? | .. |
Testsuite 2: KMail/OL | ||||||
2.1.a | ? | ? | x | ? | ? | .. |
2.1.b | ? | ? | x | ? | ? | .. |
2.1.c | ? | ? | ? | ? | ? | .. |
2.1.d | ? | ? | ? | ? | ? | .. |
2.1.e | ? | ? | ? | ? | ? | .. |
2.1.f | ? | ? | ? | ? | ? | .. |
2.2.a | ? | ? | ? | ? | ? | .. |
2.2.b | ? | ? | ? | ? | ? | .. |
2.2.c | ? | ? | ? | ? | ? | .. |
2.2.d | ? | ? | ? | ? | ? | .. |
2.2.e | ? | ? | ? | ? | ? | .. |
2.2.f | ? | ? | ? | ? | ? | .. |
2.3.a | ? | ? | ? | ? | ? | .. |
2.3.b | ? | ? | ? | ? | ? | .. |
2.3.c | ? | ? | ? | ? | ? | .. |
Testsuite 3: Thunderbird/OL | ||||||
3.1.a | ? | ? | ? | ? | ? | .. |
3.1.b | ? | ? | ? | ? | ? | .. |
3.1.c | ? | ? | ? | ? | ? | .. |
3.1.d | ? | ? | ? | ? | ? | .. |
3.1.e | ? | ? | ? | ? | ? | .. |
3.1.f | ? | ? | ? | ? | ? | .. |
3.2.a | ? | ? | ? | ? | ? | .. |
3.2.b | ? | ? | ? | ? | ? | .. |
3.2.c | ? | ? | ? | ? | ? | .. |
3.2.d | ? | ? | ? | ? | ? | .. |
3.2.e | ? | ? | ? | ? | ? | .. |
3.2.f | ? | ? | ? | ? | ? | .. |
3.3.a | ? | ? | ? | ? | ? | .. |
3.3.b | ? | ? | ? | ? | ? | .. |
3.3.c | ? | ? | ? | ? | ? | .. |
- ⁰) Currently no Entry in the test plan
- ¹) To verify and decrypt an email, it is necessary to open it in an external window, which is inconvenient.
- ²) Kleopatra is popping up and requires attention (which is slightly inconvenient)
- ³) Seems to work when choosing the right combination of actions, but throws errors and is susceptible for "wrong usage"