|
Size: 9661
Comment: two more test results.
|
← Revision 33 as of 2016-03-11 07:42:09 ⇥
Size: 10067
Comment: GpgOL test plan improvements
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| ## page was renamed from GpgOL/Development/Testplan = GpgOL test plan Here you can find information about the manual testing progress of GpgOL. |
= GpgOL Test Plan **Status: in progress** |
| Line 8: | Line 7: |
| == 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 PGP/Inline. 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) Operating 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 * Gpg4win 3.x (with GpgOL 1.4+) installed * 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 OpenPGP/MIME Send mails with OpenP~G~P/~M~I~M~E:\\ a) sign and verify\\ b) encrypt and decrypt\\ c) sign/encrypt (with 2 attachments, one image one non-ascii text) and decrypt/verify (and check attachments) ==== 1.2 S/MIME Send mails with S/~M~I~M~E:\\ a) sign and verify\\ b) encrypt and decrypt\\ c) sign/encrypt (with 2 attachments, one image one non-ascii text) and decrypt/verify (and check attachments) === Testsuite 2: GpgOL extended tests ==== 2.1 Exchange Server Run all tests from testsuite 1 via Exchange Server. ==== 2.2 Move mails Open an encrypted mail and move it from the 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 new 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 Disable GpgOL Open an encrypted mail. Disable the GpgOL plugin in Outlook (via COM add-ons). Check that the opened mail is not saved decrypted. Select a OpenPGP signed/encrypted mail. Check that the mail cannot decrypt/verify. ==== 2.7 Deactivate GpgOL's S/MIME (GpgSM) Open a S/~M~I~M~E sign/encrypted mail (which was signed/encrypted with GpgOL). Deactivate S/MIME in GpgOL's option dialog. Close and reopen the mail two times. Check that Outlook's S/MIME implementation can decrypt/verify this mail at least the second time. ==== 2.8 Close Outlook Open an encrypted mail. Close Outlook. When asked to save changes select "Yes". Verify with an other I~M~A~P client that no plaintext is on the server. ==== 2.9 Unknown recipient Try to encrypt a message to a unknown email address. Check that Kleopatra cannot match a suitable certificate. ==== 2.10 Cannot decrypt Send an encrypted email to yourself but select an other certificate for encryption (not the own certificate). Check that GpgOL cannot decrypt the received message and the error indicates why. ==== 2.11 Cannot sign Remove your certificate (incl. secret key). Try to sign a new message. Check that GpgOL cannot sign the message and the error indicates why. ==== 2.12 Cannot encrypt Remove your certificate (if still available). Try to encrypt a new message to yourself. Check that GpgOL cannot encrypt the message and the error indicates why. ==== 2.13 Signature with wrong address Create or import new secret key which does not match to Outlooks email address. Send a signed mail to yourself but select the new certificate for signing. Verify the signature. Check the warning that the email address not contained in the certificate. ==== 2.14 Attachments Send a signed mail (not encrypt) with 4 attachments:\\ a) filename "fooäüö.txt" (attachment name with umlauts) b) filename "tästfilename.txt" (attachment name with < 30% 8Bit encoding chars)\\ c) filename "test☃man.txt" (attachment name with < 30% Utf-16 characters)\\ d) filename "☃" (attachment name with mostly Utf-16 characters)\\ Check that the signature is valid. ==== 2.15 Forward / reply to encrypted mail Select forward or reply to an encrypted and signed mail. Is the plaintext inserted correctly? Is encrypt / sign preset to the state of the mail? ==== 2.16 Office elements Select rich text mail and insert a [[https://support.office.com/en-us/article/Create-a-SmartArt-graphic-4c36e284-2b76-400d-99d7-6cf198a33a4b|"SmartArt"]] through the insert menu. Sign & encrypt. Is an informative error shown? ==== 2.17 Inline editors In Outlook 2013 or 2016 reply to an encrypted mail in the message list. Are crypto buttons shown? Does it work? ==== 2.18 Address book recipient Add a recipient to your addressbook and select encrypt. Is the address correctly shown in certificate selection dialog? ==== 2.19 Shared folders Configure your I~M~A~P or Exchange account to have read access to a folder of another user. Put encrypted messages in there with the other user. Decrypt. Does it work? ==== 2.20 Kleopatra startup Decrypt a mail. After decryption shut down Kleopatra. Select another Mail. Is Kleopatra restarted automatically? === Testsuite 3: Interoperability tests (Outlook's built-in S/MIME) ==== 3.1 Receive S/MIME mails with GpgOL Send S/~M~I~M~E crypto mails from Outlook (with it's built-in S/MIME implementation) to an other Outlook (with GpgOL). a) sign and verify\\ b) encrypt and decrypt\\ c) sign/encrypt (with attachment) and decrypt/verify (and check attachment) ==== 3.1 Send S/MIME mails with GpgOL Send S/~M~I~M~E crypto mails from Outlook (with GpgOL) to an other Outlook (with it's built-in S/MIME implementation). a) sign and verify\\ b) encrypt and decrypt\\ c) sign/encrypt (with attachment) and decrypt/verify (and check attachment) === Testsuite 4: Interoperability tests (Kontact Mail) Send crypto mails between Kontact Mail (KMail) and Outlook (with GpgOL). ==== 4.1 OpenPGP/MIME |
| Line 57: | Line 178: |
| ==== 2.2 Using S/MIME | ==== 4.2 S/MIME |
| Line 65: | Line 186: |
| ==== 2.3 Using PGP/Inline | ==== 4.3 in-body OpenPGP |
| Line 71: | Line 192: |
| === 3. Thunderbird <--> Outlook Send crypto emails between Thunderbird (Enigmail) and Outlook (GpgOL). ==== 3.1 Using PGP/MIME |
=== Testsuite 5: Interoperability tests (Thunderbird) Send crypto mails between Thunderbird (with Enigmail) and Outlook (with GpgOL). ==== 5.1 OpenPGP/MIME |
| Line 82: | Line 204: |
| ==== 3.2 Using S/MIME (with Thunderbird's S/MIME implementation) | ==== 5.2 S/MIME (with Thunderbird's S/MIME implementation) |
| Line 90: | Line 212: |
| ==== 3.3 Using PGP/Inline | ==== 5.3 OpenPGP-in-body |
| Line 95: | Line 217: |
| == Test Results The detailed description of how the test was performed, what kind of results were expected and what the actual result was like. ==== 1.1.a (sign and verify Using PGP/MIME) ===== Windows 7 32 Outlook 2016 Using Gpg4Win version 2.2.6 and gpgol.dll beta 1.3.0-beta85 (2015-11-04). Imported two necessary certificates in Kleopatra and authenticated them manually. 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) ===== Windows 7 32 Outlook 2016 Using Gpg4Win version 2.2.6 and gpgol.dll beta 1.3.0-beta85 (2015-11-04). Imported two necessary certificates in Kleopatra and authenticated them manually. 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.2.a (sign and verify Using S/MIME) ===== Windows 7 32 Outlook 2016 Using Gpg4Win version 2.2.6 and gpgol.dll beta 1.3.0-beta85 (2015-11-04). Imported two necessary certificates in Kleopatra and authenticated them manually. (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" ==== 1.2.b (encrypt and decrypt Using S/MIME) ===== Windows 7 32 Outlook 2016 Using Gpg4Win version 2.2.6 and gpgol.dll beta 1.3.0-beta85 (2015-11-04). Imported two necessary certificates in Kleopatra and authenticated them manually. 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. == 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 | ? | ? | x¹ | ? | ? | .. | |1.1.b | ? | ? | x² | ? | ? | .. | |1.1.c | ? | ? | ? | ? | ? | .. | |1.1.d | ? | ? | ? | ? | ? | .. | |1.1.e | ? | ? | ? | ? | ? | .. | |1.1.f | ? | ? | ? | ? | ? | .. | |1.2.a | ? | ? | F | ? | ? | .. | |1.2.b | ? | ? | x¹ | ? | ? | .. | |1.2.c | ? | ? | ? | ? | ? | .. | |1.2.d | ? | ? | ? | ? | ? | .. | |1.2.e | ? | ? | ? | ? | ? | .. | |1.2.f | ? | ? | ? | ? | ? | .. | |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 | ? | ? | ? | ? | ? | .. | * ¹) 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) |
==== 5.4 OpenPGP/Partioned a) sign (TB) -> verify (GpgOL)\\ b) encrypt (TB) -> decrypt (GpgOL)\\ c) sign/encrypt with attachment (TB) -> decrypt/verify and check that you have the option to decrypt attachment (GpgOL) === Testsuite 6: Interoperability tests (GPGTools) Send crypto mails between Apple Mail (with GPG for Mail plugin from GPGTools) and Outlook (with GpgOL). ==== 6.1 OpenPGP/MIME a) sign (Apple Mail) -> verify (GpgOL)\\ b) encrypt (Apple Mail) -> decrypt (GpgOL)\\ c) sign/encrypt with attachment (Apple Mail) -> decrypt/verify and check attachment (GpgOL)\\ d) answer to (a): sign (GpgOL) -> verify (Apple Mail)\\ e) answer to (b): encrypt (GpgOL) -> decrypt (Apple Mail)\\ f) answer to (c): sign/encrypt with attachment (GpgOL) -> decrypt/verify and check attachment (Apple Mail) ==== 6.2 S/MIME a) sign (Apple Mail) -> verify (GpgOL)\\ b) encrypt (Apple Mail) -> decrypt (GpgOL)\\ c) sign/encrypt with attachment (Apple Mail) -> decrypt/verify and check attachment (GpgOL)\\ d) answer to (a): sign (GpgOL) -> verify (Apple Mail)\\ e) answer to (b): encrypt (GpgOL) -> decrypt (Apple Mail)\\ f) answer to (c): sign/encrypt with attachment (GpgOL) -> decrypt/verify and check attachment (Apple Mail) |
GpgOL Test Plan
Status: in progress
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)
Operating 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
- Gpg4win 3.x (with GpgOL 1.4+) installed
- 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 OpenPGP/MIME
Send mails with OpenPGP/MIME:
a) sign and verify
b) encrypt and decrypt
c) sign/encrypt (with 2 attachments, one image one non-ascii text) and decrypt/verify (and check attachments)
1.2 S/MIME
Send mails with S/MIME:
a) sign and verify
b) encrypt and decrypt
c) sign/encrypt (with 2 attachments, one image one non-ascii text) and decrypt/verify (and check attachments)
Testsuite 2: GpgOL extended tests
2.1 Exchange Server
Run all tests from testsuite 1 via Exchange Server.
2.2 Move mails
Open an encrypted mail and move it from the 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 new 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 Disable GpgOL
Open an encrypted mail. Disable the GpgOL plugin in Outlook (via COM add-ons). Check that the opened mail is not saved decrypted. Select a OpenPGP signed/encrypted mail. Check that the mail cannot decrypt/verify.
2.7 Deactivate GpgOL's S/MIME (GpgSM)
Open a S/MIME sign/encrypted mail (which was signed/encrypted with GpgOL). Deactivate S/MIME in GpgOL's option dialog. Close and reopen the mail two times. Check that Outlook's S/MIME implementation can decrypt/verify this mail at least the second time.
2.8 Close Outlook
Open an encrypted mail. Close Outlook. When asked to save changes select "Yes". Verify with an other IMAP client that no plaintext is on the server.
2.9 Unknown recipient
Try to encrypt a message to a unknown email address. Check that Kleopatra cannot match a suitable certificate.
2.10 Cannot decrypt
Send an encrypted email to yourself but select an other certificate for encryption (not the own certificate). Check that GpgOL cannot decrypt the received message and the error indicates why.
2.11 Cannot sign
Remove your certificate (incl. secret key). Try to sign a new message. Check that GpgOL cannot sign the message and the error indicates why.
2.12 Cannot encrypt
Remove your certificate (if still available). Try to encrypt a new message to yourself. Check that GpgOL cannot encrypt the message and the error indicates why.
2.13 Signature with wrong address
Create or import new secret key which does not match to Outlooks email address. Send a signed mail to yourself but select the new certificate for signing. Verify the signature. Check the warning that the email address not contained in the certificate.
2.14 Attachments
Send a signed mail (not encrypt) with 4 attachments:
a) filename "fooäüö.txt" (attachment name with umlauts) b) filename "tästfilename.txt" (attachment name with < 30% 8Bit encoding chars)
c) filename "test☃man.txt" (attachment name with < 30% Utf-16 characters)
d) filename "☃" (attachment name with mostly Utf-16 characters)
Check that the signature is valid.
2.15 Forward / reply to encrypted mail
Select forward or reply to an encrypted and signed mail. Is the plaintext inserted correctly? Is encrypt / sign preset to the state of the mail?
2.16 Office elements
Select rich text mail and insert a "SmartArt" through the insert menu. Sign & encrypt. Is an informative error shown?
2.17 Inline editors
In Outlook 2013 or 2016 reply to an encrypted mail in the message list. Are crypto buttons shown? Does it work?
2.18 Address book recipient
Add a recipient to your addressbook and select encrypt. Is the address correctly shown in certificate selection dialog?
2.19 Shared folders
Configure your IMAP or Exchange account to have read access to a folder of another user. Put encrypted messages in there with the other user. Decrypt. Does it work?
2.20 Kleopatra startup
Decrypt a mail. After decryption shut down Kleopatra. Select another Mail. Is Kleopatra restarted automatically?
Testsuite 3: Interoperability tests (Outlook's built-in S/MIME)
3.1 Receive S/MIME mails with GpgOL
Send S/MIME crypto mails from Outlook (with it's built-in S/MIME implementation) to an other Outlook (with GpgOL).
a) sign and verify
b) encrypt and decrypt
c) sign/encrypt (with attachment) and decrypt/verify (and check attachment)
3.1 Send S/MIME mails with GpgOL
Send S/MIME crypto mails from Outlook (with GpgOL) to an other Outlook (with it's built-in S/MIME implementation).
a) sign and verify
b) encrypt and decrypt
c) sign/encrypt (with attachment) and decrypt/verify (and check attachment)
Testsuite 4: Interoperability tests (Kontact Mail)
Send crypto mails between Kontact Mail (KMail) and Outlook (with GpgOL).
4.1 OpenPGP/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)
4.2 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)
4.3 in-body OpenPGP
a) sign (KMail) -> verify (GpgOL)
b) encrypt (KMail) -> decrypt (GpgOL)
c) sign/encrypt without attachment (KMail) -> decrypt/verify (GpgOL)
Testsuite 5: Interoperability tests (Thunderbird)
Send crypto mails between Thunderbird (with Enigmail) and Outlook (with GpgOL).
5.1 OpenPGP/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)
5.2 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)
5.3 OpenPGP-in-body
a) sign (TB) -> verify (GpgOL)
b) encrypt (TB) -> decrypt (GpgOL)
c) sign/encrypt with attachment (TB) -> decrypt/verify and check attachment (GpgOL)
5.4 OpenPGP/Partioned
a) sign (TB) -> verify (GpgOL)
b) encrypt (TB) -> decrypt (GpgOL)
c) sign/encrypt with attachment (TB) -> decrypt/verify and check that you have the option to decrypt attachment (GpgOL)
Testsuite 6: Interoperability tests (GPGTools)
Send crypto mails between Apple Mail (with GPG for Mail plugin from GPGTools) and Outlook (with GpgOL).
6.1 OpenPGP/MIME
a) sign (Apple Mail) -> verify (GpgOL)
b) encrypt (Apple Mail) -> decrypt (GpgOL)
c) sign/encrypt with attachment (Apple Mail) -> decrypt/verify and check attachment (GpgOL)
d) answer to (a): sign (GpgOL) -> verify (Apple Mail)
e) answer to (b): encrypt (GpgOL) -> decrypt (Apple Mail)
f) answer to (c): sign/encrypt with attachment (GpgOL) -> decrypt/verify and check attachment (Apple Mail)
6.2 S/MIME
a) sign (Apple Mail) -> verify (GpgOL)
b) encrypt (Apple Mail) -> decrypt (GpgOL)
c) sign/encrypt with attachment (Apple Mail) -> decrypt/verify and check attachment (GpgOL)
d) answer to (a): sign (GpgOL) -> verify (Apple Mail)
e) answer to (b): encrypt (GpgOL) -> decrypt (Apple Mail)
f) answer to (c): sign/encrypt with attachment (GpgOL) -> decrypt/verify and check attachment (Apple Mail)